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 Customers API

Add, modify, suppress, or unsuppress people (referred to as "customers" in our APIs). You can also use these endpoints to set attributes on people.

Customer.io Track Customers 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 Track Customers. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 8 operations across 7 paths, and defines 11 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

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

8 operations 7 paths 11 schemas 2 DELETE4 POST2 PUT

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 Customers API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (Tracking-API-Key).

  • Tracking-API-Key — The Track API uses a basic authentication scheme. Your credentials are your Site ID and your API key, Base-64 encoded in the format siteid:apikey. You can find…

Paths & Operations 8

Across 7 paths, the API surfaces 8 operations — 2 DELETE, 4 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Track Customers 8

Add, modify, suppress, or unsuppress people (referred to as "customers" in our APIs). You can also use these endpoints to set attributes on people.

PUT
/api/v1/customers/{identifier}
Add or update a customer
identify 1 param body → 200401
DELETE
/api/v1/customers/{identifier}
Delete a customer
delete 1 param → 200401
PUT
/api/v1/customers/{identifier}/devices
Add or update a customer device
add_device 1 param body → 200400401
DELETE
/api/v1/customers/{identifier}/devices/{device_id}
Delete a customer device
delete_device 2 params → 200400401
POST
/api/v1/customers/{identifier}/suppress
Suppress a customer profile
suppress 1 param → 200401
POST
/api/v1/customers/{identifier}/unsuppress
Unsuppress a customer profile
unsuppress 1 param → 200401
POST
/unsubscribe/{delivery_id}
Custom unsubscribe handling
unsubscribe 1 param body → 200400
POST
/api/v1/merge_customers
Merge duplicate people
merge body → 200400401

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are device_object_common (3 properties), v1_cio_relationships (2 properties), object_identifiers (1 property). Each schema is shown below with its type and property counts.

object_relationships
array
Each object in the array represents a relationship you want to add to, or remove from, a person.
not_nullable_customer_id
string
The ID of a customer profile, analogous to a "person" in the UI.
device_object
Device properties collected by [Customer.io SDKs](/integrations/sdk/) unless autoTrackDeviceAttributes is disabled. You can use these properties in segments an…
cio_id
string
A unique identifier set by Customer.io, used to reference a person if you want to update their identifiers.
v1_cio_relationships
object
Describes relationships to an entity—a non-person object in Customer.io, like a company, educational course, job board, etc.
2 properties
object_identifiers
object
1 property
relationship_attributes
object
The attributes associated with a relationship. Passing null or an empty string removes the attribute from the relationship.
device_object_common
object
Device information common to the v1 and v2 APIs.
3 properties 1 required
object_type_id
string
The object type an object belongs to—like "Companies" or "Accounts". Object type IDs are string-formatted integers that begin at 1 and increment for each new t…
anonymous_id
string
An identifier for an anonymous event, like a cookie. If set as an attribute on a person, any events bearing the same anonymous value are associated with this p…
not_nullable_email_address
string
The email address of the customer.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Customer.io publishes across the network.

Customer.io Track API
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
Where this information came from

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