Treasure Data Activation Templates API

Marketers find creating an activation challenging because they have to enter technical information they might not understand, which can lead to activations failing due to misconfigurations. Treasure Data solves this problem with the Activation Template. The Activation Template allows data engineers to create templates with pre-populated fields so that the marketer can confidently create an activation.

Operations 5

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

POST /entities/activation_templates Create an activation template · Create an Activation Template #
Ask an LLM
“How do I save a reusable activation setup as a template?”
“What attributes go into a new activation template?”
Tell an agent
Create an activation template with attributes {attributes}.
Save a new activation template using attributes {attributes} and relationships {relationships}.
GET /entities/activation_templates/{id} Get an activation template · Get an Activation Template #
Ask an LLM
“What settings does a particular activation template hold?”
“Can I look up one activation template by its ID?”
Tell an agent
Show activation template {id}.
Get the configuration of activation template {id}.
PATCH /entities/activation_templates/{id} Update an activation template · Update an Activation Template #
Ask an LLM
“Can I change the settings saved in an existing activation template?”
“Is it possible to edit an activation template's relationships?”
Tell an agent
Update activation template {id} with attributes {attributes}.
Change the relationships of activation template {id} to {relationships}.
DELETE /entities/activation_templates/{id} Delete an activation template · Delete an Activation Template #
Ask an LLM
“How do I remove an activation template nobody uses?”
“Can an activation template be deleted permanently?”
Tell an agent destructive · confirm first
Delete activation template {id}.
Remove the activation template with ID {id}.
GET /entities/parent_segments/{parentSegmentId}/activation_templates List activation templates for a parent segment · Returns list of Activation Templates by an audience (parent segment) #
Ask an LLM
“Which activation templates are available in a parent segment?”
“Can I list only the templates usable by a particular segment?”
Tell an agent
List activation templates for parent segment {parentSegmentId}.
List {kind} activation templates in parent segment {parentSegmentId} usable by segment {availableBySegmentId}.

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-activation-templates-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-activation-templates-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: cdp-api Activation Templates 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-activation-templates-api-openapi.yml