API and MCP reference
Customer data platform (CDP) API and MCP reference
This customer data platform (CDP) API reference helps integration engineers identify the contracts to request for profiles, events and decisions. Public examples are planning material, not a substitute for release-specific authentication, schemas and limits.
Public scope and implementation access
This public page describes the integration contracts an evaluation should obtain. It is not an executable endpoint specification. No public API hostname, dashboard key workflow, batch limit or service availability guarantee is established here. The earlier illustrative paths have been removed because this repository does not provide the corresponding platform implementation contract.
Request the supported API description, authentication instructions and examples for the selected release through an architecture review. Availability and confidentiality terms must be confirmed for that scope. Do not send credentials or production customer payloads through the public review form.
Contract checklist
Profiles, events, decisions and MCP tools
Confirm supported operations, semantics and limits before writing an integration. A capability name is not evidence that an endpoint is implemented.
| Area | Contract to obtain | Acceptance evidence |
|---|---|---|
| Authentication | Issuer, token audience, scopes, expiry, rotation and revocation. | Demonstrate a permitted request, a denied request and a revoked credential. |
| Profiles and identity | Identifiers, merge rules, conflict handling, reads, updates and permitted deletion. | Reconcile a duplicate, changed identifier and restricted profile using synthetic records. |
| Events | Payload schema, event IDs, timestamps, batching, size limits and validation errors. | Test duplicates, late events, invalid fields and safe retry behavior. |
| Segments and decisions | Definition format, evaluation input, explainability and policy checks. | Compare an accepted result with denied or incomplete input; retain the policy version. |
| Audit export | Recorded operations, access permissions, retention, export and reconciliation. | Trace an authorized operation through the retained evidence and inspect restricted access. |
| MCP tools | Tool schemas, permitted operations, identity delegation and approval boundaries. | Show that a recommendation cannot exceed the operator permissions or bypass required approval. |
Test one complete integration
Use synthetic identities and record the release and configuration under test. Ingest one permitted event, inspect the resulting profile and run the intended decision or destination action. Then test an invalid payload, duplicate event, expired credential and unavailable dependency. Agree the retry and reconciliation process before treating an accepted request as a completed downstream effect.
Keep access and evidence in scope
Document source and destination permissions, audit retention and the operator responsible for recovery. An MCP tool must use the same authorization boundary as any other integration. For broader workflow planning, use the integration guide; deployment prerequisites belong in the deployment guide.
Synthetic MCP reference
Inspect the iAge MCP reference source and illustrative event schema. The local stdio server uses synthetic fixtures and checks trusted permissions separately from purpose consent. Its SDK stub requires a reviewed adapter; it is not a supported PrivyCDP production endpoint contract.
Discuss your deployment with engineers.
Bring your data flow, operating owners and evaluation questions.
Further reading
Published: · Updated:
Editorial dates describe content changes. Confirm current sources before making legal, security or purchasing decisions.