Transcend Docs
API referencePreferences (Server-Side)

Delete preference records

POST
/v1/preferences/{partition}/delete

Batch delete consent preference records by anchor identifier. This endpoint deletes preference records from the Preference Store only and does not trigger DSR workflows or delete data in downstream systems.

Rate Limits

  • 100 requests per organization per minute (default).
  • This limit can be increased upon request.

Rate Limiting Headers

  • X-RateLimit-Limit: The maximum number of requests allowed in the current window.
  • X-RateLimit-Remaining: The number of requests remaining in the current window.
  • X-RateLimit-Reset: The time at which the current rate limit window resets in ISO 8601 format.
  • Retry-After: (on 429) The number of seconds to wait before making a new request.

Deleting by Transcend ID

  • Every preference record has a system-managed transcend identifier — a stable UUID automatically assigned by the system.
  • Use { "name": "transcend", "value": "<uuid>" } as the anchorIdentifier to delete a record by Transcend ID.

Authorization

Transcend_API_Key Modify User Stored Preferences
headerAuthorizationBearer <token>

authorization: Bearer <>

Scope: Modify User Stored Preferences

Path Parameters

partition*string

The ID of the partition in the Preference Store.

Header Parameters

authorization*string

An API key generated from the Transcend dashboard: https://app.transcend.io/infrastructure/api-keys.

x-sombra-authorization?string

The Sombra internal key. This header is only needed for self-hosted Sombra gateways. See https://docs.transcend.io/docs/dsr-automation/api-integration/authentication#authenticating-to-sombra

content-type*string

Specify content-type: application/json for a JSON response from the Transcend API.

Matchapplication-json

Request Body

application/json
  1. body
records*array<>

List of delete operations to remove whole preference records.

Itemsitems <= 10

Response Body

The response payload contains the results of the batch delete operation. Each record in the records array corresponds to an input record and indicates whether the delete operation succeeded or failed, along with any relevant error messages. Note: When the response includes failures, clients can only retry the failed items from the original request after addressing the reported errors. When the response includes errors, clients should retry the entire batch after addressing the reported errors.

application/json
  1. response
records?array<>
failures?array<>
errors?array<string>
curl -X POST 'https://multi-tenant.sombra.transcend.io/v1/preferences/string/delete' \  -H 'authorization: string' \  -H 'content-type: string' \  -H 'Content-Type: application/json' \  -d '{  "records": [    {      "anchorIdentifier": {        "name": "email",        "value": "xyz@foo.com"      },      "timestamp": "2025-11-26T17:33:13.515Z"    }  ]}'
Example Response
{  "records": [    {      "success": true    }  ],  "failures": [],  "errors": []}