verapli
Sign inJoin free
Menu

Guides · messaging · Everyday developer services

Customer.io workspace

Customer messaging platform (email, SMS, push). Needs account verification and an authenticated sending domain before emails reach your audience; Track and App API credentials per workspace.

Researched · not yet run liveLast researched 25 October 2026 · Customer.io · provider site

Researched, not yet run live. Built from the provider’s official pages (linked below). A person hasn’t walked this flow end to end yet, so check each step against the source.
Do this with verapliJSON for agents

Have ready

  • A live company website and a domain with DNS access: Customer.io reviews your website, domain and use case during account verification.
  • Public company website on your sending domain · Account verification checks your website, domain and intended use case. [5]Needed for: Pass account verification
  • DNS access for the sending domain · MX, SPF, DKIM and DMARC records are needed to authenticate the domain. [4]Needed for: Add MX, SPF, DKIM and DMARC records

Steps

Steps marked “human step” are ones only you can do: verapli never signs in, submits, pays or accepts terms for you.

  1. Sign in or create a Customer.io account

    Sign in to Customer.io. If you have no account yet, you create it yourself; verapli does not create accounts.

    • Guided by hand
    • Human step: You sign in

    Where: https://fly.customer.io/login

  2. Pass account verification

    Customer.io verifies new accounts automatically; some need extra review and you will get an email from win@customer.io asking how people subscribe and for a sample message. Until verified, emails go only to your test delivery address.

    • Guided by hand
    • Human step: The provider reviews it
    • After: Sign in or create a Customer.io account
    If something goes wrong (1)
    • Email "Action required to verify your Customer.io account": Reply with how people subscribe to your messages and an example of a message you plan to send. [5]

  3. Add your sending domain

    In the workspace's email settings add your sending domain and open Show Records.

    • Guided by hand
    • Human step: You press submit
    • After: Sign in or create a Customer.io account

  4. Add MX, SPF, DKIM and DMARC records

    Add the MX, SPF TXT and DKIM TXT records on your cio##### subdomain, and a DMARC TXT at _dmarc on the root domain (minimum v=DMARC1; p=none). Do not delete existing root records. Click Verify domain.

    • Guided by hand
    • After: Add your sending domain
    The provider says
    Verification can take up to 72 hours. [4]

  5. Create API credentials

    In Account Settings > API Credentials create a Track API credential set (for sending data) and an App API key (for triggering messages) for the workspace. App API keys are shown only once.

    • Guided by hand
    • Human step: You press submit
    • After: Sign in or create a Customer.io account

    verapli captures CUSTOMERIO_APP_API_KEY here by plain code: encrypted in your browser, never shown to AI.

Terms and gotchas

Plain-English summary, not legal advice. Each card links its source.

Can cost moneyThe rules say

Emails held until verified

Before account verification, broadcast and campaign emails go only to your test delivery address. [5]

What you end up with

Env varSecretFormatWhat it is
CUSTOMERIO_APP_API_KEYsecretCustomer.io App API key (Bearer) for transactional and broadcast API calls. Customer.io names no env var; this name is a verapli convention.

Pricing

  • Costs: Essentials starts at $100/month (5k profiles); trial available.
  • Startup Program offers a year free to companies that raised under $10M.

Source [6]

For agents

The same entry as JSON: /api/v1/entries/customer-io/workspace · requirements /api/v1/requirements/customer-io/workspace · terms /api/v1/terms/customer-io/workspace.

Remote MCP (read-only, no auth)
claude mcp add --transport http verapli https://verapli.com/mcp

> "What do I need for Customer.io workspace, and how long will it take?"
  → tools/call requirements { "provider_id": "customer-io/workspace" }

Sources

  1. Stripe Projects CLI (Available providers) Customer.io is listed as a Stripe Projects provider (Messaging, email) · accessed 25 October 2026 · official
  2. projects.dev provider catalogue Catalogue service id customer.io/workspace · accessed 25 October 2026 · official
  3. Customer.io docs - Managing credentials Track API keys (track.customer.io) for tracking data; App API keys (api.customer.io) to trigger messages; created in Account Settings > API Credentials per workspace; each workspace gets primary credentials; App API keys shown only once · accessed 25 October 2026 · official
  4. Customer.io docs - Domain authentication MX, SPF TXT and DKIM TXT on an account-specific cio##### subdomain plus DMARC at _dmarc on the root domain; Verify domain; verification can take up to 72 hours · accessed 25 October 2026 · official
  5. Customer.io docs - Account verification Accounts verified at sign-up; before verification emails go only to the test delivery address; review of website, domain and use case; email from win@customer.io if action required · accessed 25 October 2026 · official
  6. Customer.io pricing Trial available; Essentials starts at $100/month with 5k profiles; Startup Program year free for companies that raised under $10M · accessed 25 October 2026 · official

Provider rules change. This page is generated from verapli registry version 2026.1025.387; spotted something out of date? Tell us. Customer.io is not affiliated with verapli.