Delete Customization
DELETEOverview
Section titled “Overview”Delete an existing customization by its unique identifier.
Request parameters
Section titled “Request parameters”Path parameters
Section titled “Path parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
TRACKER_ID | string | ✓ | Your unique tracker identifier. |
CUSTOMIZATION_ID | UUID | ✓ | The unique ID of the customization to delete. |
Request headers
Section titled “Request headers”| Header | Value | Description |
|---|---|---|
Content-Type | application/json; charset=utf-8 | Required. |
Date | HTTP date | Required for HMAC. |
Authorization | ApiAuth {TRACKER_ID}:{SIGNATURE} | Required for HMAC. |
How to Make a Request
Section titled “How to Make a Request”- Build the string to sign from the method, content type, date, and full resource path including the customization ID.
- Generate the HMAC SHA-256 digest with your private key.
- Send the
Date,Content-Type, andAuthorizationheaders with theDELETErequest.
Response structure
Section titled “Response structure”This endpoint returns 204 No Content on successful deletion.
Error handling
Section titled “Error handling”| HTTP Status | Description |
|---|---|
204 No Content | Customization deleted successfully. |
401 Unauthorized | Missing or invalid authentication. |
404 Not Found | Customization not found. |
Was this page helpful?
Thanks.