How do I handle large data loads across the two APIs?

For high-volume ingestion use the Track API POST /api/v2/batch endpoint, which accepts an array of mixed identify, track, and device operations in one request. For extracting large datasets use the App API exports, which start async jobs for customer and delivery data that you download once complete.

Does Customer.io support US and EU regions?

Yes. Workspaces live in either the US or EU region, which determines the host your calls should target. The Track API exposes GET /api/v1/accounts/region to discover which region a workspace belongs to so subsequent calls route to the correct host.

Customer.io APIs for AI Agents

Q: Are these OpenAPI specifications official?

Customer.io does not publish canonical OpenAPI specifications covering these surfaces. Jentic generates and maintains both specs, validates them against the live API, and keeps them current so that agents and developers can call Customer.io through structured tooling.

MarketingMarketing AutomationJentic-Generated SpecsBasic authAgent Ready

customer.io·Developer portal → docs.customer.io

Customer.io API Catalog

2 APIs across 1 product group. All share one credential.

Marketing2

Customer.io APIIdentify and track customers, send transactional email, manage devices, list campaigns and segments, and export delivery and customer data through Customer.io.~21 endpoints Customer.io Track APIIngest behavioural data into Customer.io: identify people, track events, manage devices, submit forms, suppress profiles, and send batched or v2 entity requests.~16 endpoints

Which Customer.io API should I use?

I want to...	Use	Why
Add or update people, record events, or register push devices	Customer.io Track API	The Track API is the ingestion surface for identify, event, device, form, merge, and batched requests.
Send transactional email or pull campaign and newsletter metrics	Customer.io API	The App API covers transactional sends, campaign and newsletter metrics, segment listing, and data exports.
Identify a customer or track a single event	Customer.io Track API	Prefer the Track API for high-throughput ingestion; the App API also identifies and tracks but is broader than needed for pure ingestion.
Suppress, unsuppress, or delete a profile	Customer.io Track API	The Track API exposes suppression and deletion for compliance; the App API also suppresses if you already hold that surface.

Install Jentic One Beta

Connect the Customer.io APIs to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Customer.io APIs, 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.

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Customer.io by hand means encoding a site ID and key into a Basic auth header per surface, choosing the right regional track host, and mapping the customer, event, campaign, and export routes yourself. Through Jentic you install Jentic One once, add the Customer.io APIs from the Jentic directory, store the credential pairs once, and your agent calls them.

Permission scoping

Customer.io puts the person identifier in the URL path across both surfaces (/customers/{customer_id}/... and /api/v1/customers/{identifier}/...), so your own rules in Jentic One can pin an agent to one person and let it identify, track, and register devices while withholding suppress, delete, merge, or export operations unless you add them.

Credential isolation

FAQs

Specific to using Customer.io APIs through Jentic.

What is the difference between the Customer.io API and the Track API?

The Track API is the data-ingestion surface: it identifies people, records attributed and anonymous events, manages push devices, submits forms, merges duplicates, suppresses profiles, and sends batched or v2 entity requests. The Customer.io API is the broader App surface: it lists campaigns and segments, returns campaign and newsletter metrics, starts customer and delivery exports, and sends transactional email. Most automations write signals through the Track API and read or send through the App API.

Do both Customer.io APIs use the same credentials?

Both use HTTP Basic with a workspace site ID and an API key, but the key differs by surface. The Track API expects a tracking API key while the App API expects an App API key, so you provide the matching pair for each surface you call.

Which API should an agent use to send email?

Use the Customer.io API. Transactional sends go through its POST /send/email endpoint with a transactional message ID, recipient, and template variables. The Track API does not send email; it only ingests the behavioural data that can trigger a campaign to send.

Are these OpenAPI specifications official?

BOOK A DEMO

Start Connecting APIs to Your AI Agents

Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.

Book a Demo

For Agents

APIs2 in catalogue

Endpoints37 indexed

AuthBasic auth — 1 credential for all 2 APIs

ProvenanceJentic-generated specs

An agent can ingest behavioural data into Customer.io by identifying people, tracking events, registering push devices, and sending batched payloads, then act on that data by sending transactional email, pulling campaign and newsletter metrics, exporting customer and delivery datasets, and managing suppression across the App and Track APIs.

Customer.io pairs a high-throughput ingestion surface for people, events, and devices with an App API for campaign metrics, exports, and transactional email, so the same platform owns both the behavioural data and the messaging it triggers. Its identifier-in-path routing makes it straightforward to scope automation to a single customer.

Use for: Ingesting people, events, and devices into Customer.io and acting on that data through transactional email, campaign and newsletter metrics, segment listing, exports, and suppression

Not supported: campaign authoring, SMS sending, in-app messages, push payload delivery, workflow builder editing

Credentials: Both APIs use HTTP Basic authentication with a workspace site ID as the username and an API key as the password, though the App API expects an App API key while the Track API expects a tracking API key, so the credential pair differs by surface.

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" | sh

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" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

What AI Agents Can Do with Customer.io

Each workflow spans multiple Customer.io APIs. Jentic routes each operation to the right API automatically.

Ingest behaviour then trigger transactional email

Identify a customer and track an event through the Track API to drive a campaign trigger, then send a related transactional email through the App API. The Track API records the signal and the App API sends the receipt, reset, or confirmation off the back of it.

Example prompt:

Call PUT /api/v1/customers/{identifier} and POST /api/v1/customers/{identifier}/events on the Track API, then POST /send/email on the App API with the matching transactional template

APIs used

Customer.io Track API + Customer.io API

Track events and report on campaign performance

Feed behavioural events into Customer.io through the Track API so campaigns fire, then pull the resulting campaign and newsletter metrics through the App API to populate a reporting dashboard. This closes the loop from signal ingestion to performance measurement.

Example prompt:

Post events via POST /api/v1/customers/{identifier}/events on the Track API, then call GET /campaigns and GET /campaigns/{campaign_id}/metrics on the App API for a weekly report

APIs used

Customer.io Track API + Customer.io API

Bulk backfill then export for audit

Backfill historical people and events through the Track API batch endpoint during a migration, then start a customer or delivery export through the App API to verify the load or produce an audit archive. Ingestion and export live on separate surfaces but combine into one migration workflow.

Example prompt:

POST a mixed payload to /api/v2/batch on the Track API, then POST /exports/customers on the App API and poll GET /activities until the export completes

APIs used

Customer.io Track API + Customer.io API

Compliance suppression with delivery evidence

Honour an unsubscribe or deletion request by suppressing or deleting a profile through the Track API, then export delivery data through the App API to document what was sent before the request. This produces a defensible record for data subject requests.

Example prompt:

Call POST /api/v1/customers/{identifier}/suppress on the Track API, then POST /exports/deliveries on the App API to archive prior sends for the record

APIs used

Customer.io Track API + Customer.io API

Customer.io APIs for AI Agents

Customer.io API Catalog

Marketing2

Which Customer.io API should I use?

Connect the Customer.io APIs to your agent

Why Jentic?

FAQs

Start Connecting APIs to Your AI Agents

What AI Agents Can Do with Customer.io

If you need a different Marketing vendor