Get single interaction content file

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.

Parameters

Path parameters

The endpoint accepts the following path parameters:

guid

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

contentKey

The identifier of the content you want to get from the interaction. Minimum length is 1, maximum is 36. Characters must be one of ^[0-9a-zA-Z!\-_.,*'()]+$.

Header parameters

range

This parameter is optional. You can request a specific part of a file from an interaction, for example the first 20MB of a call recording. For information on the standard accepted, see HTTP range requests.

Responses

A response to the endpoint returns a file.

Successful response

A response to a valid request contains a binary content file such as an audio, video or json file. The way the file is presented depends on individual client settings. The types of content returned in a response are defined in the Content-Type header. The GET interaction content endpoint supports the following types:

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

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