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

Operations 17

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /audiences/{audienceId}/folders/{folderId}/syndications List activations under a segment folder · Retrieve list of activations recursively under a folder #
Ask an LLM
“Can I see every activation inside a segment folder, including its subfolders?”
“Which activations in a folder use a given connection type or schedule status?”
Tell an agent
List all activations recursively under folder {folderId} in parent segment {audienceId}.
Show activations under folder {folderId} of parent segment {audienceId} whose name includes {name_include}.
GET /audiences/{audienceId}/segments/{segmentId}/syndications List activations of a segment (audience API) · Retrieve list of activations in segment #
Ask an LLM
“What activations are attached to this segment in my parent segment?”
“Where do I find the activations that push one segment out to destinations?”
Tell an agent
List the activations for segment {segmentId} in parent segment {audienceId}.
Show which activations send segment {segmentId} (parent segment {audienceId}) to destinations.
POST /audiences/{audienceId}/segments/{segmentId}/syndications Create an activation for a segment · Create activation #
Ask an LLM
“How do I set up an activation that sends a segment to a destination connection in Treasure Data?”
“Can an activation run on a cron schedule with email notifications?”
Tell an agent
Create an activation named {name} for segment {segmentId} in parent segment {audienceId}.
Create activation {name} on segment {segmentId} of parent segment {audienceId} using connection {connectionId}.
GET /audiences/{audienceId}/segments/{segmentId}/syndications/{syndicationId} Get an activation of a segment by ID · Retrieve activation by ID #
Ask an LLM
“How can I look up the settings of a single activation on a parent-segment segment?”
“What schedule and connection does a specific activation use?”
Tell an agent
Show activation {syndicationId} of segment {segmentId} in parent segment {audienceId}.
Get the schedule and connection of activation {syndicationId} on segment {segmentId}, parent segment {audienceId}.
PUT /audiences/{audienceId}/segments/{segmentId}/syndications/{syndicationId} Update an activation's settings · Update activation #
Ask an LLM
“Can I change the schedule or columns of an existing activation?”
“How do I rename an activation that's already sending a segment out?”
Tell an agent
Rename activation {syndicationId} on segment {segmentId} in parent segment {audienceId} to {name}.
Change the cron of activation {syndicationId} (segment {segmentId}, parent segment {audienceId}, name {name}) to {cron}.
DELETE /audiences/{audienceId}/segments/{segmentId}/syndications/{syndicationId} Delete an activation from a segment · Delete activation #
Ask an LLM
“How do I remove an activation from a segment under a parent segment?”
“Can I stop a segment being sent to a destination by deleting its activation?”
Tell an agent destructive · confirm first
Delete activation {syndicationId} from segment {segmentId} in parent segment {audienceId}.
Remove activation {syndicationId} so segment {segmentId} in parent segment {audienceId} stops being sent.
POST /audiences/{audienceId}/segments/{segmentId}/syndications/{syndicationId}/run Run an activation now (legacy Audience Studio) · Run activation (legacy) #
Ask an LLM
“How do I trigger an activation to run immediately in legacy Audience Studio?”
“Can I manually kick off an activation instead of waiting for its schedule?”
Tell an agent
Run activation {syndicationId} of segment {segmentId} in parent segment {audienceId} now.
Trigger legacy activation {syndicationId} for segment {segmentId} in parent segment {audienceId} outside its schedule.
GET /audiences/{audienceId}/syndications List all activations in a parent segment · Retrieve list of activations in audience #
Ask an LLM
“What activations exist across a whole parent segment and what are their statuses?”
“Can I get the activation list for a parent segment without the detail fields?”
Tell an agent
List every activation in parent segment {audienceId} with their schedules.
List activations in parent segment {audienceId} with without_detail set to {without_detail}.
GET /entities/segments/{segmentId}/syndications List a segment's activations (entities API) · Retrieve list of activations #
Ask an LLM
“Is there a JSON:API endpoint that lists a segment's activations by segment ID alone?”
“Which activations belong to a segment in the entities API?”
Tell an agent
List activations for segment {segmentId} using the entities API.
Show the JSON:API activation records for segment {segmentId}.
POST /entities/segments/{segmentId}/syndications Create an activation via the entities API · Create activation #
Ask an LLM
“Can I create an activation with only a segment ID, using the JSON:API entities endpoint?”
“What does a JSON:API activation create payload need for type and attributes?”
Tell an agent
Create an entities-API activation on segment {segmentId} with attributes {attributes}.
Add a JSON:API activation of type {type} to segment {segmentId}.
GET /entities/segments/{segmentId}/syndications/{id} Get one activation via the entities API · Retrieve list of activations #
Ask an LLM
“How do I fetch a single activation from the entities API by its ID?”
“Can I read an activation's attributes in JSON:API format?”
Tell an agent
Get entities-API activation {id} on segment {segmentId}.
Read the JSON:API attributes of activation {id} for segment {segmentId}.
PATCH /entities/segments/{segmentId}/syndications/{id} Patch an activation via the entities API · Update activation #
Ask an LLM
“How do I partially update an activation's attributes with a JSON:API PATCH?”
“Can I change a single attribute of an activation in the entities API?”
Tell an agent
Patch entities-API activation {id} on segment {segmentId} with attributes {attributes}.
Partially update JSON:API activation {id} of segment {segmentId}.
DELETE /entities/segments/{segmentId}/syndications/{id} Delete an activation via the entities API · Delete activation #
Ask an LLM
“Can I delete an activation through the JSON:API entities endpoint?”
“How is an activation removed when I only know the segment ID and activation ID?”
Tell an agent destructive · confirm first
Delete entities-API activation {id} from segment {segmentId}.
Remove JSON:API activation {id} belonging to segment {segmentId}.
POST /entities/segments/{segmentId}/syndications/{id}/run Run an activation via the entities API · Run activation #
Ask an LLM
“Can I trigger an activation run through the entities API by segment and activation ID?”
“What starts an entities-API activation immediately?”
Tell an agent
Run entities-API activation {id} on segment {segmentId}.
Trigger activation {id} of segment {segmentId} via the entities endpoint now.
GET /entities/parent_segments/{parentSegmentId}/syndications List activation summaries by parent segment · Retrieve list of activations by parent segment #
Ask an LLM
“Can I get a summary list of activations for a parent segment from the entities API?”
“Which activations hang off one parent segment, in summary form?”
Tell an agent
List activation summaries for parent segment {parentSegmentId} via the entities API.
Show entities-API activations under parent segment {parentSegmentId}.
GET /entities/parent_segments/{parentSegmentId}/user_defined_workflow_projects List workflow projects for custom activations · List of workflow project names #
Ask an LLM
“Which workflow projects can I pick for a custom workflow activation?”
“Can I filter workflow project names by a pattern?”
Tell an agent
List workflow project names for parent segment {parentSegmentId}.
Find workflow projects matching {namePattern} for parent segment {parentSegmentId}, after {lastId}.
GET /entities/parent_segments/{parentSegmentId}/user_defined_workflows List workflows in a project for custom activations · List of workflow names #
Ask an LLM
“Which workflows inside a project can a custom activation call?”
“What workflow names exist in a given workflow project for my parent segment?”
Tell an agent
Show the individual workflows defined inside project {workflowProjectName} for parent segment {parentSegmentId}.
Show workflows of project {workflowProjectName} usable by parent segment {parentSegmentId}.

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

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