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._

Business capability
Customer Segmentation Management BC-420.20

Operations 12

GET /audiences Retrieve list of parent segment configurations #
POST /audiences Create new parent segment configuration #
GET /audiences/{audienceId} Retrieve parent segment configuration by ID #
PUT /audiences/{audienceId} Update parent segment configuration #
DELETE /audiences/{audienceId} Delete parent segment configuration #
GET /audiences/{audienceId}/attributes Retrieve list of audience attributes #
GET /audiences/{audienceId}/behaviors Retrieve list of audience behaviors #
POST /audiences/{audienceId}/run Run workflow to (re)generate parent segment #
GET /audiences/{audienceId}/executions Retrieve list of executions using audienceId #
GET /audiences/{audienceId}/statistics Retrieve population statistics audience #
GET /audiences/{audienceId}/sample_values Retrieve list of values for a parent segment configuration's attribute #
GET /audiences/{audienceId}/behaviors/{audienceBehaviorId}/sample_values Retrieve list of sample values for a parent segment configuration's behavior #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/treasure-data-parent-segment-configurations-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

treasure-data-parent-segment-configurations-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: cdp-api Parent Segment Configurations API
  description: All of the CDP APIs are organized around REST - if you've interacted with a RESTful API already, many of the concepts will be familiar to you. All API calls to CDP API should be made to the following endpoints depending on the region. For historical reasons there are REST API endpoints and JSON:API endpoints. JSON:API endpoints are located under "/entities".
  termsOfService: https://www.treasuredata.com/terms/
  version: 1.0.0
servers:
- url: https://api-cdp.treasuredata.com
- url: https://api-cdp.treasuredata.co.jp
- url: https://api-cdp.eu01.treasuredata.com
- url: https://api-cdp.ap02.treasuredata.com
- url: https://api-cdp.ap03.treasuredata.com
tags:


# --- truncated at 32 KB (41 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/treasure-data/refs/heads/main/openapi/treasure-data-parent-segment-configurations-api-openapi.yml