Conversations api read timeout

Hi,
I am trying to execute this conversations api by passing the conversation id:
https:////api/v2/conversations/{conversationId}/recordings?formatId=WAV

I am passing the Authorization token in the header but I am getting the read timeout whenever I fire this api. I am using Java Spring framework Rest template to make this call. The other APIs to get the token, get all the conversations between two dates works fine but only this one throws readtimeout. Any help/pointers is greatly appreciated.
Thanks.

Can you provide the contextId or correlationId sent in the response?

Hi, I am not getting any contextId or correlationId in the response. It's just returning null.

It will be hard for me to trace what's going wrong without this. It may be present in the response headers as "inin-correlation-id"

Also, I'm a bit confused by the url you provided in the original post. I expected to see an api hostname (based on region) after the https://. Those are found in table form here: https://developer.genesys.cloud/platform/api/

In any case, you would probably have more success opening a case with Care, where they can investigate customer-specific data like authorization tokens.

I found the issue and solution. For this particular api and some others, first call usually returns 202, but we need to set a big number for read timeout(in my case 7k ms). When it returns 202, try making the same call again and you will get 200 with data. Hope this helps.

FWIW, you should set your client's request timeout to 16 seconds (16,000 ms). The API's max timeout is 15 seconds, so you'll always get some kind of response within that period. Setting your timeout to 1 second more allows some buffer to count time in transit because the API measures 15 seconds on its side. If your client timeout is reached, that indicates a network error as the API will always respond.

Thanks for the info. I will definitely keep this in my mind while designing my application.

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.