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.
Most URLs in the example code use the following values:
- ***. To access the API for your region, replace *** with the correct subdomain for your region:
Region URL subdomain Base URL EMEA emea https://emea.api.newvoicemedia.com USA nam https://nam.api.newvoicemedia.com APAC apac https://apac.api.newvoicemedia.com - <ACCESS_TOKEN>. The value represents a bearer access token which you must use to validate every request. Replace <ACCESS_TOKEN> where used with your bearer access token. For information about getting a bearer access token, see How to authenticate with a Vonage Contact Center (VCC) API.
Headers
Header parameters in Requests (Interaction Content API) apply to this endpoint.
Authorization scopes supported:
Scope | Access granted |
---|---|
interaction-content:delete | Entire endpoint |
Parameters
Path parameters
The endpoint accepts the following path parameters:
guid
Type | Required | Example |
---|---|---|
String | Trsue | 2480fc2c-bbd7-427c-9439-02f76583aef5 |
The unique identifier of the interaction you want to delete content for.
contentKey
Type | Required | Example |
---|---|---|
String | True | callRecording |
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.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.- Unique identifiers. To get other interaction content, you must provide the unique identifier of the specific content you want to delete. For example,
017f2106-ff1b-8d35-89e5-1e01b327a159
. Unique identifiers are returned by theGET /interactions
andGET /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.)
- Screen recordings.
- Video and screen share (Visual Engagement) recordings.
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).
For information, see Trying out Vonage Contact Center APIs.