Treasure Data Predictive Segments API

Using Treasure Data’s predictive scoring model, based on predictive segments, marketers can predict profile behavior such as who is likely to churn, purchase, click, or convert in the near future. A predictive model is a set of rules that makes it possible to predict an unmeasured value from other, known values. The form of the rules is suggested by reviewing the data collected. Training is then used to make some predictions. Predictive modeling uses statistics to predict outcomes. Predictive modeling is a typically used statistical technique to predict future behavior. Predictive modeling solutions analyze historical and current data and the generated model helps predict future outcomes. In predictive modeling, data is collected, a statistical model is formulated, predictions are made, and the model is validated (or revised) as additional data becomes available. For example, risk models can be created to combine member information in complex ways with demographic and lifestyle information from external sources to improve underwriting accuracy. Predictive models analyze past performance to assess how likely a customer is to exhibit a specific behavior in the future. This category also encompasses models that seek out subtle data patterns to answer questions about customer performance, such as fraud detection models. Predictive models often perform calculations during live transactions—for example, to evaluate the risk or opportunity of a given customer or transaction to guide a decision. Treasure Data’s predictive scoring model uses predictive segments to customize predictive scoring models for a particular segment.

Operations 21

GET /audiences/{audienceId}/predictive_segments Retrieve list of predictive scoring models #
POST /audiences/{audienceId}/predictive_segments Create predictive scoring model (legacy) #
GET /audiences/{audienceId}/predictive_segments/{predictiveSegmentId} Retrieve predictive scoring model #
PATCH /audiences/{audienceId}/predictive_segments/{predictiveSegmentId} Update predictive scoring model (legacy) #
DELETE /audiences/{audienceId}/predictive_segments/{predictiveSegmentId} Delete predictive scoring model (legacy) #
GET /audiences/{audienceId}/predictive_segments/{predictiveSegmentId}/executions Retrieve predictive scoring model executions #
GET /audiences/{audienceId}/predictive_segments/guess_rule_async Retrieve guessed rule #
GET /audiences/{audienceId}/predictive_segments/{predictiveSegmentId}/model/columns Retrieve column list #
GET /audiences/{audienceId}/predictive_segments/{predictiveSegmentId}/model/features Retrieve column list of features #
GET /audiences/{audienceId}/predictive_segments/{predictiveSegmentId}/score_histogram Retrieve histogram #
POST /audiences/{audienceId}/predictive_segments/{predictiveSegmentId}/run Train predictive scoring model (legacy) #
GET /entities/segments/{id}/predictive_segments/guess_rule_async Retrieve predictive scoring rules #
POST /entities/predictive_segments Create predictive scoring model #
GET /entities/predictive_segments/{id} Retrieve predictive scording model by ID #
PATCH /entities/predictive_segments/{id} Update predictive scoring model #
DELETE /entities/predictive_segments/{id} Delete predictive scoring model #
POST /entities/predictive_segments/{id}/run Run predictive scoring model #
GET /entities/predictive_segments/{id}/executions Retrieve executions of predictive scoring model #
GET /entities/predictive_segments/{id}/model/features Retrieve features of predictive scoring model #
GET /entities/predictive_segments/{id}/model/columns Retrieve columns of predictive scoring model #
GET /entities/predictive_segments/{id}/model/score Retrieve scores of predictive scoring model #

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