Customer.io Lets Teams Push Email HTML in and Publish by API

Customer.io said Oct. 6 that its Design Studio API can now take an email “through its whole lifecycle”: create it from your own HTML, test it, link it to a workflow and publish later changes. The company announced it in a release note.

Endpoints cover the path from HTML to publish

Teams can build emails in an outside tool and push the HTML to Customer.io through the Emails endpoints, Customer.io said. The same endpoints manage translations, folders and custom components.

Email testing endpoints come next. They review an email for issues, preview it with sample data and send a test to the sender’s own inbox. Inbox previews show how the email renders across email clients.

Linking and publishing endpoints finish the job. They attach an email to an automation, broadcast or transactional message. Later edits go live when the team publishes them.

The API only manages emails made in Design Studio

Customer.io’s integration guide, last updated Oct. 7, lists what the API cannot do. It cannot manage emails made in other editors, including the drag-and-drop editor. It cannot manage global styles such as color palettes, font families and brand rules. Those are set up in the Design Studio interface.

Publishing works one email at a time. A change to global styles or a custom component does not publish to every message that uses it.

The API also does not send mail to an audience. Transactional messages, one-time sends and API-triggered broadcasts go through the separate App API. The guide says there is “no endpoint that triggers automations.”

Setup details that can trip a build

Images must sit at public URLs. Design Studio “does not support base64 inline images,” the guide says. They can come from a team’s own CDN, an external editor’s image host or Customer.io’s Assets API. The Assets API belongs to the App API and takes the same App API key as the Design Studio API.

The take

We think the publish step is the part to watch. Customer.io publishes one email at a time, and a change to a custom component does not reach the other emails that use it. That keeps one bad edit from going out to every workflow at once. It also leaves the team to script the rounds, one call per email.

The API only reaches emails made in Design Studio. A team on the drag-and-drop editor has to rebuild those emails before any of this applies. We’d move one low-risk email through every step first and write down which steps still need a person.