Page Comparison

The GET /interactions/{guid}/content/{contentKey} endpoint enables you to get a single interaction content file after specifying the interaction GUID and the content key.

...

Authorization scopes supported:

Parameters

...

The endpoint accepts the following path parameters:

guid

The unique identifier of the interaction you want to get content for.

contentKey

...

• callRecording. The call recording files in audio/wav format.
• transcript. The transcript of a call recording in application/json format.
• chatTranscript. The transcript of a chat in application/json format.
• attachment. The attachment file in application/json format.
• categorizationResult. The categorization result of the transcript in application/json format.
• ivrAudioRecording. The IVR audio recording files in audio/wav format.
• Unique identifiers. To get a voicemail or , a screen recording, or an audio recording collected by the IVR Data Collector, you must provide the unique identifier of the specific voicemail, screen recording, or screen audio recording you want to get. For example,   017f2106-ff1b-8d35-89e5-1e01b327a159. (Identifiers for older voicemails may be in the format voicemail-123 where 123 is the ID of the agent who the voicemail is for.) Unique identifiers for voicemails, screen recordings, and screen audio recordings are returned by the the GET /interactions and GET /interactions/{guid} endpoints.

Header parameters

range

bytes=0-1023

...

• callRecording (audio/wav)
• transcript, chatTranscript, categorizationResult, attachment (application/json)
• screenRecording (video/webm)
• voicemail (audio/wav)
• ivrAudioRecording (audio/wav)

For information about successful responses, see Success response code and parameters in Responses (Interaction Content API).