Legacy Dev Forum Posts

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

Get recordingId older than 558 days

  • 1.  Get recordingId older than 558 days

    Posted 06-05-2025 18:24

    Lucasss | 2022-11-17 01:27:57 UTC | #1

    Hello,

    I found the conversationId using job api to download a recording older than 558 days.

    /api/v2/analytics/conversations/details/jobs,

    /api/v2/analytics/conversations/details/jobs/{jobId}/results

    If I request recording metadata api with this conversation id, it returns an error.

    /api/v2/conversations/{conversationId}/recordingmetadata

    { "message": "Conversation does not exist in your organization", "code": "bad.request", "status": 400, "contextId": "3f7dec60-d004-4045-b03d-013f4afc91ea", "details": [], "errors": [] }

    I referred to the document below. https://help.mypurecloud.com/articles/retention-period-for-analytics-data-and-recording/

    Is there a way to get a recording Id older than 558 days?

    Thank you

    Eos_Rios | 2022-11-17 13:50:25 UTC | #2

    you have to be in an eligible group, and probably have to have enabled this before the time limit passes, but bottom line is reach out to support;

    ,full:true

    What is allowlisting?

    Allowlisting is a temporary workaround to bypass the 558 day deprecation to the Analytics Details API. Allowlisting will enable data that is up to 5 years old to be retrieved from this endpoint which extends recording playback functionality for conversations that are older than 1.5 years. (Note: Allowlisting is not available in us-west-2, ca-central-1, and eu-west-2) To request to be allowlisted, please contact Product Support.

    system | 2022-12-18 13:48:52 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: 17256



Related Content