How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

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.

Treasure Data Predictive Segments API is one of 67 APIs that Treasure Data publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Predictive Segments. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.

This API exposes 21 operations across 16 paths, and defines 27 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 5 base URLs: https://api-cdp.treasuredata.com, https://api-cdp.treasuredata.co.jp, https://api-cdp.eu01.treasuredata.com, https://api-cdp.ap02.treasuredata.com, https://api-cdp.ap03.treasuredata.com.

21 operations 16 paths 27 schemas 2 DELETE13 GET2 PATCH4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.treasuredata.com/v3/bulk_loads
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

Treasure Data Predictive Segments API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (TdApikeyAuth).

Paths & Operations 21

Across 16 paths, the API surfaces 21 operations — 2 DELETE, 13 GET, 2 PATCH, 4 POST. Each is listed below with its method, path, parameters, and response codes.

Predictive Segments 21

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…

GET
/audiences/{audienceId}/predictive_segments
Retrieve list of predictive scoring models
predictive_segments#index 1 param → 2004004014034044XX5XX
POST
/audiences/{audienceId}/predictive_segments
Create predictive scoring model (legacy)
predictive_segments#create 1 param body → 2004004014034044XX5XX
GET
/audiences/{audienceId}/predictive_segments/{predictiveSegmentId}
Retrieve predictive scoring model
2 params → 2004004014034044XX5XX
PATCH
/audiences/{audienceId}/predictive_segments/{predictiveSegmentId}
Update predictive scoring model (legacy)
predictive_segments#update 2 params body → 2004004014034044XX5XX
DELETE
/audiences/{audienceId}/predictive_segments/{predictiveSegmentId}
Delete predictive scoring model (legacy)
predictive_segments#destroy 2 params → 2004004014034044XX5XX
GET
/audiences/{audienceId}/predictive_segments/{predictiveSegmentId}/executions
Retrieve predictive scoring model executions
2 params → 2004004014034044XX5XX
GET
/audiences/{audienceId}/predictive_segments/guess_rule_async
Retrieve guessed rule
2 params → 2004004014034044XX5XX
GET
/audiences/{audienceId}/predictive_segments/{predictiveSegmentId}/model/columns
Retrieve column list
3 params → 2004004014034044XX5XX
GET
/audiences/{audienceId}/predictive_segments/{predictiveSegmentId}/model/features
Retrieve column list of features
3 params → 2004004014034044XX5XX
GET
/audiences/{audienceId}/predictive_segments/{predictiveSegmentId}/score_histogram
Retrieve histogram
3 params → 2004004014034044XX5XX
POST
/audiences/{audienceId}/predictive_segments/{predictiveSegmentId}/run
Train predictive scoring model (legacy)
predictiveSegment#run 2 params → 200
GET
/entities/segments/{id}/predictive_segments/guess_rule_async
Retrieve predictive scoring rules
1 param → 200
POST
/entities/predictive_segments
Create predictive scoring model
body → 200
GET
/entities/predictive_segments/{id}
Retrieve predictive scording model by ID
1 param → 200
PATCH
/entities/predictive_segments/{id}
Update predictive scoring model
1 param body → 200
DELETE
/entities/predictive_segments/{id}
Delete predictive scoring model
1 param → 200
POST
/entities/predictive_segments/{id}/run
Run predictive scoring model
1 param → 200
GET
/entities/predictive_segments/{id}/executions
Retrieve executions of predictive scoring model
1 param → 2004034045XX
GET
/entities/predictive_segments/{id}/model/features
Retrieve features of predictive scoring model
2 params → 200
GET
/entities/predictive_segments/{id}/model/columns
Retrieve columns of predictive scoring model
2 params → 200
GET
/entities/predictive_segments/{id}/model/score
Retrieve scores of predictive scoring model
1 param → 200

Schemas 27

The contract defines 27 schemas that model the data the API accepts and returns. The most detailed are PredictiveSegment (15 properties), PredictiveSegmentJsonApiResourceAttr (15 properties), PredictiveSegmentParameters (10 properties), ExecutionCore (5 properties). Each schema is shown below with its type and property counts.

UserJsonApiResource
object
3 properties 3 required
Execution
EntitiesPredictiveSegmentUpdateRepresentation
object
4 properties
EntitiesGetPredictiveSegmentModelColumnsJsonApiResult
object
1 property
PredictiveSegmentJsonApiResourceAttr
object
15 properties
RelationshipsFolderJsonApiResource
object
1 property
JsonApiPermissionError
object
4 properties 3 required
EntitiesGetPredictiveSegmentJsonApiResponse
object
2 properties 2 required
PredictiveSegmentExecutionCore
PredictiveSegmentPreprocessItem
object
2 properties 2 required
PredictiveSegmentAreaUnderRocCurve
numbernull
Evaluation score for the model. See also https://en.wikipedia.org/wiki/ReceiveroperatingcharacteristicAreaunderthecurve
PredictiveSegment
object
15 properties
EntitiesGetPredictiveSegmentExecutionJsonApiResponse
object
1 property 1 required
PredictiveSegmentModelScoreHistogram
array
EntitiesSegmentPredictiveSegmentGuessRuleAsyncJsonApiResult
object
1 property
PredictiveSegmentRule
object
4 properties
PredictiveSegmentParameters
object
10 properties
ExecutionCore
object
5 properties 5 required
EntitiesGetPredictiveSegmentModelFeaturesJsonApiResult
object
1 property
PredictiveSegmentGradeThresholds
array
Given the items [a, b, c], they must meet the condition a = b = c
PredictiveSegmentAccuracy
numbernull
Accuracy for trained model evaluated on initial training.
PredictiveSegmentExecutionJsonApiResource
object
3 properties 3 required
PredictiveSegmentExecution
JsonApiNotFoundError
object
3 properties 3 required
Error
object
2 properties 2 required
EntitiesGetPredictiveSegmentModelScoresJsonApiResult
object
1 property
FunctionExpression

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

treasure-data-predictive-segments-api-openapi.yml Raw ↑

Other APIs Treasure Data publishes across the network.

Treasure Data Bulk Loads API
Treasure Data User API
Treasure Data System API
Treasure Data Postback API
Treasure Workflow API
Treasure Data Bulk Import API
Treasure Data Bulk Loads API
Treasure Data Connectors API
Treasure Data Databases API
Treasure Data Jobs API
Treasure Data SSO API
Treasure Data System API
Where this information came from

This is an independent, third-party profile of Treasure Data Predictive Segments API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.