Customer.io Track API
Browse all Customer APIs39
AI ReadinessNon-Ready (F)39/100
Agent-ready OpenAPI document · curated by JenticMarketingMarketing Automationbasic16 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Ingest behavioural data into Customer.io: identify people, track events, manage devices, submit forms, suppress profiles, and send batched or v2 entity requests.
Use for: Identify a new signup with their email, name, and plan tier, Track an 'order_completed' event for an identified customer, Register a push device token for a mobile customer, Suppress a customer who has unsubscribed from all messaging
Not supported: Does not handle campaign creation, sending transactional email, or pulling reporting metrics - use for ingesting people, events, devices, and batched data only.
Jentic publishes the only available OpenAPI specification for Customer.io Track API, keeping it validated and agent-ready. The Track API is the data ingestion surface for Customer.io, used to add and update people, record events, manage devices, suppress profiles, submit forms, merge duplicates, and send batched requests. It also includes account region discovery and a v2 entity endpoint for unified ingestion. Authentication uses HTTP Basic with a site ID and tracking API key.
Install Jentic One Beta
Connect the Customer.io Track API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Customer.io Track API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcustomer.io%2Fcustomerio-track" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcustomer.io%2Fcustomerio-track" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Customer.io Track API.
Add or update people in Customer.io with traits and timestamps via PUT /api/v1/customers/{identifier}
Track named customer events or anonymous events to drive campaign triggers
Register and remove customer devices to enable push delivery
Suppress, unsuppress, or delete people for compliance and lifecycle hygiene
Submit forms, add or remove people from manual segments, and merge duplicate profiles
Send a batched payload of mixed identify, track, and device operations through /api/v2/batch
Use Cases
Patterns agents use Customer.io Track API for, with concrete tasks.
★ Server-Side Event Ingestion
Send identification and event data from a server-side application into Customer.io to drive campaigns. Use PUT /api/v1/customers/{identifier} for upsert, POST /api/v1/customers/{identifier}/events for attributed events, and POST /api/v1/events for anonymous traffic. Suitable for backend services that own the source of truth for user behaviour.
Call PUT /api/v1/customers/{identifier} with traits, then POST /api/v1/customers/{identifier}/events with name='checkout_completed' and properties for the order
Mobile Device Registration for Push
Register and rotate device tokens so Customer.io campaigns can deliver push notifications to mobile customers. Use PUT /api/v1/customers/{identifier}/devices to add or update a token and DELETE /api/v1/customers/{identifier}/devices/{device_id} to revoke it on logout or app uninstall.
Call PUT /api/v1/customers/{identifier}/devices with the FCM or APNs token after a user signs in on a new device
Batched Backfill or Sync
Backfill historical events or sync records from another system using POST /api/v1/segments/{segment_id}/add_customers for segment population, /api/v1/merge_customers for de-duplication, and POST /api/v2/batch for a high-throughput batched payload of mixed operations. Reduces request volume during one-off migrations and nightly syncs.
Construct a /api/v2/batch payload with 200 mixed identify and track requests and POST it in a single call during a nightly sync window
Compliance and Suppression Workflow
Honour unsubscribe, deletion, and data subject requests by suppressing or deleting profiles via the Track API. POST /api/v1/customers/{identifier}/suppress halts messaging, POST /api/v1/customers/{identifier}/unsuppress reverses it, and DELETE /api/v1/customers/{identifier} removes the profile.
Call POST /api/v1/customers/{identifier}/suppress when a customer submits an unsubscribe and DELETE /api/v1/customers/{identifier} on a verified deletion request
AI Agent Track Workflow via Jentic
An AI agent automating ingestion of customer signals uses Jentic to send identify and event payloads directly. The agent searches for 'track customer event', loads the operation, supplies the identifier and event name, and posts the event without bespoke integration glue.
Use Jentic to search 'track customer event' and execute /api/v1/customers/{identifier}/events for each row of an enrichment job's output
Key Endpoints
16 endpoints — jentic publishes the only available openapi specification for customer.
METHOD
PATH
DESCRIPTION
PUT
/api/v1/customers/{identifier}
Add or update a customer
POST
/api/v1/customers/{identifier}/events
Track a customer event
POST
/api/v1/events
Track an anonymous event
PUT
/api/v1/customers/{identifier}/devices
Register a customer device
POST
/api/v1/customers/{identifier}/suppress
Suppress a customer profile
POST
/api/v1/merge_customers
Merge duplicate customer profiles
POST
/api/v2/batch
Send a batched payload
GET
/api/v1/accounts/region
Find the workspace region
PUT
/api/v1/customers/{identifier}
Add or update a customer
POST
/api/v1/customers/{identifier}/events
Track a customer event
POST
/api/v1/events
Track an anonymous event
PUT
/api/v1/customers/{identifier}/devices
Register a customer device
POST
/api/v1/customers/{identifier}/suppress
Suppress a customer profile
POST
/api/v1/merge_customers
Merge duplicate customer profiles
POST
/api/v2/batch
Send a batched payload
GET
/api/v1/accounts/region
Find the workspace region
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
C
Customer.io Track API
- Non-Ready (F)39/100
82
Foundational Compliance63
Developer Experience & Jentic Compatibility43
AI-Readiness & Agent Experience94
Agent Usability10
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
82
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
30%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
43
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D-Signals: 4
26%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
94%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
52%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
10
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
10%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Customer.io Track API by hand means encoding a site ID and tracking key into a Basic auth header and choosing between the track.customer.io and track-eu.customer.io hosts for your region yourself. Through Jentic you install once, import the Customer.io Track API from the API Directory, store the credential pair once, and your agent calls it.
Permission scoping
Customer.io puts the person identifier in the URL path (/api/v1/customers/{identifier}/...), so a rule can pin your agent to one person: it can update that person and add their events. You choose the operations it may call, so a merge or suppress call is not included unless you add it.
Credential isolation
Your Customer.io site ID and tracking key are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'identify a person' or 'track an event', and Jentic returns the matching Track API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Customer.io Track API through Jentic.
Why is there no official OpenAPI spec for Customer.io Track API?
Customer.io does not publish a complete OpenAPI specification for the Track surface. Jentic generates and maintains this spec so that AI agents and developers can call Customer.io Track API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Customer.io Track API use?
The Track API uses HTTP Basic with a workspace site ID as the username and a tracking API key as the password. Through Jentic both values are held in the encrypted vault and injected into the Authorization header at call time.
Can I send batched events to the Customer.io Track API?
Yes. POST /api/v2/batch accepts an array of mixed identify, track, and device operations in a single request, useful for backfills and nightly syncs.
What are the rate limits for the Customer.io Track API?
Track endpoints accept high event throughput; specific limits depend on the Customer.io plan and are not encoded in the spec. Use /api/v2/batch for bulk loads to stay within per-request limits.
How do I find which region my Customer.io workspace is in through Jentic?
Run pip install jentic, search for 'find account region', load GET /api/v1/accounts/region, and execute it. Jentic returns the region (US or EU) so you can route subsequent calls to the right host.
How do I suppress a customer for GDPR compliance?
Call POST /api/v1/customers/{identifier}/suppress to stop messaging while keeping the profile. For full deletion call DELETE /api/v1/customers/{identifier}, which removes the profile and stops all subsequent processing.
Can I limit what my agent is allowed to do with the Customer.io Track API?
Yes. Jentic One runs self-hosted, so your own rules decide which Track API operations and credentials the agent may use. Because Customer.io puts the person identifier in the URL path (/api/v1/customers/{identifier}/...), you can pin the agent to update one person and record their events while excluding calls you never add, such as POST /api/v1/merge_customers or POST /api/v1/customers/{identifier}/suppress. The site ID and tracking key stay with your instance and are injected only for the operations you have allowed.
GET STARTED