Genesys Cloud - Developer Community!

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

Assistance Required: 404 Error When Fetching Call Recordings via API

  • 1.  Assistance Required: 404 Error When Fetching Call Recordings via API

    Posted 04-02-2025 10:58
    Edited by Manav Katewa 04-02-2025 10:58
     
    Hi Team,  
     
    We are currently using the `GET /api/v2/analytics/conversations/details/query` API to retrieve conversation IDs within a specified time range. The API is functioning as expected, returning the conversation IDs with `recording = True`.  
     
    However, when attempting to fetch the call recording for external speech analytics using the retrieved conversation ID, we encounter a 404 error (as shown in the attached screenshot). The only parameters we are passing is the conversation ID, which is the sole required field for this request.  
     
    To clarify:  
    - Call recordings are being successfully stored in the domain.  
     
    Could you please investigate and advise on where we might be going wrong? Any insights or guidance would be greatly appreciated.  
     
    For your reference, I've attached a screenshot illustrating the error. 

    Thank you for your support.  
     
    Best regards,  
    Manav

     


    #Integrations
    #PlatformAPI

    ------------------------------
    Manav Katewa
    Product Manager
    Eltropy
    ------------------------------



  • 2.  RE: Assistance Required: 404 Error When Fetching Call Recordings via API

    Posted 04-03-2025 16:16

    Are you getting that recording ID via /api/v2/conversations/{conversationId}/recordings first?  You are a bit vague on your flow for fetching the data, so just wanting to confirm.  The text in your video is blurry for me.

    Ideal process would be

    1. Call /api/v2/analytics/conversations/details/query
    2. For each conversation, call /api/v2/conversations/{conversationId}/recordings
      1. Note, this can return HTTP 202 Accepted.  The expectation is you wait a coupel seconds, then re-call it, to get the full response.  This is because Genesys is generating S3 signed URL's to temporarily access the audio files where they are stored, this isn't instant so it's more of a queue than a one-shot API call.
    3. Fetch the recordings from the AWS URL step 2 provides

    If that's what you are doing, I would check the permissions of the OAuth client/user you are using, as well as confirm the recording is actually there (recording polices can delete them but leave the "Recorded" flag enabled on the conversation record).



    ------------------------------
    Paul McGurn
    Senior Manager, Telecom & DevOps
    Persistent Systems
    ------------------------------



Related Content