Marketing Automation
Customer.io
API integration
Ship Marketing Automation features without building the integration. Full Customer.io API access via Proxy, normalized data through Unified APIs, and 230+ MCP-ready tools for AI agents — all extensible to your exact use case.
Talk to usUse Cases
Why integrate with Customer.io
Common scenarios for SaaS companies building Customer.io integrations for their customers.
Sync billing events to trigger automated dunning campaigns
Subscription and billing platforms can push payment failure events and account status changes into their customers' Customer.io workspaces, enabling marketers to build omnichannel dunning journeys without developer intervention.
Power lifecycle marketing with real-time product behavior data
Product-led SaaS companies can pipe behavioral events like feature adoption milestones or onboarding completions directly into Customer.io, letting their users' marketing teams build triggered campaigns based on what users actually do in the product.
Surface email engagement data inside customer success dashboards
CS platforms can pull message delivery, open, and click data from Customer.io so account managers see the full picture of marketing touchpoints before renewal conversations — without switching tools.
Sync audience cohorts for targeted in-app and email campaigns
Analytics and engagement platforms can push dynamically computed user segments into Customer.io, giving marketers precise audience targeting for campaigns without manual list uploads.
Keep contact profiles enriched with live SaaS platform attributes
Any B2B SaaS can continuously upsert user attributes like health scores, plan tiers, or usage metrics into Customer.io contacts, ensuring marketers always segment on fresh, accurate data.
What You Can Build
Ship these features with Truto + Customer.io
Concrete product features your team can ship faster by leveraging Truto’s Customer.io integration instead of building from scratch.
Bi-directional contact and attribute sync
Continuously upsert user profiles with custom attributes like MRR, plan tier, and last activity date into your customers' Customer.io workspaces, and read contact data back for display in your own UI.
Behavioral event forwarding engine
Push named product events (e.g., invoice_failed, feature_activated) from your platform into Customer.io so end users can use them as journey entry triggers without writing code.
Campaign and message engagement timeline
Fetch message-level delivery, open, click, and unsubscribe metrics from Customer.io and render them as a native activity timeline or ROI dashboard inside your product.
Segment audience sync
Create and update Customer.io segments from cohorts defined in your platform, enabling marketers to target precise user groups for campaigns without manual CSV imports.
Workspace-aware environment routing
Read workspace metadata from Customer.io to let end users map your platform's staging and production environments to the correct Customer.io workspace during setup.
Transactional message trigger with dynamic variables
Let your users fire API-triggered transactional emails or SMS through Customer.io, passing custom Liquid variables like secure links or invoice amounts at send time.
SuperAI
Customer.io AI agent tools
Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.
list_all_customer_io_campaigns
List automations. Returns a list of your automations and associated metadata.
get_single_customer_io_campaign_by_id
Get an automation. Returns metadata for an individual automation.
customer_io_campaigns_get_metrics
Get automation metrics. Returns metrics for an individual automation as a series of counts, oldest first—the 0-index of any result is the oldest point in the window. **We recommend version 2. Send `version=2`.** It accepts an… Required: campaign_id.
customer_io_campaigns_get_link_metrics
Get automation link metrics. Returns metrics for link clicks within an automation, both in total and in `series` periods (days, weeks, etc). `series` metrics are ordered oldest to newest (i.e. the 0-index for any result is the… Required: campaign_id.
customer_io_campaigns_get_journey_metrics
Get automation journey metrics. Returns a list of Journey Metrics for your automation. These metrics show how many people triggered your automation, were messaged, etc for the time period and "resolution" you set. You must… Required: campaign_id, start, end.
list_all_customer_io_campaign_actions
List automation actions. Returns the operations in an automation workflow. Each object in the response represents an action or 'tile' in the automation builder. This endpoint returns up to 10 `actions` at a time. If there is… Required: campaign_id.
get_single_customer_io_campaign_action_by_id
Get an automation action. Returns information about a specific action in an automation. Required: campaign_id.
update_a_customer_io_campaign_action_by_id
Update an automation action. Update the contents of an automation action, including the body of messages and HTTP requests. **NOTE**: You can't manage content made with Design Studio with this endpoint. Use the Design Studio… Required: campaign_id.
customer_io_campaign_actions_get_translation
Get a translation of an automation message. Returns a translated version of a message in an automation. The message is identified by the `action_id`. Required: campaign_id, action_id, language.
customer_io_campaign_actions_update_translation
Update a translation of an automation message. Update the contents of a language variant of an automation action, including the body of the messages and HTTP requests. **NOTE**: You can't manage content made with Design Studio… Required: campaign_id, action_id, language.
customer_io_campaign_actions_get_metrics
Get automation action metrics. Returns metrics for an individual action, both in total and as a series of counts, oldest first—the 0-index of any result is the oldest point in the window. **We recommend version 2. Send… Required: campaign_id, action_id.
customer_io_campaign_actions_get_link_metrics
Get link metrics for an action. Returns link click metrics for an individual action. Unless you specify otherwise, the response contains data for the maximum period by days (45 days). You cannot request fewer than 2 steps of… Required: campaign_id, action_id.
list_all_customer_io_customers
Search for customers. Provide a filter to search for people in your workspace. Your filter can filter people by segment (using the Segment ID) and attribute values; when you filter by attributes, you can use `eq` (matching an… Required: filter.
customer_io_customers_list_by_email
Get customers by email. Return a list of people in your workspace matching an email address. If the email contains special characters like `+`, make sure you percent-encode them in the query parameter. For example, use… Required: email.
customer_io_customers_get_attributes
Lookup a customer's attributes. Return a list of attributes for a customer profile. You can use attributes to fashion segments or as liquid merge fields in your messages. Required: customer_id.
customer_io_customers_get_attributes_bulk
List customers, attributes, and devices. Return attributes and devices for up to 100 customers by ID. If an ID in the request does not exist, the response omits it. Required: ids.
customer_io_customers_get_subscription_preferences
Lookup a customer's subscription preferences. Returns a list of subscription preferences for a person, including the custom header of the subscription preferences page, topic names, and topic descriptions. Returns translated… Required: customer_id.
customer_io_customers_update_optouts
Update a customer's opt-outs. Opt a person out of, or back in to, specific senders and channels. Provide one entry per sender/channel in the `optouts` array. Set `optout` to `true` to opt the person out of a sender, or `false`… Required: optouts, customer_id.
list_all_customer_io_segment_customers
List customers in a segment. Returns customers in a segment. This endpoint returns an array of `identifiers`; each object in the array represents a person and contains the identifier values allowed in your workspace. In… Required: segment_id.
list_all_customer_io_segments
List segments. Retrieve a list of your segments. The list doesn't include archived segments.
get_single_customer_io_segment_by_id
Get a segment. Return information about a segment.
create_a_customer_io_segment
Create a manual segment. Create a manual segment with a name and a description. This request creates an empty segment. You can't create a data-driven or snapshot segment with this endpoint. Required: segment.
delete_a_customer_io_segment_by_id
Delete a segment. Delete a manual segment. You can't delete a data-driven or snapshot segment with this request. You also can't delete a manual segment used in another segment, an automation, an unsent one-time send, or a SQL…
customer_io_segments_get_dependencies
Get a segment's dependencies. Use this endpoint to find out which automations and one-time sends use a segment. Required: segment_id.
customer_io_segments_get_customer_count
Get a segment customer count. Returns the membership count for a segment. Required: segment_id.
list_all_customer_io_broadcasts
List broadcasts. Returns a list of your API-triggered broadcasts and associated metadata.
customer_io_broadcasts_trigger
Send an API-triggered broadcast. Trigger a broadcast and optionally provide data to populate liquid placeholders in the message. To trigger one-time send broadcasts, use the one-time send endpoint. Broadcasts are optimized to… Required: broadcast_id, and exactly one of ids/emails/recipients/per_user_data/data_file_url.
get_single_customer_io_broadcast_by_id
Get a broadcast. Returns metadata for an individual broadcast.
customer_io_broadcasts_get_metrics
Get broadcast metrics. Returns a list of metrics for an individual broadcast in `steps` (days, weeks, etc). We return metrics from oldest to newest (i.e. the 0-index for any result is the oldest step/period). You cannot… Required: broadcast_id.
customer_io_broadcasts_get_link_metrics
Get broadcast link metrics. Returns metrics for link clicks within a broadcast, both in total and in `series` periods (days, weeks, etc). `series` metrics are ordered oldest to newest (i.e. the 0-index for any result is the… Required: broadcast_id.
list_all_customer_io_broadcast_actions
List broadcast actions. Returns the actions that occur as a part of a broadcast. If a message block contains multiple languages, this endpoint returns an object for each language variant. Each language variant includes the… Required: broadcast_id.
get_single_customer_io_broadcast_action_by_id
Get a broadcast action. Returns information about a specific action within a broadcast. Required: broadcast_id.
update_a_customer_io_broadcast_action_by_id
Update a broadcast action. Update the contents of a broadcast action, including the body of messages or HTTP requests. **NOTE** You cannot manage content made with Design Studio with this endpoint. Use the Design Studio APIs… Required: broadcast_id.
customer_io_broadcast_actions_get_translation
Get a translation of a broadcast message. Returns information about a translation of message in a broadcast. The message is identified by the `action_id`. Required: broadcast_id, action_id, language.
customer_io_broadcast_actions_update_translation
Update a translation of a broadcast message. Update a translation of a specific broadcast action, including the body of messages or HTTP requests. **NOTE** You cannot manage content made with Design Studio with this endpoint.… Required: broadcast_id, action_id, language.
customer_io_broadcast_actions_get_metrics
Get broadcast action metrics. Returns a list of metrics for an individual action both in total and in `steps` (days, weeks, etc) over a period of time. Stepped `series` metrics return from oldest to newest (i.e. the 0-index… Required: broadcast_id, action_id.
customer_io_broadcast_actions_get_link_metrics
Get broadcast action link metrics. Returns link click metrics for an individual broadcast action. Unless you specify otherwise, the response contains data for the maximum period by days (45 days). You cannot request fewer than… Required: broadcast_id, action_id.
list_all_customer_io_broadcast_triggers
Get broadcast triggers. Returns a list of the `triggers` for a broadcast. Required: broadcast_id.
customer_io_broadcast_triggers_cancel
Cancel a scheduled broadcast. Cancel a trigger you scheduled with `scheduled_at`, before it fires. The request fails if the broadcast has started calculating its audience, is already sending, or has already sent. A trigger… Required: broadcast_id, trigger_id.
customer_io_broadcast_triggers_list_errors
Get broadcast error descriptions. If your broadcast produced validation errors, this endpoint can help you better understand what went wrong. Broadcast errors are generally issues in your broadcast audience and associated. Required: broadcast_id, trigger_id.
get_single_customer_io_broadcast_trigger_by_id
Get the status of a broadcast. After triggering a broadcast you can retrieve the status of that broadcast using a GET of the `trigger_id`. You can retrieve the `trigger_id` from Get broadcast triggers. Required: broadcast_id.
list_all_customer_io_activities
List activities. This endpoint returns a list of "activities" for people, similar to your workspace's Activity Logs. This endpoint is guaranteed to return activity history within the past 30 days. It _might_ return data older…
list_all_customer_io_collections
List your collections. Returns a list of all of your collections, including the `name` and `schema` for each collection.
create_a_customer_io_collection
Create a collection. Create a new collection and provide the `data` that you'll access from the collection or the `url` that you'll download CSV or JSON data from. **Note**: A collection that you upload or send in an API… Required: data, name.
get_single_customer_io_collection_by_id
Lookup a collection. Retrieves details about a collection, including the `schema` and `name`. This request does not include the `content` of the collection (the values associated with keys in the schema).
delete_a_customer_io_collection_by_id
Delete a collection. Remove a collection and its contents. You can't delete a collection that an automation or broadcast queries, including an archived one, because you could unarchive it later. Remove the collection from…
update_a_customer_io_collection_by_id
Update a collection. Update the `name` or replace the contents of a collection. Updating the `data` or `url` for your collection fully replaces the contents of the collection. To set or change the collection's key field or…
customer_io_collections_get_contents
Lookup collection contents. Retrieve the rows of a collection. Without query parameters, this request returns the whole collection as JSON Lines: each line of the response is one row, as a JSON object. If a collection is too… Required: collection_id.
customer_io_collections_update_contents
Update the contents of a collection. Replace the contents of a collection (the `data` from when you created or updated a collection). Send the rows as a JSON array of objects, or as CSV with a `Content-Type` of `text/csv`.… Required: collection_id.
customer_io_collections_start_sync
Sync a collection from a source. Watch a folder in one of your collection sources, and have Customer.io load each new file in the folder into the collection. Customer.io saves and deletes rows by key, the same way as a write… Required: source_id, collection_id.
customer_io_collections_get_sync
Look up a collection's sync. Returns the collection's sync, including the last file Customer.io loaded and the last error. Required: collection_id.
customer_io_collections_stop_sync
Stop a collection's sync. Stop loading files into the collection, and delete the sync's rejected rows. Rows that the sync already loaded stay in the collection. Required: collection_id.
customer_io_collections_poll_sync
Check a sync's folder now. Check the sync's folder for new files now, instead of waiting for the next scheduled check. If a check is already running, Customer.io doesn't start another. Customer.io responds right away, before… Required: collection_id.
list_all_customer_io_messages
List messages. Return a list of deliveries, including metrics for each delivery, for messages in your workspace. The request body contains filters determining the deliveries you want to return information about. Use the…
get_single_customer_io_message_by_id
Get a message. Return a information about, and metrics for, a delivery—the instance of a message intended for an individual recipient person.
customer_io_messages_get_archived
Get an archived message. Returns the archived copy of a delivery, including the message body, recipient, and metrics. This endpoint is limited to 100 requests per day. Required: message_id.
list_all_customer_io_newsletters
List one-time sends. Returns a list of your one-time sends (referred to as "newsletters" in our APIs) and associated metadata.
get_single_customer_io_newsletter_by_id
Get a one-time send. Returns metadata for an individual one-time send (referred to as a "newsletter" in our APIs).
customer_io_newsletters_send
Trigger a one-time send. Trigger a one-time send (referred to as a "newsletter" in our APIs) immediately. It must be in a draft state. If it has already been sent, you'll get a `400` error. The recipients are fixed when you… Required: newsletter_id.
customer_io_newsletters_schedule
Schedule a one-time send. Schedule a one-time send (referred to as a "newsletter" in our APIs) to send at a specific time. It must be in a draft state. If it has already been sent, you'll get a `400` error. If it's already… Required: scheduled_at, newsletter_id.
create_a_customer_io_newsletter
Create and send a one-time send. Create a one-time send (referred to as a "newsletter" in our APIs) and optionally schedule it or send it immediately. Set the audience with either `recipients` (a filter over segments and… Required: body, subject, type, name.
delete_a_customer_io_newsletter_by_id
Delete a one-time send. Deletes an individual one-time send (referred to as a "newsletter" in our APIs), including content, settings, and metrics. It will be removed from segments, and its templates will no longer show in the…
customer_io_newsletters_get_metrics
Get one-time send metrics. Returns a list of metrics for an individual one-time send (referred to as a "newsletter" in our APIs) in `steps` (days, weeks, etc). We return metrics from oldest to newest (i.e. the 0-index for any… Required: newsletter_id.
customer_io_newsletters_get_link_metrics
Get click metrics for one-time send links. Returns metrics for link clicks within a one-time send (referred to as a "newsletter" in our APIs), both in total and in `series` periods (days, weeks, etc). `series` metrics are… Required: newsletter_id.
customer_io_newsletters_create_translation
Add a translation to a one-time send. Add a language variant to a one-time send (referred to as a "newsletter" in our APIs). If you omit optional fields, the values from the default template are copied over untranslated. Make… Required: body, language, subject, newsletter_id.
customer_io_newsletters_get_translation
Get a one-time send translation. Returns information about a specific language variant of a one-time send (referred to as a "newsletter" in our APIs). If it includes A/B tests, use Get a translation in a one-time send test group. Required: newsletter_id, language.
customer_io_newsletters_update_translation
Update a translation of a one-time send. Update the translation of a one-time send (referred to as a "newsletter" in our APIs) variant. If it includes A/B tests, use Update a translation in a one-time send test group.… Required: newsletter_id, language.
customer_io_newsletters_delete_translation
Delete a translation of a one-time send. Delete a specific language variant of a one-time send (referred to as a "newsletter" in our APIs). You cannot delete the default language variant. If it has already been sent, you… Required: newsletter_id, language.
list_all_customer_io_newsletter_variants
List one-time send variants. Returns a one-time send's content variants (a one-time send is referred to as a "newsletter" in our APIs)—these are either different languages in a multi-language one-time send or A/B tests. Required: newsletter_id.
get_single_customer_io_newsletter_variant_by_id
Get a one-time send variant. Returns information about a specific variant of a one-time send (referred to as a "newsletter" in our APIs), where a variant is either a language in a multi-language one-time send or a part of an… Required: newsletter_id.
update_a_customer_io_newsletter_variant_by_id
Update a one-time send variant. Update the content of a one-time send (referred to as a "newsletter" in our APIs): the default message, a test variant in an A/B test group, or a translation. For an email, you can also update… Required: newsletter_id.
customer_io_newsletter_variants_get_metrics
Get metrics for a test or translation variant of a one-time send. Returns a metrics for an individual one-time send (referred to as a "newsletter" in our APIs) variant—either an individual language in a multi-language one-time… Required: newsletter_id, content_id.
customer_io_newsletter_variants_get_link_metrics
Get click metrics for links in one-time send variants. Returns link click metrics for an individual one-time send (referred to as a "newsletter" in our APIs) variant—an individual language in a multi-language one-time send or… Required: newsletter_id, content_id.
list_all_customer_io_newsletter_test_groups
List a one-time send's A/B test groups. Returns information about each test group in a one-time send (referred to as a "newsletter" in our APIs), including content ids for each group. Required: newsletter_id.
create_a_customer_io_newsletter_test_group
Create an A/B test group for a one-time send. Create a new A/B test group for a one-time send (referred to as a "newsletter" in our APIs). This duplicates the existing one-time send's content into a new test group, allowing… Required: newsletter_id.
customer_io_newsletter_test_groups_create_translation
Add a translation to a one-time send test group. Add a language variant to a specific A/B test group in a one-time send (referred to as a "newsletter" in our APIs). The new variant is a copy of the default template in the test… Required: body, language, subject, newsletter_id, test_group_id.
customer_io_newsletter_test_groups_get_translation
Get a translation in a one-time send test group. Returns information about a specific language variant of a one-time send (referred to as a "newsletter" in our APIs) in an A/B test group. You can retrieve `test_group_ids` from… Required: newsletter_id, test_group_id, language.
customer_io_newsletter_test_groups_update_translation
Update a translation in a one-time send test group. Update the translation of a one-time send (referred to as a "newsletter" in our APIs) variant in an A/B test. You can retrieve a list of `test_group_ids` from List a one-time… Required: newsletter_id, test_group_id, language.
customer_io_newsletter_test_groups_delete_translation
Delete a translation in a one-time send test group. Delete a specific language variant of a one-time send (referred to as a "newsletter" in our APIs) in an A/B test group. You cannot delete the default language variant. If it… Required: newsletter_id, test_group_id, language.
list_all_customer_io_object_types
List object types. Returns a list of object types in your system. Because each object type is an incrementing ID, you may need to use this endpoint to find the ID of the object type you want to query, create, or modify.
list_all_customer_io_sender_identities
List sender identities. Returns a list of senders in your workspace. Senders are who your messages are "from".
get_single_customer_io_sender_identity_by_id
Get a sender. Returns information about a specific sender.
customer_io_sender_identities_get_usage
Get sender usage data. Returns lists of the automations and one-time sends that use a sender. Required: sender_id.
list_all_customer_io_snippets
List snippets. Returns a list of snippets in your workspace. Snippets are pieces of reusable content, like a common footer for your emails.
create_a_customer_io_snippet
Create a snippet. Create a new snippet. If a snippet with that name already exists, we'll return a `422` error. If the value contains Liquid, we validate it. Required: name, value.
customer_io_snippets_upsert
Update snippets. In your payload, you'll pass a `name` and `value`. Snippet names are unique. If the snippet `name` does not exist, we'll create a new snippet. If the `name` exists, we'll update the existing snippet. Required: name, value.
delete_a_customer_io_snippet_by_id
Delete a snippet. Remove a snippet. You can only remove a snippet that is not in use. If your snippet is in use, you'll receive a `400` error.
list_all_customer_io_subscription_topics
List subscription topics. Returns a list of subscription topics in your workspace. If there are no topics, it returns an empty array.
list_all_customer_io_transactional_messages
List transactional messages. Returns a list of your transactional messages—the transactional IDs that you use to trigger an individual transactional delivery. This endpoint does not return information about deliveries…
get_single_customer_io_transactional_message_by_id
Get a transactional message. Returns information about an individual transactional message.
customer_io_transactional_messages_get_translation
Get a translation of a transactional message. Returns information about a translation of an individual transactional message, including the message content. To look up a translation by its id instead of its language, see Get a… Required: transactional_id, language.
customer_io_transactional_messages_update_translation
Update a translation of a transactional message. Update the body and other data of a specific language variant for a transactional message. This fully overwrites this specific translation of your existing transactional… Required: transactional_id, language.
customer_io_transactional_messages_get_metrics
Get transactional message metrics. Returns a list of metrics for a transactional message in `steps` (days, weeks, etc). We return metrics from oldest to newest (i.e. the 0-index for any result is the oldest step/period). You… Required: transactional_id.
customer_io_transactional_messages_get_link_metrics
Get transactional message link metrics. Returns metrics for clicked links from a transactional message, both in total and in `series` periods (days, weeks, etc). `series` metrics are ordered oldest to newest (i.e. the 0-index… Required: transactional_id.
list_all_customer_io_transactional_message_variants
List all variants of a transactional message. Returns the content variants of a transactional message, where each variant represents a different language. Required: transactional_id.
update_a_customer_io_transactional_message_variant_by_id
Update a transactional message. Update the body of a transactional email. This fully overwrites your existing transactional message. We'll use your updated content for any future transactional requests (`/v1/send/email`), so… Required: transactional_id.
get_single_customer_io_transactional_message_variant_by_id
Get a translation of a transactional by ID. Returns an individual translation variant of a transactional message, including the message content. To look up a translation by its language instead of its id, see Get a translation… Required: transactional_id.
list_all_customer_io_workspaces
List workspaces. Returns a list of workspaces in your account.
customer_io_live_notifications_start
Start a live notification. Start a live notification for a profile. Customer.io mints an `instance_id` for the new activity and returns it. You'll use this ID to update, end, or check the status of the activity. On iOS, this… Required: attributes, content_state, identifiers, notification_type.
customer_io_live_notifications_update_notification
Update a live notification. Push a new content state to a running activity, referenced by its `instance_id`. The device re-renders the activity from the state you send. Send the **full** content state on every update, not just… Required: content_state, instance_id.
customer_io_live_notifications_end
End a live notification. End a running activity, referenced by its `instance_id`. On iOS, the system dismisses the activity from the Lock Screen. On Android, the SDK normally renders the final content as a non-ongoing… Required: instance_id.
get_single_customer_io_live_notification_by_id
Get a live notification's status. Look up a live notification's current state, lifecycle timestamps, and the status of its most recent delivery.
customer_io_transactional_sends_send_email
Send a transactional email. Send a transactional email. While not strictly required, we recommend that you include a `transactional_message_id` in your request. If you don't, Customer.io attributes metrics to… Required: to.
customer_io_transactional_sends_send_in_app
Send a transactional in-app message. Send a transactional in-app message. In-app messages render in your application through the Customer.io SDK to the devices associated with the person you target by `identifiers`. You send a… Required: identifiers, transactional_message_id.
customer_io_transactional_sends_send_inbox_message
Send a transactional inbox message. Send a transactional inbox message. Inbox messages deliver raw JSON payloads to your application through our JavaScript SDK, allowing you to build custom notification centers, message feeds,… Required: identifiers, transactional_message_id.
customer_io_transactional_sends_send_push
Send a transactional push. Send a transactional push. You send a message using a `transactional_message_id` for a transactional push message template composed in the user interface. You can optionally override any of the… Required: identifiers, transactional_message_id.
customer_io_transactional_sends_send_sms
Send a transactional SMS. Send a transactional SMS message. To send a message, you'll need to provide a `transactional_message_id`. This is either the numerical ID of your transactional message template or the *Trigger Name*… Required: identifiers, to, transactional_message_id.
customer_io_transactional_sends_send_whatsapp
Send a transactional WhatsApp message. Send a transactional WhatsApp message. To use this endpoint, you must be integrated with WhatsApp Business, not Twilio. Then you need to create the template in the UI and have it approved… Required: identifiers, to, transactional_message_id.
list_all_customer_io_campaign_messages
Get automation message metadata. Returns information about the deliveries (instances of messages sent to individual people) sent from an automation. Provide query parameters to refine the metrics you want to return. Use the… Required: campaign_id.
list_all_customer_io_assets
List file assets. Returns a paginated list of file assets. Supports filtering by parent folder and choosing between direct children or the entire folder subtree.
create_a_customer_io_asset_file
Create a file asset. Creates a new file asset. Accepted file types: `image/bmp`, `image/jpeg`, `image/jpg`, `image/png`, `image/gif`, `application/pdf`. Maximum file size: 2 MB. Maximum image dimensions: 4096px. Required: file.
get_single_customer_io_asset_file_by_id
Get a file asset. Retrieves a single file asset by its ID. Returns 404 if the asset does not exist or is a folder.
update_a_customer_io_asset_file_by_id
Update a file asset. Updates the name and/or parent folder of a file asset. The file itself (path, size) cannot be changed. At least one of `name` or `parent_folder_id` must be provided.
delete_a_customer_io_asset_file_by_id
Delete a file asset. Soft-deletes a file asset by setting its `deleted_at` timestamp. The underlying file in cloud storage is not removed. Assets that are currently in use cannot be deleted.
list_all_customer_io_asset_folders
List folders. Returns a paginated list of asset folders. Supports filtering by parent folder and choosing between direct children or the entire folder subtree.
create_a_customer_io_asset_folder
Create a folder. Creates a new folder for organizing file assets. Folder names must be unique within the same parent folder. Required: name.
get_single_customer_io_asset_folder_by_id
Get a folder. Retrieves a single folder by its ID.
update_a_customer_io_asset_folder_by_id
Update a folder. Updates the name and/or parent folder of an existing folder. At least one of `name` or `parent_folder_id` must be provided. Moving a folder into itself or one of its descendants is not allowed (cycle detection).
delete_a_customer_io_asset_folder_by_id
Delete a folder. Soft-deletes an empty folder. Folders that still contain files or subfolders cannot be deleted. Assets marked as in use also prevent deletion.
list_all_customer_io_broadcast_messages
Get messages for a broadcast. Returns information about the deliveries (instances of messages sent to individual people) sent from an API-triggered broadcast. Provide query parameters to refine the metrics you want to return.… Required: broadcast_id.
customer_io_data_index_update_attributes
Add or update attributes. Attributes are customer data like their name and email. Use this endpoint to add new attributes or update existing attributes in your workspace. To add attributes to customers, use our Pipelines or… Required: attributes.
customer_io_data_index_update_events
Add or update events. Events are actions your customers have performed. Use this endpoint to add new events or update existing events in your workspace. To associate events with customers, use our Pipelines or Track APIs.… Required: events.
customer_io_esp_suppressions_get_by_email
Look up an ESP-suppressed address. Look up an email address to learn if, and why, it was suppressed by the email service provider (ESP). Customer.io checks the address against the bounces and spam reports on all of your… Required: email_address.
customer_io_esp_suppressions_list_by_type
Get ESP-suppressed emails by type. Find addresses that the email service provider (ESP) suppressed because of bounces or spam reports. You can get up to 1000 addresses per request. Use the `offset` parameter to get addresses… Required: suppression_type.
customer_io_esp_suppressions_list_by_domain
Get ESP-suppressed emails by domain. Find addresses suppressed by the Email Service Provider (ESP) for a particular reason on a specific sending domain. You can get up to 1000 addresses per request. Use the `start` parameter… Required: domain_name, suppression_type.
customer_io_esp_suppressions_unsuppress
Un-suppress an ESP-suppressed address. Remove an address from the ESP's suppression list. Required: suppression_type, email_address.
customer_io_esp_suppressions_suppress
Suppress an email at the ESP. Suppress an email address at the email service provider (ESP). Addresses suppressed this way are only suppressed through the ESP; these adresses are _not_ suppressed in Customer.io, so the person… Required: suppression_type, email_address.
list_all_customer_io_exports
List exports. Return a list of your exports. Exports are point-in-time people or automation metrics.
get_single_customer_io_export_by_id
Get an export. Return information about a specific export.
customer_io_exports_get_download_url
Download an export. This endpoint returns a signed link to download an export. The link expires after 15 minutes. Required: export_id.
customer_io_exports_create_customers_export
Export customer data. Provide filters and attributes describing the customers you want to export. This endpoint returns export metadata; use the `/exports/{export_id}/endpoint` to download your export. Required: filters.
customer_io_exports_create_deliveries_export
Export information about deliveries. Provide filters for the one-time send, automation, or action you want to return delivery information from. This endpoint starts an export, but you cannot download your export from this… Required: newsletter_id.
create_a_customer_io_import
Import items in bulk. This endpoint lets you upload a file containing people, events, objects, relationships, or geofences. It provides a handy way of adding and updating them in bulk. Uploading people, objects, or… Required: import.
get_single_customer_io_import_by_id
Retrieve a bulk import. This endpoint returns information about an "import"—a file of people, events, objects, relationships, or geofences that you uploaded using the `v1/imports` endpoint. You can use this endpoint to check…
list_all_customer_io_ip_addresses
List IP addresses. Returns a list of IP addresses that you need to allowlist if you're using a firewall or Custom SMTP provider's IP access management settings to deny access to unknown IP addresses. These addresses apply to…
list_all_customer_io_newsletter_messages
Get delivery data for a one-time send. Returns information about the "deliveries" (rendered messages) sent to your recipients for a specific one-time send (referred to as a "newsletter" in our APIs). Provide query parameters… Required: newsletter_id.
customer_io_objects_search
Find objects. Use a set of filter conditions to find objects in your workspace. Returns a list of object IDs that you can use to look up object attributes, or to create or modify objects. The list is paged if you have a large… Required: filter, object_type_id.
customer_io_objects_get_attributes
Get Object Attributes. Get a list of attributes for an object. Attributes are things you know about an object—like an account name, billing date, etc. Required: object_type_id, object_id.
list_all_customer_io_object_relationships
Get Object Relationships. Get a list of people people related to an object. You can use the `start` parameter with the `next` property in responses to return pages of results. However, it's possible that you'll see duplicate… Required: object_type_id, object_id.
list_all_customer_io_optouts
List opt-outs in the workspace. Return a workspace-wide list of opt-outs across all channels. Each entry represents a person and the senders/channels (SMS or WhatsApp) they've opted out of. A person opts out of a specific…
create_a_customer_io_reporting_webhook
Create a reporting webhook. Create a new webhook configuration. Required: endpoint, events, name.
list_all_customer_io_reporting_webhooks
List reporting webhooks. Return a list of all of your reporting webhooks
get_single_customer_io_reporting_webhook_by_id
Get a reporting webhook. Returns information about a specific reporting webhook.
update_a_customer_io_reporting_webhook_by_id
Update a webhook configuration. Update the configuration of a reporting webhook. Turn events on or off, change the webhook URL, etc. Required: endpoint, events, name.
delete_a_customer_io_reporting_webhook_by_id
Delete a reporting webhook. Delete a reporting webhook's configuration.
customer_io_subscription_center_get_token
Generate a subscription center token. Generates a signed token and URL for a person's standalone subscription center page. The token is valid for 24 hours. Use the returned `url` to link people to a hosted subscription center… Required: customer_id.
list_all_customer_io_subscription_channels
List subscription channels. Returns a list of subscription channels available in your workspace. Channels represent the delivery methods that people can subscribe to or unsubscribe from—email, SMS, push, etc. If you haven't…
list_all_customer_io_transactional_message_deliveries
Get transactional message deliveries. Returns information about the deliveries (instances of messages sent to individual people) from a transactional message. Provide query parameters to refine the metrics you want to return.… Required: transactional_id.
create_a_customer_io_collection_write
Write to a collection. Add, update, or delete rows by key, without replacing the whole collection. The collection needs a key field. A row whose key already exists replaces the old row, and a row with a new key is added. To… Required: data, collection_id.
get_single_customer_io_collection_write_by_id
Look up a collection write. Returns the status of a change you submitted to a collection and, if the change failed, the reason. Customer.io keeps each result for 24 hours. Required: collection_id.
list_all_customer_io_collection_sync_rejects
List rejected sync rows. Returns the rows from synced files that Customer.io couldn't load, sorted by file and then by row. Customer.io keeps rejected rows for 90 days. Required: collection_id.
list_all_customer_io_collection_sources
List collection sources. Returns the cloud storage buckets that you connected to your workspace as collection sources. Customer.io never returns a source's credentials.
create_a_customer_io_collection_source
Connect a collection source. Connect a bucket in Amazon S3, Google Cloud Storage, or Azure Blob Storage so that you can load files from it into your collections. After you connect a source, send its `id` and a file `path` to… Required: bucket, credentials, name, provider, region.
get_single_customer_io_collection_source_by_id
Look up a collection source. Returns a collection source, without its credentials.
delete_a_customer_io_collection_source_by_id
Delete a collection source. Disconnect a bucket from your workspace. Collections that you already wrote from the source keep their rows. After you delete a source, Customer.io responds to a new write request that names it with…
customer_io_collection_sources_check
Check a collection source. Check that a source's credentials can still read its bucket, like after you rotate a key or change the bucket's permissions. Customer.io runs the same check as when you connect the source. Required: source_id.
list_all_customer_io_customer_relationships
Lookup a customer's relationships. Return a list of objects that a person is related to. You can use the `start` parameter with the `next` property in responses to return pages of results. However, it's possible that you'll… Required: customer_id.
list_all_customer_io_customer_segments
Lookup a customer's segments. Returns a list of segments that a customer profile belongs to. Required: customer_id.
list_all_customer_io_customer_messages
Lookup messages sent to a customer. Returns information about the deliveries sent to a person. Provide query parameters to refine the data you want to return. Use the `start_ts` and `end_ts` to find messages within a time… Required: customer_id.
list_all_customer_io_customer_activities
Lookup a customer's activities. Return a list of activities performed by, or for, a customer. Activities are things like attribute changes and message sends. This endpoint is guaranteed to return activity history within the… Required: customer_id.
list_all_customer_io_customer_optouts
Lookup a customer's opt-outs. Return a list of the senders and channels that a person has opted out of, across all channels. An entry's presence in the `optouts` array means the person is opted out of that sender/channel. Use… Required: customer_id.
list_all_customer_io_design_studio_folders
List folders. Returns a paginated list of folders. This does not include files like emails, components, etc.
create_a_customer_io_design_studio_folder
Create a folder. Create a new folder at the root level or under a parent folder. To create a child folder, you need the UUID of the parent folder, which you can retrieve with List folders. Required: name.
get_single_customer_io_design_studio_folder_by_id
Get a folder. Get a folder by its UUID. You can retrieve the UUID of folders through List folders.
update_a_customer_io_design_studio_folder_by_id
Update a folder. Update part of a folder: the name and/or the folder it belongs to. If you move a folder, all files stay nested in the folder.
delete_a_customer_io_design_studio_folder_by_id
Delete a folder. Delete a folder **including subfolders and all file (components, templates, and emails)**. You cannot delete a folder with emails used in your workflows (automations, broadcasts, etc). However, you can delete…
list_all_customer_io_design_studio_emails
List emails. Returns a paginated list of emails and a separate array of folders that the emails belong to.
create_a_customer_io_design_studio_email
Create an email. Create an email. Note, you can create an email without filling out all required fields for sending. You can fill in the envelope, like a to and from address, with this method, but that's not required until you… Required: name.
get_single_customer_io_design_studio_email_by_id
Get an email. Returns a single email including content, envelope details, and transformers. This endpoint returns only default emails; see Email translations to access language variants.
update_a_customer_io_design_studio_email_by_id
Update an email. Update part of an email: an email's name, template status, folder, content, envelope, or transformers. Note, this does not publish your email; if the email is linked to a workflow like an automation, you still…
delete_a_customer_io_design_studio_email_by_id
Delete an email. Delete an email. You cannot delete an email that is linked to a workflow (automation, broadcast, etc). This deletes the email and all translations.
customer_io_design_studio_emails_link
Link an email to a workflow. Link a Design Studio email to a workflow: a transactional message, a one-time send, an automation, or an API-triggered broadcast. After you link an email, publish it to push the content live. You… Required: target, email_id.
customer_io_design_studio_emails_publish
Publish an email. Publish a linked Design Studio email. This pushes its current content to the workflow it's linked to. You must link an email to a workflow before you can publish it. Publishing pushes updates to all language… Required: email_id.
customer_io_design_studio_emails_get_publish_status
Get publish status. Check the status of a multi-language publish that returned `"status": "pending"`. Pass the `publish_id` from the Publish an email response. When the publish is still running, the response returns `"status":… Required: publish_id, email_id.
customer_io_design_studio_emails_get_unpublished_changes
Check for unpublished changes. Check whether a linked email, or any of its translations, has content changes that haven't been published yet. Use this to decide whether you need to publish before changes go live. Returns… Required: email_id.
customer_io_design_studio_emails_render
Render an email. Returns email-ready HTML. Use this endpoint to inspect your compiled markup. Liquid tags are left intact—`{{customer.first_name}}` stays in the output as written. To evaluate liquid against real profile data… Required: email_id.
customer_io_design_studio_emails_preview
Preview an email. Returns an email with liquid fully evaluated against data you provide. The response includes the final HTML as a recipient would see it, along with liquid errors. Omit the body or send `{}` to render your… Required: email_id.
customer_io_design_studio_emails_test_send
Send a test email. Sends a test email to a real inbox through your sending domain using the content saved to Design Studio. The test includes the tracking pixel and link parameters a real send would add, so you can see your… Required: to, email_id.
customer_io_design_studio_emails_review
Review an email. Checks an email's saved content for errors and suggests how to improve accessibility, styling, and more. This runs the same process as the *Review* panel in Design Studio and returns a readiness score, a… Required: email_id.
customer_io_design_studio_emails_create_inbox_preview
Send for inbox previews. Initiate one or more inbox previews for an email. This uses inbox preview credits; check your balance with Get preview credit balance. **Learn how billing for inbox previews work before you call this… Required: client_ids, email_id.
list_all_customer_io_design_studio_email_translations
List email translations. Returns all translations for an email. Each translation contains the email's content, envelope, and transformers for a specific language. Required: email_id.
create_a_customer_io_design_studio_email_translation
Create an email translation. Creates a new translation for an email. If content, envelope, and/or transformers are omitted, the values are copied from the default (parent) email. Required: language, email_id.
get_single_customer_io_design_studio_email_translation_by_id
Get an email translation. Returns a single email translation by language code, including content, envelope, and transformers. Required: email_id.
update_a_customer_io_design_studio_email_translation_by_id
Update an email translation. Update part of an email translation: the content, envelope, or transformers for a specific email translation. Note, this does not publish your email; if the email is linked to a workflow like an… Required: email_id.
delete_a_customer_io_design_studio_email_translation_by_id
Delete an email translation. Delete a specific language translation from an email. This fails if the email is linked to a workflow (automation, broadcast, etc). Required: email_id.
list_all_customer_io_design_studio_email_versions
List email versions. Returns an email's saved versions, newest first. A version is a named checkpoint of the email's content and envelope. - Design Studio creates a version automatically every time you publish the email. - You… Required: email_id.
create_a_customer_io_design_studio_email_version
Save an email version. Saves a version of the email's current content, envelope, and any component dependencies it references. If you need to revert to a previous version, use Restore an email version. If the email is… Required: name, email_id.
get_single_customer_io_design_studio_email_version_by_id
Get an email version. Returns a snapshot of the version's content including the code for any custom components referenced in the email (see `dependencies` for more). Required: email_id.
delete_a_customer_io_design_studio_email_version_by_id
Delete an email version. Deletes a version. You can't delete a version that Design Studio created automatically during a publish. Required: email_id.
customer_io_design_studio_email_versions_restore
Restore an email version. Returns the email to a saved version. This restores only the email itself; if the code for a referenced custom component changed since this version was saved, the latest component code renders in… Required: email_id, version_id.
list_all_customer_io_design_studio_sms
List SMS. Returns a paginated list of your SMS messages and a separate array of the folders they belong to. Each item in the list is a summary; to see an SMS's content, recipient, and sender, get the SMS.
create_a_customer_io_design_studio_sm
Create an SMS. This endpoint creates an SMS message in Design Studio. After you create an SMS, link it to a workflow. If you make updates after linking the message, make sure you publish changes to send the latest content to… Required: content, name.
get_single_customer_io_design_studio_sm_by_id
Get an SMS. Returns a single SMS, including its content, recipient, and sender.
update_a_customer_io_design_studio_sm_by_id
Update an SMS. Update an SMS's name, folder, content, recipient, or sender. You only need to send the fields you want to change; Customer.io keeps the current value of any field you leave out. If the SMS is linked to a…
delete_a_customer_io_design_studio_sm_by_id
Delete an SMS. Delete an SMS. You can't delete an SMS that's linked to a workflow, like a transactional message, a one-time send, or an automation action.
customer_io_design_studio_sms_link
Link an SMS to a workflow. Link an existing SMS to a workflow—a transactional message, a one-time send, an automation action, or an API-triggered broadcast—to send it to your audience. If your workflow is already live, people… Required: target, sms_id.
customer_io_design_studio_sms_publish
Publish an SMS. If you made changes to a linked SMS message, you need to publish the SMS when you're ready so your workflows send the latest content. Required: sms_id.
list_all_customer_io_design_studio_whatsapp
List WhatsApp templates. Returns a paginated list of the WhatsApp templates you made in Design Studio and a separate array of the folders they belong to. Each item in the list is a summary that includes the template's Meta…
create_a_customer_io_design_studio_whatsapp
Create a WhatsApp template. This endpoint creates a WhatsApp template in Design Studio. Creating a template doesn't send anything to Meta. Before you can send the template to your audience, you need to submit it to Meta for… Required: category, content, language, name, recipient.
get_single_customer_io_design_studio_whatsapp_by_id
Get a WhatsApp template. Returns a single WhatsApp template, including its content, category, language, recipient, sender, and Meta approval status.
update_a_customer_io_design_studio_whatsapp_by_id
Update a WhatsApp template. Update a WhatsApp template's name, folder, category, language, content, recipient, or sender. You only need to send the fields you want to change; Customer.io keeps the current value of any field…
delete_a_customer_io_design_studio_whatsapp_by_id
Delete a WhatsApp template. Delete a WhatsApp template from Design Studio. You can't delete a template that's linked to a workflow, like a transactional message, a one-time send, or an automation action. Deleting a template in…
customer_io_design_studio_whatsapp_submit
Submit a WhatsApp template to Meta. Submit a WhatsApp template to Meta for approval. Customer.io sends the template's content, category, and language to Meta, which creates a new template in your WhatsApp Business Account.… Required: whatsapp_id.
customer_io_design_studio_whatsapp_get_status
Get a WhatsApp template's Meta status. Returns a WhatsApp template's Meta approval status. After you submit a template, call this endpoint periodically to find out when Meta approves or rejects it. If you haven't submitted the… Required: whatsapp_id.
customer_io_design_studio_whatsapp_link
Link a WhatsApp template to a workflow. Link a WhatsApp template to a workflow or action: a transactional message, a one-time send, an automation action, or an API-triggered broadcast. The workflow or action needs to send… Required: target, whatsapp_id.
customer_io_design_studio_whatsapp_publish
Publish a WhatsApp template. Publish a linked WhatsApp template, pushing its current content, recipient, and sender to the workflow it's linked to. Publishing doesn't send anything to Meta, so you can publish as often as you… Required: whatsapp_id.
list_all_customer_io_design_studio_components
List components. Returns a paginated list of components and any folders in the result set.
create_a_customer_io_design_studio_component
Create a component. Creates a custom component. Required: content, name, tag.
get_single_customer_io_design_studio_component_by_id
Get a component. Returns a single component with its full content.
update_a_customer_io_design_studio_component_by_id
Update a component. Update part of a component: its name, tag, folder, or content.
delete_a_customer_io_design_studio_component_by_id
Delete a component. Delete a component. Note, this deletes any component. If you delete a component in use, the emails that reference it could fail to send.
list_all_customer_io_inbox_preview_clients
List inbox preview options. Returns the catalog of email clients and devices available for inbox previews. Use the `id` values returned by this endpoint as `client_ids` when you send for an inbox preview.
customer_io_inbox_previews_get_credits
Get preview credit balance. Returns your account's credit balance for inbox previews. Your credit balance determines how many previews you can generate in your account. Learn more about how inbox previews use credits.
get_single_customer_io_inbox_preview_job_by_id
Get an inbox preview job. Returns the status of a preview job submitted with Send for inbox previews, including each preview's settings. Required: email_id.
customer_io_inbox_preview_jobs_get_capture
Get a preview screenshot. Returns the image bytes for a single preview job, proxied from the vendor. The response's content type matches whatever the vendor sent for that capture, which isn't always PNG, and the… Required: email_id, run_id, client_id.
list_all_customer_io_inbox_preview_jobs
List inbox preview history. Returns a paginated history of inbox preview jobs across your workspace, or for a single email when you pass `node_id`. Only lists runs recent enough for their screenshots to still be viewable—an…
customer_io_track_accounts_get_region
Find your account region. This endpoint returns the appropriate region and URL for your Track API credentials. Use it to determine the URLs you should use to successfully complete other requests. You can perform this operation… Track API: needs the optional Site ID + Track API Key on the connection.
customer_io_track_customers_identify
Add or update a customer. Adds or updates a person. If your request does _not_ include `cio_id` and the identifiers in the request body do not belong to a person, your request adds a person. If a person already exists with the… Required: identifier. Track API: needs the optional Site ID + Track API Key on the connection.
delete_a_customer_io_track_customer_by_id
Delete a customer. Deleting a customer removes them, and all of their information, from Customer.io. **NOTE**: Calls that update customers by ID can also create a customer. If you send data to Customer.io through other means… Track API: needs the optional Site ID + Track API Key on the connection.
customer_io_track_customers_add_device
Add or update a customer device. Customers can have more than one device. Use this method to add iOS and Android devices to, or update devices for, a customer profile. Required: device, identifier. Track API: needs the optional Site ID + Track API Key on the connection.
customer_io_track_customers_delete_device
Delete a customer device. Remove a device from a customer profile. If you continue sending data about a device to Customer.io, you may inadvertently re-add the device to the customer profile. Required: identifier, device_id. Track API: needs the optional Site ID + Track API Key on the connection.
customer_io_track_customers_suppress
Suppress a customer profile. Delete a customer profile and prevent the person's identifier(s) from being re-added to your workspace. Any future API calls or operations referencing the specified ID are ignored. If you suppress… Required: identifier. Track API: needs the optional Site ID + Track API Key on the connection.
customer_io_track_customers_unsuppress
Unsuppress a customer profile. Unsuppressing a profile allows you to add the customer back to Customer.io. If you unsuppress a person in a workspace that identifies people by *email or ID* and the suppressed person had both an… Required: identifier. Track API: needs the optional Site ID + Track API Key on the connection.
customer_io_track_customers_unsubscribe
Custom unsubscribe handling. This endpoint lets you set a global unsubscribed status outside of the subscription pathways native to Customer.io. If you use custom unsubscribe links, you can host a custom unsubscribe page and… Required: delivery_id. Track API: needs the optional Site ID + Track API Key on the connection.
customer_io_track_customers_merge
Merge duplicate people. Merge two customer profiles together. The payload contains `primary` and `secondary` profile objects. The primary profile remains after the merge and the secondary is deleted. This operation is _not_… Required: primary, secondary. Track API: needs the optional Site ID + Track API Key on the connection.
customer_io_track_events_track
Track a customer event. Send an event associated with a person, referenced by the identifier in the path. There are three defined event `type` values: `page`, `screen` and `event`. Page and screen events represent website page… Required: name, identifier. Track API: needs the optional Site ID + Track API Key on the connection.
customer_io_track_events_track_anonymous
Track an anonymous event. An anonymous event represents a person you haven't identified yet. When you identify a person, you can set their `anonymous_id` attribute. If event merging is turned on in your workspace, and the… Required: name. Track API: needs the optional Site ID + Track API Key on the connection.
customer_io_track_events_report_metrics
Report metrics. This endpoint helps you report metrics from channels that aren't native to Customer.io or don't rely on our SDKs. When we deliver a message, we include a CIO-Delivery-ID header. This is the `delivery_id` in the… Required: delivery_id, metric. Track API: needs the optional Site ID + Track API Key on the connection.
customer_io_track_events_report_push_metrics
Report push metrics. While this endpoint still works, you should take advantage of our universal metrics endpoint. It supports channels besides push and lets you provide additional information with some metrics. Use this… Track API: needs the optional Site ID + Track API Key on the connection.
customer_io_track_forms_submit
Submit a form. Submit a form response. If Customer.io does not recognize the `form_id` we create a new form connection (found on the *Data & Integrations* > *Integrations* > *Forms* page). Form submissions with the same ID are… Required: data, form_id. Track API: needs the optional Site ID + Track API Key on the connection.
customer_io_track_segments_add_customers
Add people to a manual segment. Add people to a manual segment by ID. You are limited to 1000 customer IDs per request. This endpoint lets you add people to manual segments, but a segment must exist before you can add people… Required: ids, segment_id. Track API: needs the optional Site ID + Track API Key on the connection.
customer_io_track_segments_remove_customers
Remove people from a manual segment. You can remove users from a manual segment by ID. You are limited to 1000 customer IDs per request. When you call this API, you can pass an `id_type` query parameter to set the type of… Required: ids, segment_id. Track API: needs the optional Site ID + Track API Key on the connection.
create_a_customer_io_track_entity
Make a single request. This endpoint lets you create, update, or delete a single person or object—including managing relationships between objects and people. An "object" is any kind of non-person entity that you want to… Required: action, attributes, identifiers, name, type. Track API: needs the optional Site ID + Track API Key on the connection.
create_a_customer_io_track_batch
Send multiple requests. This endpoint lets you batch requests for different people and objects in a single request. Each object in your array represents an individual "entity" operation—it represents a change for a person, an… Track API: needs the optional Site ID + Track API Key on the connection.
Why Truto
Why use Truto’s MCP server for Customer.io
Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 1050+ integrations.
Auto-generated, always up to date
Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.
Fine-grained access control
Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.
Multi-tenant by design
Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.
Works with every MCP client
Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.
Built-in auth, rate limits, and error handling
Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.
Expiring and auditable servers
Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.
Unified APIs
Unified APIs for Customer.io
Skip writing code for every integration. Use Truto’s category-specific Unified APIs out of the box or customize the mappings with AI.
Unified Marketing Automation API
Campaigns
The campaign represent a campaign in the remote system.
Contacts
The contact represent a contact in the remote system.
Messages
The message represent a message in the remote system.
Segments
Represents a segment of contacts in the remote system.
Templates
The template represent a template for marketing asset in the remote system.
Users
The user represent a user in the remote system.
Workspaces
The workspace represent a workspace in the remote system.
How It Works
From zero to integrated
Start with Customer.io in a free sandbox, usually ready within one business day. No boilerplate, no maintenance burden.
Link your customer’s Customer.io account
Use Truto’s frontend SDK to connect your customer’s Customer.io account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.
We handle authentication
Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.
Call our API, we call Customer.io
Truto’s Proxy API is a 1-to-1 mapping of the Customer.io API. You call us, we call Customer.io, and pass the response back in the same cycle.
Unified response format
Every response follows a single format across all integrations. We translate Customer.io’s pagination into unified cursor-based pagination. Data is always in the result attribute.
FAQs
Common questions about Customer.io on Truto
Authentication, rate limits, data freshness, and everything else you need to know before you integrate.
What authentication method does Customer.io use?
Customer.io uses API key-based authentication. The Track API uses a Site ID and API Key pair, while the App API uses a separate App API Key. Truto handles storing and managing these credentials so your end users authenticate once during the connection flow.
Does Customer.io have separate APIs for reading and writing data?
Yes. Customer.io splits its API into two distinct surfaces: the Track API (and Pipelines API) for ingesting contacts, attributes, and events, and the App API for reading campaigns, messages, segments, and workspace metadata. Truto abstracts this split behind a single unified interface.
Are Customer.io tools available today in Truto?
Customer.io integration tools are built on request. Once requested, Truto builds and exposes them through the Unified Marketing Automation API, covering resources like Campaigns, Contacts, Messages, Segments, Templates, Users, and Workspaces.
How does Truto handle Customer.io's rate limits and pagination?
Truto manages rate limiting and pagination automatically. When you query resources like messages or contacts through the Unified API, Truto handles page cursors and respects Customer.io's rate limits transparently, so your application never needs to deal with retry logic or partial responses.
Can I sync custom attributes and events that aren't part of a standard schema?
Yes. Customer.io supports highly flexible custom attributes on contact profiles and arbitrary named events. Truto's Unified API passes through custom fields and event properties, so your integration isn't limited to a fixed set of attributes.
What Unified API resources map to Customer.io capabilities?
Truto's Unified Marketing Automation API covers Campaigns, Contacts, Messages, Segments, Templates, Users, and Workspaces — mapping to Customer.io's core concepts for managing audiences, triggering communications, and reading engagement data.
Customer.io
Get Customer.io integrated into your app
Our team understands what it takes to make a Customer.io integration successful. A short, crisp 30 minute call with folks who understand the problem.