Treasure Data

Treasure Data Realtime Personalization API

The Realtime Personalization API from Treasure Data — 7 operation(s) for realtime personalization.

GitHub OpenAPI

Operations 12

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}/realtime_personalization_services List realtime personalization services · Return a list of Realtime Personalization Services for the Audience #
Ask an LLM
“Which realtime personalization services are set up for an audience?”
“Can I filter personalization services by name or page through them?”
Tell an agent
List the realtime personalization services for audience {audienceId}.
Find personalization services in audience {audienceId} whose name includes {name_include}.
POST /audiences/{audienceId}/realtime_personalization_services Create a realtime personalization service · Create a Realtime Personalization Service for the Audience #
Ask an LLM
“How do I stand up a realtime personalization service for an audience?”
“Can a new personalization service be made public when I create it?”
Tell an agent
Create a personalization service named {name} for audience {audienceId}.
Create personalization service {name} in audience {audienceId} described as {description}, with public set to {public}.
GET /audiences/{audienceId}/realtime_personalization_services/{realtimePersonalizationServiceId} Get a realtime personalization service · Return the specified Realtime Personalization Service #
Ask an LLM
“What is configured on one personalization service?”
“Can I look up a single personalization service in an audience?”
Tell an agent
Show personalization service {realtimePersonalizationServiceId} in audience {audienceId}.
Fetch the details of personalization service {realtimePersonalizationServiceId} for audience {audienceId}.
PATCH /audiences/{audienceId}/realtime_personalization_services/{realtimePersonalizationServiceId} Edit a realtime personalization service · Edit the specified Realtime Personalization Service #
Ask an LLM
“Can I rename a personalization service or change its description?”
“What can be edited on an existing personalization service?”
Tell an agent
Rename personalization service {realtimePersonalizationServiceId} in audience {audienceId} to {name}.
Set the name of service {realtimePersonalizationServiceId} in audience {audienceId} to {name} and its description to {description}.
DELETE /audiences/{audienceId}/realtime_personalization_services/{realtimePersonalizationServiceId} Delete a realtime personalization service · Delete the specified Realtime Personalization Service #
Ask an LLM
“How do I shut down and remove a personalization service?”
“Is deleting a whole personalization service permanent?”
Tell an agent destructive · confirm first
Delete personalization service {realtimePersonalizationServiceId} from audience {audienceId}.
Remove the unused personalization service {realtimePersonalizationServiceId} in audience {audienceId}.
POST /audiences/{audienceId}/realtime_personalization_services/{realtimePersonalizationServiceId}/tokens Create a personalization token · Create a new Personalization Token #
Ask an LLM
“How do I issue an access token for a personalization service?”
“Can I restrict a personalization token to certain IP addresses?”
Tell an agent
Create a token named {name} for personalization service {realtimePersonalizationServiceId} in audience {audienceId}.
Issue personalization token {name} on service {realtimePersonalizationServiceId} in audience {audienceId}, allowed only from {allowedIps}.
DELETE /audiences/{audienceId}/realtime_personalization_services/{realtimePersonalizationServiceId}/tokens/{tokenId} Delete a personalization token · Delete the specified Realtime Personalization Token #
Ask an LLM
“How do I revoke a personalization token that leaked?”
“Does deleting a token stop clients that use it from calling the service?”
Tell an agent destructive · confirm first
Delete token {tokenId} from personalization service {realtimePersonalizationServiceId} in audience {audienceId}.
Revoke personalization token {tokenId} on service {realtimePersonalizationServiceId}, audience {audienceId}.
POST /entities/realtime_personalizations Create a realtime personalization · Create a realtime personalization #
Ask an LLM
“Can I define a new realtime personalization that returns profile data in real time?”
“What attributes are required to create a realtime personalization entity?”
Tell an agent
Create a realtime personalization with attributes {attributes}.
Create a realtime personalization with {attributes} linked to {relationships}.
GET /entities/realtime_personalizations/{realtimePersonalizationId} Get a realtime personalization · Get a realtime personalization #
Ask an LLM
“What is configured on a particular realtime personalization?”
“Can I fetch a single realtime personalization entity by ID?”
Tell an agent
Show realtime personalization {realtimePersonalizationId}.
Fetch the settings of realtime personalization {realtimePersonalizationId}.
PATCH /entities/realtime_personalizations/{realtimePersonalizationId} Update a realtime personalization · Update a realtime personalization #
Ask an LLM
“Can I change the attributes of an existing realtime personalization?”
“What happens when I edit a realtime personalization entity?”
Tell an agent
Update realtime personalization {realtimePersonalizationId} with attributes {attributes}.
Change the attributes of existing realtime personalization {realtimePersonalizationId} to {attributes}.
DELETE /entities/realtime_personalizations/{realtimePersonalizationId} Delete a realtime personalization · Delete realtime personalization entity #
Ask an LLM
“How do I remove a realtime personalization entity?”
“Is deleting a realtime personalization permanent?”
Tell an agent destructive · confirm first
Delete realtime personalization {realtimePersonalizationId}.
Remove the obsolete realtime personalization {realtimePersonalizationId}.
GET /entities/parent_segments/{parentSegmentId}/realtime_personalizations List realtime personalizations in a parent segment · Retrieve a list of realtime personalizations under the Parent Segment #
Ask an LLM
“Which realtime personalizations exist under a parent segment?”
“Can I list only the realtime personalizations I have edit permission on?”
Tell an agent
List realtime personalizations under parent segment {parentSegmentId}.
List realtime personalizations in parent segment {parentSegmentId} where I have {permissions} permission.

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