Email on Acid API

Name: Email on Acid API
Brand: Email on Acid API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingEmail Marketingbasic9 EndpointsREST

For Agents

Run automated rendering and spam tests on marketing emails across 90+ inbox clients and retrieve per-client screenshots and deliverability scores.

Install Jentic One Beta

Connect the Email on Acid API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Email on Acid API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Email on Acid API.

Submit an HTML email for rendering tests across desktop, mobile, and webmail clients

Retrieve per-client screenshot URLs and rendering metadata for a completed test

Reprocess a stalled test against the currently available client list

GET STARTED

Start building with Email on Acid API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Email on Acid API, keeping it validated and agent-ready. Email on Acid runs pre-send email tests across more than 90 client and device combinations and returns rendered screenshots so marketing teams can catch broken layouts before campaigns go out. The API supports creating and reprocessing inbox tests, fetching per-client results, and running spam filter checks against major providers. Use it to gate marketing email deployment on automated rendering and deliverability checks rather than manual previews.

Use Cases

Patterns agents use Email on Acid API for, with concrete tasks.

★ Pre-Send Rendering QA

Run an HTML email through Email on Acid before deployment to catch layout breaks in Outlook desktop, Apple Mail, Gmail webmail, and mobile clients. The API creates a test, returns a test ID, and exposes per-client screenshot URLs as renders complete. Marketing operations teams use this to gate campaign sends on automated visual checks instead of manually forwarding to test inboxes, cutting QA time per campaign from hours to minutes.

POST /email/tests with the campaign HTML and a list of target client IDs, poll GET /email/tests/{testId}/results/{clientId} for each client, and return the screenshot URLs that show rendering failures.

Campaign Spam Score Check

Submit campaign content to spam tests and read scores from major filters before sending to a paid list. The API runs the email against SpamAssassin and major provider checks and returns scored output identifying triggers such as suspect headers or content phrases. Teams use this to fix deliverability issues before damaging sender reputation, particularly on cold or re-engagement sends.

POST /spam/tests with the email subject, headers, and body, then GET /spam/tests/{testId} once processing completes to retrieve the score breakdown and trigger keywords.

Client Coverage Discovery

List the supported email clients before scheduling a rendering test so the right device and client matrix is targeted. The API returns identifiers and human-readable names for every client currently available for testing. Operations teams script this into nightly checks so new clients are picked up automatically and old ones are pruned from test plans.

Call GET /email/clients and return a deduplicated list of client IDs grouped by platform (desktop, mobile, webmail).

Agent-Driven Pre-Flight Email Check

An agent inside a marketing platform takes a draft HTML email, submits it to Email on Acid for both rendering and spam tests, waits for results, and writes a structured pass or fail summary back to the campaign record. Through Jentic the agent searches for the relevant operations, loads input schemas, and executes the calls without bespoke client code. Integration time drops from a multi-day SDK build to under an hour.

Search Jentic for 'test email rendering across clients', execute POST /email/tests and POST /spam/tests in parallel, poll for completion, and return a single JSON object summarising rendering issues and the spam score.

Key Endpoints

9 endpoints — jentic publishes the only available openapi specification for email on acid api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/email/tests

Create an email rendering test

GET

/email/tests/{testId}

Get test details and overall status

GET

/email/tests/{testId}/results/{clientId}

Get rendering result for a specific client

POST

/email/tests/{testId}/reprocess

Reprocess a stalled test

POST

/spam/tests

Create a spam filter test

GET

/spam/tests/{testId}

Get spam test scores and triggers

GET

/email/clients

List supported email clients

POST

/email/tests

Create an email rendering test

GET

/email/tests/{testId}

Get test details and overall status

GET

/email/tests/{testId}/results/{clientId}

Get rendering result for a specific client

POST

/email/tests/{testId}/reprocess

Reprocess a stalled test

POST

/spam/tests

Create a spam filter test

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Email on Acid Basic Auth credentials are stored encrypted in the Jentic vault. Agents receive scoped access tokens — the raw username and password never enter the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'test email rendering across clients') and Jentic returns the matching Email on Acid operations with their input schemas, so the agent calls the right endpoint without browsing docs.

Time to first call

Direct Email on Acid integration: 1-2 days for auth, polling, and screenshot retrieval logic. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Email on Acid API through Jentic.

Why is there no official OpenAPI spec for Email on Acid API?

Email on Acid does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Email on Acid API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Email on Acid API use?

The API uses HTTP Basic authentication with your Email on Acid account credentials passed in the Authorization header. Through Jentic, those credentials are stored encrypted in the vault and the agent receives only a scoped token, so the username and password never enter the agent's context.

Can I run spam filter tests with the Email on Acid API?

Yes. POST /spam/tests submits the email and GET /spam/tests/{testId} returns the scores and trigger details. The same flow can be used directly or driven through a Jentic agent.

How do I get rendering screenshots through Jentic?

Search Jentic with the query 'test email rendering across clients', load the schema for POST /email/tests, execute it with your HTML and client list, then call GET /email/tests/{testId}/results/{clientId} per client to retrieve screenshot URLs.

What are the rate limits for the Email on Acid API?

The OpenAPI spec does not declare quantitative rate limits; Email on Acid enforces limits at the account tier. Treat 429 responses as authoritative and back off using the Retry-After header when present.

Can I list the available email clients before submitting a test?

Yes. GET /email/clients returns the current catalogue with client IDs and platform metadata, so you can build the target client list dynamically rather than hard-coding values.

How do I reprocess a test that did not finish?

Call POST /email/tests/{testId}/reprocess to requeue an incomplete test against the currently available client list, then re-poll GET /email/tests/{testId} until status reaches completion.

Email on Acid API

Connect the Email on Acid API to your agent

Capabilities

Start building with Email on Acid API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs