Legacy Dev Forum Posts

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

202 Accepted and not 200 OK when trying to access recording API

  • 1.  202 Accepted and not 200 OK when trying to access recording API

    Posted 06-05-2025 18:22

    Somik_Mukherjee1 | 2022-06-02 14:26:17 UTC | #1

    Hi Team,

    I have used the below endpoint and tried to fill optional fields too. It always results in 202 Accepted and 1/5 times it comes with 200 OK.

    /api/v2/conversations/{conversationId}/recordings?maxWaitMs=1000&formatId=WAV&mediaFormats=WAV

    Please note this issue does not occur in other conversation APIs but only to this recording endpoint.

    Thanks, Somik Mukherjee

    tim.smith | 2022-06-02 15:48:26 UTC | #2

    The API documentation for GET /api/v2/conversations/{conversationId}/recordings does not document a 202 response code. Please open a case with Genesys Cloud Care to investigate this issue.

    My guess is that the behavior you're seeing is expected and the 202 response is simply lacking documentation. Care will be able to confirm this and report the missing documentation to be fixed.

    system | 2022-07-03 14:31:21 UTC | #3

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

    This post was migrated from the old Developer Forum.

    ref: 14986



Related Content