Treasure Data Parent Segment Configurations API
Defining a data model for customer data is done by defining parent segments. Parent segments give you an ability to build a single view of a customer, including capturing all interactions, such as attributes and behaviors associated with your brand. In parent segments, you unify your customer data. When the customer data is unified, you can create customer segments without writing any SQL queries. You can personalize customer communications and conversations of any size and in any channel. _Treasure Data is making an effort to use more inclusive language in its product, content, and customer solutions. As we gradually make the move to replace insensitive language beginning in our UI, you may continue to see parent segments in the UI, for example, referenced as master segment in portions of Treasure Data APIs._
Treasure Data Parent Segment Configurations API is one of 67 APIs that Treasure Data publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Parent Segment Configurations. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.
This API exposes 12 operations across 9 paths, and defines 26 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.
Requests are made against 5 base URLs: https://api-cdp.treasuredata.com, https://api-cdp.treasuredata.co.jp, https://api-cdp.eu01.treasuredata.com, https://api-cdp.ap02.treasuredata.com, https://api-cdp.ap03.treasuredata.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Treasure Data Parent Segment Configurations API declares
1 security scheme
for authenticating requests.
An API key is passed in the header as Authorization (TdApikeyAuth).
Paths & Operations 12
Across 9 paths, the API surfaces 12 operations — 1 DELETE, 8 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
Defining a data model for customer data is done by defining parent segments. Parent segments give you an ability to build a single view of a customer, including capturing all inte…
Schemas 26
The contract defines 26 schemas that model the data the API accepts and returns. The most detailed are Audience (28 properties), ComposableAudience (21 properties), AudienceAttributeWithVisibility (14 properties), ComposableAudienceAttribute (12 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Treasure Data 12
Other APIs Treasure Data publishes across the network.
This is an independent, third-party profile of Treasure Data Parent Segment Configurations 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.