Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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:

ScopeAccess granted
interaction-content:readEntire endpoint

Parameters

...

The endpoint accepts the following path parameters:

guid

Type

Required

Example

StringTrue2480fc2c-bbd7-427c-9439-02f76583aef5

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

contentKey

Type

Required

Example

StringTruecallRecording

...

  • 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.
  • attachment. The attachment file in application/json format.
  • categorizationResult. The categorization result of the transcript in application/json format.
  • Unique identifiers. To get a voicemail or a screen recording, you must provide the unique identifier of the specific voicemail or screen 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 and screen recordings are returned by the GET /interactions and GET /interactions/{guid} endpoints.

Header parameters

range

Type

Required

Example

StringFalse
bytes=0-1023

...

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

...