When responding to an erasure request, use this PUT method to confirm completion of an erasure in your system.

PUT

/v1/data-silo

In your request headers, pass authorization: Bearer <<token>>.

If you're self-hosting Sombra, also add the request header x-sombra-authorization: Bearer <<sombraInternalKey>>. You can read more about request authorization here.

x-transcend-noncestring
A reusable token sent in Transcend's webhook for this job, and returned by you when uploading the result of this job back to Transcend. Called a 'nonce' for legacy reasons, but is actually reusable.
authorizationstring
An API key generated from the Transcend dashboard: https://app.transcend.io/infrastructure/api-keys.
x-sombra-authorizationstring
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-typestring
Specify content-type: application/json for a JSON response from the Transcend API.

application/json

profilesarray<object>
[DEPRECATED] An array of each of the profiles that were erased. You should not set this value if you are using multi tenant Sombra or have a Sombra version at or above 7.199.0. For recent versions of Sombra, the profile identifier is pulled from the nonce, which means you can pass an empty body.
statusstringenum:"READY" | "RESOLVED" | "SKIPPED" | "SKIPPED_DUE_TO_EXCEPTION" | "ACTION_REQUIRED" | "WAITING"
Override the integration to be in a specific state. If `status` is set to "READY" or "RESOLVED", this will also mark all specified profiles as resolved.
profileStatusstringenum:"RESOLVED" | "SKIPPED" | "SKIPPED_DUE_TO_EXCEPTION" | "WAITING" | "ERROR"
Override the specified profiles to be in a specific state.
pollIdstring
If this DSR is in a polling state, this field will contain the ID of the async job that is polling for the DSR. You can use this ID to check the status of the DSR in your system.
messagestring
A message to include in the response to provide an update about the response. This is displayed in the Transcend dashboard. This can be an error message or a description about the current state of the request job.
retryAfterDatestring (date-time)
A date in the future that indicates when the user can retry the request. This is used for workflows that are asynchronous or to indicate when an error should be retried.

Request Body Examples

Update the profile specified in the nonce as resolved and denote that processing is done.:

{}

Update the profile specified in the nonce as resolved and denote that no data was found.:

{
  "status": "SKIPPED"
}

Update the profile specified in the nonce as skipped and denote more data to come:

{
  "status": "WAITING",
  "profileStatus": "SKIPPED"
}

Report back that an error occurred while processing the request:

{
  "message": "Something went wrong! Please reach out to Bobby.",
  "profileStatus": "ERROR"
}

Report back that an asynchronous job is polling for the DSR:

{
  "message": "The request has started processing and is polling for the DSR.",
  "pollId": "async-job-id-123",
  "profileStatus": "WAITING"
}

Report back that an asynchronous job is polling for the DSR, retry at a specific time:

{
  "message": "The request has started processing and is polling for the DSR.",
  "pollId": "async-job-id-123",
  "profileStatus": "WAITING",
  "retryAfterDate": "2025-06-07T00:00:00.000Z"
}

(DEPRECATED) Update the profile "12345" as resolved and denote that processing is done.:

{
  "profiles": [
    {
      "profileId": "12345"
    }
  ],
  "status": "RESOLVED"
}

(DEPRECATED) Update the profile "12345" as skipped and denote more data to come:

{
  "profiles": [
    {
      "profileId": "12345"
    }
  ],
  "status": "WAITING",
  "profileStatus": "SKIPPED"
}

200 (OK)

application/json

Your request was received without an issue.

400 (Bad Request)

application/json

While this request passed authentication, the input is malformed. Please double-check that your code conforms to our API specification.

401 (Unauthorized)

application/json

There was a problem authenticating your request. This may be an issue with the Transcend API key ("authorization" header), or the Sombra API key ("x-sombra-authorization" header used for self-hosted gateways only).

413 (Request Entity Too Large)

application/json

The request body is too large. JSON and raw bodies must be less than 50MB. URL encoded bodies must be less than 30MB.

429 (Too Many Requests)

application/json

You are sending requests too quickly and have hit our rate limit. If you hit this, you'll need to throttle your request velocity or try again later.

Response Headers

Retry-Afterinteger
X-RateLimit-Limitinteger
X-RateLimit-Remaininginteger
X-RateLimit-Resetinteger
Retry-Afterinteger
X-RateLimit-Limitinteger
X-RateLimit-Remaininginteger
X-RateLimit-Resetinteger
Retry-Afterinteger
X-RateLimit-Limitinteger
X-RateLimit-Remaininginteger
X-RateLimit-Resetinteger
Retry-Afterinteger
X-RateLimit-Limitinteger
X-RateLimit-Remaininginteger
X-RateLimit-Resetinteger

500 (Internal Server Error)

application/json

A 5xx error means there is either an issue with your self-hosted gateway, or a Transcend server is having issues. You check our system status at status.transcend.io. Please reach out to Transcend support if you're experiencing this error.

502 (Bad Gateway)

application/json

An upstream service on Transcend's side is having issues. You check our system status at status.transcend.io. Please reach out to Transcend support if you're experiencing this error.