Customer.io API

Name: Customer.io API
Brand: Customer.io API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingMarketing Automationbasic21 EndpointsREST

Install Jentic One Beta

Connect the Customer.io API to your agent

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

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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.

Capabilities

What an agent can do with Customer.io API.

Identify and update customer profiles by customer_id with traits and timestamps

Track named events for an identified customer or anonymously to drive campaign triggers

Send transactional email through the /send/email endpoint with template and recipient data

GET STARTED

Start building with Customer.io API

Explore with Jentic

View OpenAPI Document

For Agents

Identify and track customers, send transactional email, manage devices, list campaigns and segments, and export delivery and customer data through Customer.io.

Use for: Identify a customer with their email and traits after signup, Track a 'subscription_renewed' event on a customer, Send a transactional password reset email through Customer.io, List all active campaigns and their performance metrics

Not supported: Does not handle SMS sending, push notification delivery payloads, or in-app messages - use for customer identification, event tracking, transactional email, and campaign metrics only.

Use Cases

Patterns agents use Customer.io API for, with concrete tasks.

★ Behavioural Email Automation

Drive lifecycle email campaigns from product behaviour by identifying customers and tracking events that match Customer.io campaign triggers. Use PUT /customers/{customer_id} to maintain the profile and POST /customers/{customer_id}/events to record actions like 'cart_abandoned' or 'trial_expired'. Integration takes a day or two compared with hand-rolling a behavioural messaging stack.

Call PUT /customers/{customer_id} with the user's email and signup_date, then POST /customers/{customer_id}/events with name='trial_started' to enrol them in the trial nurture campaign

Transactional Email Sending

Send transactional emails such as receipts, password resets, and confirmations through Customer.io's transactional API. POST /send/email accepts a transactional message ID, recipient, and template variables, so product teams can use the same provider for both lifecycle and transactional traffic.

Call POST /send/email with transactional_message_id for the password reset template, the user email, and a reset link variable

Campaign Performance Reporting

Pull campaign and newsletter metrics into a reporting dashboard or warehouse. GET /campaigns lists active campaigns, GET /campaigns/{campaign_id}/metrics returns send, open, click, and conversion counts, and GET /newsletters/{newsletter_id}/metrics covers one-off sends. Suitable for marketing analysts who want Customer.io performance alongside other channel metrics.

Call GET /campaigns to list campaign IDs, then GET /campaigns/{campaign_id}/metrics for each to populate a weekly performance dashboard

Customer Data Export

Export customer and delivery datasets for warehouse load, audit, or migration. POST /exports/customers and POST /exports/deliveries kick off async export jobs that return downloadable archives. Used by data teams running daily syncs or by ops teams preparing GDPR data subject access responses.

Call POST /exports/customers with the desired filter to start an export job, then poll GET /activities to confirm completion before downloading

AI Agent Messaging via Jentic

An AI agent automating customer communications uses Jentic to call Customer.io directly without bespoke integration code. The agent searches for 'send transactional email' or 'track customer event', loads the schema, supplies the parameters, and triggers the action.

Use Jentic to search 'send transactional email' and execute /send/email with the password reset template after a user requests a reset

Key Endpoints

21 endpoints — jentic publishes the only available openapi specification for customer.

METHOD

PATH

DESCRIPTION

PUT

/customers/{customer_id}

Identify or update a customer

POST

/customers/{customer_id}/events

Track a customer event

POST

/send/email

Send a transactional email

GET

/campaigns

List campaigns

GET

/campaigns/{campaign_id}/metrics

Get campaign metrics

POST

/exports/customers

Start a customer export job

POST

/customers/{customer_id}/suppress

Suppress a customer

GET

/segments

List segments

PUT

/customers/{customer_id}

Identify or update a customer

POST

/customers/{customer_id}/events

Track a customer event

POST

/send/email

Send a transactional email

GET

/campaigns

List campaigns

GET

/campaigns/{campaign_id}/metrics

Get campaign metrics

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Customer.io site ID and API 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 'send a transactional email' or 'track a customer event', and Jentic returns the matching Customer.io operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Customer.io API through Jentic.

Why is there no official OpenAPI spec for Customer.io API?

Customer.io does not publish a single canonical OpenAPI specification covering this surface. Jentic generates and maintains this spec so that AI agents and developers can call Customer.io 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 API use?

The API uses HTTP Basic authentication with a workspace site ID as the username and an 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 transactional email with the Customer.io API?

Yes. Call POST /send/email with a transactional_message_id, the recipient email, and any template variables. The endpoint is suitable for receipts, password resets, and one-off notifications.

What are the rate limits for the Customer.io API?

Rate limits depend on the Customer.io plan and the specific endpoint family; tracking endpoints generally accept higher throughput than App API endpoints. The spec does not encode exact numbers; check your workspace settings for current limits.

How do I track a customer event through Jentic?

Run pip install jentic, search for 'track customer event', load POST /customers/{customer_id}/events, and execute it with the event name and any properties. Jentic posts the event so it can drive campaign triggers.

How do I export delivery data from Customer.io?

Call POST /exports/deliveries to start an async export job. The response includes a job ID; poll GET /activities or use the deliveries export status to confirm completion before downloading the resulting archive.

Can I limit what my agent is allowed to do with the Customer.io API?

Yes. Because you run Jentic One yourself, your own rules decide which Customer.io operations and credentials the agent may use. Since the customer id sits in the URL path, such as /customers/{customer_id}/events, a rule can pin the agent to a single customer so it can update that profile and track its events but nothing else. You choose the operations it may call, so a suppress or a POST /exports/customers request is not available unless you explicitly add it.

Customer.io API

Connect the Customer.io API to your agent

Capabilities

Start building with Customer.io API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs