How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Transcend Preferences API

Server-side preference store CRUD and query operations.

Transcend Preferences API is one of 11 APIs that Transcend publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 2 JSON Schema definitions.

Tagged areas include Preferences. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a status page, a JSON-LD context, rate-limit docs, and 2 JSON Schemas.

This API exposes 6 operations across 6 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 3.2.

Requests are made against 6 base URLs: https://api.transcend.io, https://api.us.transcend.io, https://multi-tenant.sombra.transcend.io, https://multi-tenant.sombra.us.transcend.io, https://consent.transcend.io, https://consent.us.transcend.io.

6 operations 6 paths 3 schemas 5 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.2
Base URL
https://api.transcend.io
Authentication
API Key
Contact
Resource Areas
1

Authentication & Security 1

Transcend Preferences API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Transcend_API_Key). By default, every request must be authenticated.

  • Transcend_API_Key — API key issued from the Transcend admin dashboard. Send as Authorization: Bearer .

Paths & Operations 6

Across 6 paths, the API surfaces 6 operations — 5 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Preferences 6

Server-side preference store CRUD and query operations.

PUT
/v1/preferences
Upsert Preferences for a Data Subject
upsertPreferences body → 200
POST
/v1/preferences/{partition}/query
Query Preferences in a Partition
queryPreferences 1 param body → 200
POST
/v1/preferences/{partition}/delete
Delete Preference Records
deletePreferences 1 param body → 200
POST
/v1/preferences/{partition}/append-identifiers
Append Identifiers To Preference Records
appendPreferenceIdentifiers 1 param body → 200
POST
/v1/preferences/{partition}/update-identifiers
Update Identifiers On Preference Records
updatePreferenceIdentifiers 1 param body → 200
POST
/v1/preferences/{partition}/delete-identifiers
Delete Identifiers From Preference Records
deletePreferenceIdentifiers 1 param body → 200

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are PreferenceUpsert (3 properties), IdentifierMutation (2 properties), Identifier (2 properties). Each schema is shown below with its type and property counts.

Identifier
object
2 properties
IdentifierMutation
object
2 properties
PreferenceUpsert
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

transcend-io-preferences-api-openapi.yml Raw ↑

Other APIs Transcend publishes across the network.

Transcend GraphQL API
Transcend CLI
Transcend MCP Servers
Transcend Consent API
Transcend Custom Integration API
Transcend Data Subject Request API
Transcend LLM Classifier API
Transcend Preflight API
Transcend Public Keys API
Transcend Transcend API API
Where this information came from

This is an independent, third-party profile of Transcend Preferences API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.