Our principles

Code it your way

We know email code is a fickle beast, and sometimes you have to do things that would make web designers weep. That is why Taxi makes no assumptions about your code | you can add as many obscure fixes as you like, and we will take care of the content.

Craft the editor experience

Taxi Syntax gives you complete control over what is editable and what is not. It means you can build the perfect experience for Editors - enabling them to change everything they need to and nothing that they do not.

The perfect crime

Once the final code is exported from Taxi, we remove all evidence of Taxi Syntax. That means there is nothing unexpected to cause problems in your email platform, or in users' email clients.

Our minimum viable language

You can get started with making your email HTML editable by using just two Taxi Syntax tags. When you are ready, you can get more granular control over templates with just a few more tags.

See how Email Design Systems and Taxi Syntax work.

Use Litmus Builder

We are big fans of Litmus Builder, the first code editor tailored specifically for email designers. Litmus Builder fully supports Taxi Syntax, so it is even easier to make the HTML in your Email Design System editable.

Find out more about Litmus Builder.

Automate with the Taxi API

The Taxi REST API gives you programmatic access to your email content and resources, enabling you to integrate Taxi into your existing workflows and systems.

Push and pull content — Read and update field values on any version to sync content bidirectionally with your CMS or other systems.
Render emails — Generate final HTML with Liquid variable substitution, or compile for continuous export via a connector.
Manage modules — Add, remove and reorder modules in modulezones to assemble emails programmatically.
Mailing lifecycle — Create and manage mailings, versions and translations across your projects.
Clone resources — Asynchronously clone projects, mailings or versions via REST, with optional name and description overrides and dedicated clone_status endpoints for polling progress.
Trigger connector exports — Asynchronously export a version through any configured GCS or SparkPost connector via REST, with per-connector schema validation and an export status endpoint for polling progress.
Email Design Systems — Upload, update and validate your EDS via the API, with optional review-free uploads for CI/CD pipelines.
Read & List Resources — List and read your Email Design Systems, list a project's mailings or a mailing's versions, and render any mailing's final HTML and subject line on demand.

API keys can be generated from the Integrations page in your Taxi account.

Explore the full API documentation →

# Get field values from a version
GET /api/v1/versions/{id}/fields

# Update field values (push content)
PUT /api/v1/versions/{id}/fields

# Render final HTML
GET /api/v1/versions/{id}/render

# Add a module to a modulezone
POST /api/v1/versions/{id}/modules

# Upload a new Email Design System
POST /api/v1/eds/create

# Clone a project, mailing or version (async, returns 202)
POST /api/v1/projects/{id}/clone
POST /api/v1/mailings/{id}/clone
POST /api/v1/versions/{id}/clone

# Poll clone progress until completed
GET  /api/v1/projects/{id}/clone_status
GET  /api/v1/mailings/{id}/clone_status
GET  /api/v1/versions/{id}/clone_status

# Trigger an export through a configured connector (async, returns 202)
POST /api/v1/mailings/{id}/export/connector/{connector_id}

# Poll export status / list a mailing's export history
GET  /api/v1/exports/{id}
GET  /api/v1/mailings/{id}/exports

# List and read Email Design Systems
GET  /api/v1/eds
GET  /api/v1/eds/{id}

# Render a mailing's default (or a specified) version
GET  /api/v1/mailings/{id}/render

# List a project's mailings, or a mailing's versions
GET  /api/v1/projects/{id}/mailings
GET  /api/v1/mailings/{id}/versions

Connect AI Assistants via MCP

Taxi MCP Server (Beta) exposes your Email Design Systems to AI assistants and agentic tools over the Model Context Protocol, so tools like Claude can browse, read and validate your design systems — the reusable design your emails are built from, not individual mailings — and, with an extra permission, propose changes as review-ready drafts.

Browse & Search — List and search your organisation's Email Design Systems by name or description.
Read & Validate — Fetch a design system's full source HTML and metadata, or validate EDS markup against Taxi Syntax rules before anything is saved.
Draft Changes for Review — With Content Management enabled, an assistant can create a new EDS or stage updated HTML on an existing one, always as a pending draft a teammate reviews and publishes in Taxi.
Secure, Scoped Access — Connections use standard OAuth 2.0, with read and write permissions granted separately.

Taxi MCP Server is in beta. Contact your account manager or support to enable it for your organisation, and to grant content-management (draft write) permissions separately.

# Connect Claude Code to your Taxi MCP server
claude mcp add --transport http taxi \
  https://your-subdomain.emailcms.net/mcp

# First use opens your browser to sign in and grant access
/mcp

# Check connection and authorization status anytime
claude mcp list

Other MCP-compatible tools can connect the same way — they'll discover the sign-in flow automatically from your Taxi MCP server URL.

Connect to your email platform

We are building connectors to make it even easier to export your finalised campaign directly to your favourite email platform. Or build custom integrations using the Taxi API.

More about connectors