Delete single interaction content file

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.

In this page


Most URLs in the example code use the following values:

Headers

Header parameters in Requests (Interaction Content API) apply to this endpoint.

Authorization scopes supported:

ScopeAccess granted
interaction-content:deleteEntire endpoint

Parameters

Path 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 delete content for.

contentKey

Type

Required

Example

StringTruecallRecording

The identifier of the content you want to delete from the interaction. Supported values are:

  • callRecording. The call recording files in audio/wav format.
  • transcript. The transcript of a call recording in application/JSON format.
  • categorizationResult. The categorization result of the transcript in application/JSON format.
  • sentimentSummary. The sentiment summary of the transcript in application/JSON format.
  • Unique identifiers. To get other interaction content, you must provide the unique identifier of the specific content you want to get. 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 the unique identifier is:

    • Audio recordings collected by the IVR Data Collector. Content is returned in video file format.

    • Voicemails. Content is returned in WAV format. Identifiers for older voicemails may be in the format voicemail-123 where 123 is the ID of the agent who the voicemail is for.

    • Screen recordings. Content is returned in video file format.

    • Video and screen share (Visual Engagement) recordings. Content is returned in video file format.

    • Chat transcript. Content is returned in application/JSON format.
    • Chat attachment. Content can be in any format.
    • Conversation summaries generated by AI. Content is returned in JSON format.
    • Interaction logs in JSON format.

Requests

Delete call recording for an interaction

curl -L -X DELETE "https://***.api.newvoicemedia.com/interaction-content/interactions/017d8f64-945e-4eb4-9bcb-98b7bec78f24/content/callrecording" \
-H "Accept: application/vnd.newvoicemedia.v3+json" \
-H "Authorization: Bearer <ACCESS_TOKEN>"

Delete screen recording for an interaction

curl -L -X DELETE "https://***.api.newvoicemedia.com/interaction-content/interactions/017d8f64-945e-4eb4-9bcb-98b7bec78f24/content/a94461c0-7d9d-4195-ae5b-0eaffd2bbb59" \
-H "Accept: application/vnd.newvoicemedia.v3+json" \
-H "Authorization: Bearer <ACCESS_TOKEN>"

DELETE voicemail for an interaction

curl -L -X DELETE "https://***.api.newvoicemedia.com/interaction-content/interactions/017d8f64-945e-4eb4-9bcb-98b7bec78f24/content/017f2106-ff1b-8d35-89e5-1e01b327a159" \ 
-H "Accept: application/vnd.newvoicemedia.v3+json" \ 
-H "Authorization: Bearer <ACCESS_TOKEN>"

Responses

A response of this endpoint does not return any content data, just status code indicating result, optionally with json with deletion error description in case request failed. 

Successful response

A response to a valid deletion request is empty, with 204 status code.

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

Try it out

  

For information, see Trying out Vonage Contact Center APIs.