Page Comparison

The DELETE /interactions/{guid}/content/{contentKey} endpoint enables you to delete 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 delete 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 delete a voicemail, a screen recording, or an audio recording collected by the IVR Data Collector, get other interaction content, you must provide the unique identifier of the specific voicemail, screen recording, or audio recording content you want to delete. For example, 017f2106-ff1b-8d35-89e5-1e01b327a159. Unique identifiers are returned by the GET /interactions and GET /interactions/{guid} endpoints. Interaction content that is identified by unique identifier is:
  
  • Audio recordings collected by the IVR Data Collector.
  • Voicemails. (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 audio recordings are returned by the GET /interactions and GET /interactions/{guid} endpoints
  •  
  • Screen recordings.
  • Video and screen share (Visual Engagement) recordings.

Requests

Delete call recording for an interaction

...