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

Customer.io Track API

The Customer.io Track API allows developers to send behavioral data and customer profile information into Customer.io. It provides endpoints for identifying customers, tracking events, managing devices for push notifications, and sending anonymous events. The API uses basic authentication with a Site ID and API key, and accepts JSON request bodies.

Customer.io Track API is one of 42 APIs that Customer.io publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Behavioral Data, Customer Data, Event Tracking, Marketing Automation, and Messaging. The published artifact set on APIs.io includes API documentation and an OpenAPI specification.

This API exposes 1 operation across 1 path, and defines 19 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://cdp.customer.io/v1, https://cdp-eu.customer.io/v1.

1 operations 1 paths 19 schemas 1 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://track.customer.io
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

Customer.io Track API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (Basic-Auth).

  • Basic-Auth — The Data Pipelines API uses a basic authentication scheme with your API key. Because basic authorization typically expects a username and password combination,…

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

Track 1
POST
/track
Track events
track 1 param body → 200

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are common_fields (8 properties), context_page (7 properties), context_common (5 properties), unsuppress_person (4 properties). Each schema is shown below with its type and property counts.

all_common_fields
context_page
object
Contains information about the current page in the browser. This is automatically collected by our JavaScript source.
7 properties
delete_device
object
Delete a device.
3 properties 3 required
context_mobile
A dictionary of context about a source call/event, like the user’s IP address or locale. Context is automatically collected by our source libraries.
integrations
object
Contains a list of booleans indicating the integrations that are enabled (true) or disabled (false). By default, all integrations are enabled (returning an emp…
unsuppress_person
object
Allow a userId to be added back to your Customer.io workspace.
4 properties 2 required
context_non_mobile
A dictionary of context about a source call/event, like the user’s IP address or locale. Context is automatically collected by our source libraries.
report_delivery_event
object
Reports delivery events for messages.
3 properties 2 required
create_update_device
object
Add or update a device. If a device (represented by device.token) exists, does not exist, we'll create it. If the device token already exists, we'll update the…
3 properties 3 required
track
anonymousId
string
A unique substitute for a User ID in cases when you don’t have an absolutely unique identifier. Our libraries generate this value automatically to help you tra…
delete_person
object
Remove a person from your Customer.io environment.
3 properties 2 required
context_common
object
Contains contextual information about the event.
5 properties
relationship_deleted
object
Remove a relationship between a person and an object in Customer.io.
3 properties 3 required
userId
string
The unique identifier for a person. This value should be unique across systems, so you recognize the same person in your sources and destinations.
group_deleted
object
Remove a group (also called an "object") from Customer.io Journeys.
3 properties 3 required
report_content_event
object
Reports impressions and clicks for anonymous messages.
3 properties 2 required
suppress_person
object
Remove a person from your Customer.io workspace and prevent them from being added back.
4 properties 2 required
common_fields
object
8 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

customer-io-track-api-openapi.yml Raw ↑

Other APIs Customer.io publishes across the network.

Customer.io Activities API
Customer.io Alias API
Customer.io Batch API
Customer.io Broadcasts API
Customer.io Campaigns API
Customer.io Collections API
Customer.io Customers API
Customer.io Exports API
Customer.io Group API
Customer.io Identify API
Customer.io Messages API
Customer.io Newsletters API
Where this information came from

This is an independent, third-party profile of Customer.io Track 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.