-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chats
endpoint returning 400 Status - Bad Request Errors
#14
Comments
I'm labeling this as |
+1 on getting this error when trying to use stitch. Any ideas how to get around? |
+1 on this as well. Any updates on getting around this? I've tried removing replication from account and agents, along with ban, but still getting the same error. |
Getting the same error now. It will be great help if anyone can guide on how to resolve the same. Thanks. |
Getting the same error. Seems related to a previous update that limited the start and end time pulled to 14 days in order to limit the total chats retrieved from the endpoint to 10k or less. If you exceed 10k (40 per page x 250 pages) on the 251st page you will always get this error. Seems enough people are having it that we may want to reduce this start and end time window to 7 days. |
Alternately, if this has been parameterized in the code to accept a custom start and end time, we need an update in Stitch to allow this to be set in the Integration. |
We noticed a bad request against the
chats
endpoint.400 Client Error: BAD REQUEST for url: https://www.zopim.com/api/v2/chats/search?q=type%3Achat+AND+end_timestamp%3A%5B2017-11-19T14%3A47%3A52%2B00%3A00+TO+2017-12-03T14%3A47%3A52%2B00%3A00%5D&page=251
Full traceback below:
The text was updated successfully, but these errors were encountered: