Treasure Data

Treasure Data Activations API

Activation is the process that allows marketers to personalize communication to users interested in your brand. **Funnel activation** — Create a funnel activation for each funnel stage. The activation exports to external marketing tools for campaigns or BI tools for analysis and reporting. **Segment activation** — Activate the segment data (export) to external tools for activities such as marketing campaigns, business analysis, and social media. Targets include Email Marketing Systems, Marketing Automation Systems, Advertising Platforms, CRM, ERP, Cloud Services, and SFTP. _Known formerly as syndication in Audience Studio Legacy. You may continue to see syndication referenced in Treasure Data APIs._

GitHub OpenAPI

Operations 17

GET /audiences/{audienceId}/folders/{folderId}/syndications Retrieve list of activations recursively under a folder #
GET /audiences/{audienceId}/segments/{segmentId}/syndications Retrieve list of activations in segment #
POST /audiences/{audienceId}/segments/{segmentId}/syndications Create activation #
GET /audiences/{audienceId}/segments/{segmentId}/syndications/{syndicationId} Retrieve activation by ID #
PUT /audiences/{audienceId}/segments/{segmentId}/syndications/{syndicationId} Update activation #
DELETE /audiences/{audienceId}/segments/{segmentId}/syndications/{syndicationId} Delete activation #
POST /audiences/{audienceId}/segments/{segmentId}/syndications/{syndicationId}/run Run activation (legacy) #
GET /audiences/{audienceId}/syndications Retrieve list of activations in audience #
GET /entities/segments/{segmentId}/syndications Retrieve list of activations #
POST /entities/segments/{segmentId}/syndications Create activation #
GET /entities/segments/{segmentId}/syndications/{id} Retrieve list of activations #
PATCH /entities/segments/{segmentId}/syndications/{id} Update activation #
DELETE /entities/segments/{segmentId}/syndications/{id} Delete activation #
POST /entities/segments/{segmentId}/syndications/{id}/run Run activation #
GET /entities/parent_segments/{parentSegmentId}/syndications Retrieve list of activations by parent segment #
GET /entities/parent_segments/{parentSegmentId}/user_defined_workflow_projects List of workflow project names #
GET /entities/parent_segments/{parentSegmentId}/user_defined_workflows List of workflow names #

Documentation

📖
Documentation
https://docs.treasure.ai/apis/td-api
📖
APIReference
https://docs.treasure.ai/apis/td_api_v3-public
📖
GettingStarted
https://docs.treasure.ai/apis/td-api
📖
Documentation
https://docs.treasure.ai/apis/audience-api/overview
📖
APIReference
https://docs.treasure.ai/apis/td_cdp_api-public
📖
GettingStarted
https://docs.treasure.ai/apis/audience-api
📖
Documentation
https://docs.treasure.ai/apis/llm-api
📖
APIReference
https://docs.treasure.ai/apis/llm_api-public
📖
GettingStarted
https://docs.treasure.ai/apis/llm-api
📖
APIReference
https://docs.treasure.ai/apis/dwh_integration_api-public
📖
GettingStarted
https://docs.treasure.ai/apis/dwh-integration-api/quickstart
📖
GettingStarted
https://docs.treasure.ai/apis/p13n-api
📖
GettingStarted
https://docs.treasure.ai/apis/postback-v2/quickstart

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/treasure-data/refs/heads/main/openapi/treasure-data-activations-api-openapi.yml

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

GitHub Google LinkedIn

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

OpenAPI Specification

treasure-data-activations-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: cdp-api Activations 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 (65 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/treasure-data/refs/heads/main/openapi/treasure-data-activations-api-openapi.yml