These APIs send source events—identify, track, group, etc—into Customer.io, where you can route them to downstream destinations. The Data Pipelines API even supports Journeys.
Journeys has three APIs. The Track API helps you identify and track people. The App API provides ways to trigger broadcasts and return information about people in your workspace. And reporting webhooks return information that shows how your messages perform.
Hover over an item on the right to reveal information about our Journeys APIs. Click an item to go to the API-reference.
Data Pipelines helps you send information from your website, apps, and other sources into all kinds of destinations without writing your own integrations. You can make simple calls to our API and set up actions in multiple downstream destinations—including Journeys!
You'll use the Track API to get data about People and Objects into both Journeys and Data Pipelines. The track API includes endpoints including, but not limited to:
You can use our Web SDK or our client libraries to take advantage of this API without writing your own requests from scratch.
You'll use our App API to integrate with your backend apps, hence the name. You can use this API to:
Our App API has two endpoints designed specifically to trigger messages:
Transactional messages represent information that your customer implicitly requests—like password reset requests, purchase receipts, and so on. You can pass your entire message to this endpoint, so you can both compose and trigger messages from your backend integration.
API-triggered broadcasts let you trigger a message from your app or a backend integration to an audience of people. For example, you might send a broadcast to a group of people interested in an event when tickets go on sale.
Reporting webhooks let you subscribe to specific channels and metrics, so that you can report information about message performance and how your audience responds to messages to your app asynchronously.
