Raghava_PVDS | 2020-06-08 14:30:58 UTC | #1
HI Team
I am writing python code for accessing call conversation details.
I canot able run the date even for oneday and throwing error below.
Please confirm any limitation of Genesys API,if so what is the limit
Exception when calling ConversationsApi: (413)
Reason: Request Entity Too Large
HTTP response headers: HTTPHeaderDict({'Content-Type': 'application/json', 'Content-Length': '200', 'Connection': 'keep-alive', 'Date': 'Mon, 08 Jun 2020 04:30:30 GMT', 'ININ-Correlation-Id': '3a4774a5-6ebe-4695-802b-6d3ee86b5122', 'inin-ratelimit-count': '1', 'inin-ratelimit-allowed': '300', 'inin-ratelimit-reset': '61', 'Strict-Transport-Security': 'max-age=600; includeSubDomains', 'Cache-Control': 'no-cache, no-store, must-revalidate', 'Pragma': 'no-cache', 'Expires': '0', 'X-Cache': 'Error from cloudfront', 'Via': '1.1 01885e0921b66bb470420212191fe04d.cloudfront.net (CloudFront)', 'X-Amz-Cf-Pop': 'MAA50-C1', 'X-Amz-Cf-Id': 'KvulKLzPDhttV29ESVWsVOc6OCbsqjQAcyHDk3zOWb8YivSB8rGpiA=='})
HTTP response body: {"message":"The response size is too large. Max bytes allowed are: 10000000","code":"request entity too large","status":413,"contextId":"3a4774a5-6ebe-4695-802b-6d3ee86b5122","details":[],"errors":[]}
tim.smith | 2020-06-08 17:58:01 UTC | #2
Raghava_PVDS, post:1, topic:7979
Please confirm any limitation of Genesys API,if so what is the limit
Kindly refer to the error message:
Raghava_PVDS, post:1, topic:7979
"message":"The response size is too large. Max bytes allowed are: 10000000",
Raghava_PVDS | 2020-06-08 18:46:22 UTC | #3
Smith,
why it was throwng error for me
tim.smith | 2020-06-08 18:58:44 UTC | #4
Sorry, that error is a bit confusing. 413 and the reason in your post above point to an error with your request. But upon further investigation, the error in the message body is actually not a typo; the error is being caused by the response payload being too large. That should probably be a 500 error, not a 413 since your request was valid. Please open a case with Genesys Cloud Care to investigate further. Be sure to specifically mention that the this forum topic directed you to Care as the issue here is a server-side issue, not a client issue as the response code suggests.
tim.smith | 2020-06-09 14:18:57 UTC | #5
Further internal investigation has found this was related to a new feature that was rolled out. A fix is being tested and deployed very soon. Please continue to work with Care for details and further updates.
system | 2020-07-09 14:18:58 UTC | #6
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 7979