List out all of the identifiers that are attached to DSRs. These may be the emails, coreIdentifiers, phone numbers, user IDs, advertising IDs and more.

POST

/v1/request-identifiers

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.

Requires scope:

View the Request Compilation

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

requestIdstring (uuid)(required)
The UUID of the request to fetch request identifiers for
firstnumber
The number of results to return on this page. Defaults to 10, maximum is 100.
offsetnumber
The offset to use while paginating.

Request Body Examples

Query for first 100 identifiers on a request:

{
  "first": 100,
  "requestId": "96946f0d-6453-4d52-9d66-d5f2089acbc1"
}

Query for second page:

{
  "first": 100,
  "requestId": "96946f0d-6453-4d52-9d66-d5f2089acbc1",
  "offset": 100
}

200 (OK)

application/json

Returns a list of request identifiers

Response Body

identifiersarray<object>(required)

Response Body Example

Sample response body:

{
  "identifiers": [
    {
      "id": "7f21c58b-53c9-483e-84c2-40284cdd28ae",
      "value": "no-track@example.com",
      "name": "email",
      "type": "email"
    },
    {
      "id": "c8f600ea-917f-4e02-95d4-af475d3e07ec",
      "value": "another@example.com",
      "name": "email",
      "type": "email"
    },
    {
      "id": "cf2ad7bc-ea08-4e19-b167-4ef24c3770cd",
      "value": "myusernameslug",
      "name": "coreIdentifier",
      "type": "coreIdentifier"
    },
    {
      "id": "b1981873-f3e6-4fc8-9713-64b1c7cdc5ef",
      "value": "+16126883289",
      "name": "phone",
      "type": "phone"
    },
    {
      "id": "6bdd20f6-5019-4d64-a9b4-0ea5111b94d3",
      "value": "38400000-8cf0-11bd-b23e-10b96e40000d",
      "name": "gaid",
      "type": "gaid"
    },
    {
      "id": "62e2fadd-6331-4ae0-a72b-52d61f27769c",
      "value": "myusernameslug",
      "name": "user_id",
      "type": "custom"
    }
  ]
}

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

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.