Skip to content
Docs

Reference

REST API changelog

Changes to REST API: new features, improvements and fixes.

October 2026

  1. Improved

    Hosted MCP server covers the full API v2

    MCP serverREST API

    The MCP server at https://api.emailit.com/mcp now covers everything in API v2:

    • New toolsets: campaigns, automations, forms, DMARC reports, email verification, events, contact bulk actions and export, subscribers, and webhook tests, retries and secret rotation. See the tool reference.
    • Annotations: every tool is labeled read-only, destructive, idempotent or open-world, so clients can ask before running write actions.
    • Structured results: tools return JSON as text and as structured content for clients that parse it.
    • Built-in instructions: the server tells assistants to confirm recipients before sending and to ask before deleting anything.
    • Toolsets and read-only mode: load fewer tools with ?toolsets= or hide write tools with ?read_only=true. See Toolsets.
    • Stateless transport: no MCP sessions to expire; clients send every request with POST.

    Fixed: OAuth connections approved with both the sending and full scopes now work on every tool, and the workspace you switch to stays selected after the client refreshes its token.

September 2026

  1. Fixed

    API v2 compatibility fixes

    REST APIAPI keysEmail APISending domains

    • API keys created before keys had the secret_ prefix are accepted on /v2 again.
    • Retrieve an email returns the full email object, including object, from and to.
    • Domain responses return track_loads and track_clicks as 0 or 1, as documented.
  2. New

    API and SMTP request logs

    Email logsREST APISMTP relay

    Open Email API → Logs to see successful and failed requests from the last hour up to the last 30 days. Filter by source (API or SMTP), outcome, method, path, status code, duration or API key, and open a request to see its request and response bodies. Sensitive values are redacted and long bodies are shortened.

    See Request logs.

  3. New

    Filters and sorting on every list

    DashboardREST API

    In the dashboard, use Filters to combine conditions with Match all or Match any, click column headers to sort, and choose columns in Display options.

    In the API, filter with field.condition=value query parameters, combine them with match=all or match=or, and sort with order and direction:

    Terminal
    curl "https://api.emailit.com/v2/emails?status.exact=bounced&created_at.after=2026-09-01&order=created_at&direction=desc" \
      -H "Authorization: Bearer $EMAILIT_API_KEY"

    Each list endpoint documents its filterable fields. See Filtering.

February 2026

  1. New

    Contacts, Events and Webhooks APIs

    ContactsEmail logsWebhooksREST API

    • Contacts: create, list, retrieve, update and delete contacts. Look a contact up by its con_ ID or email address, and add it to audiences in the same call.
    • Events: list events, filtered by one or more types and optionally with their data, and retrieve a single event.
    • Webhooks: create, list, retrieve, update and delete webhook endpoints.

    These endpoints need a full access key. See the API reference.

January 2026

  1. Changed

    Prefixed object IDs

    REST API

    IDs are unique across services and sort by creation time. Common prefixes are em_ for emails, dom_ for domains, key_ for API keys, aud_ for audiences, sub_ for subscribers, con_ for contacts, sup_ for suppressions, wh_ for webhooks, evt_ for events and cmp_ for campaigns.

    Store IDs as opaque strings rather than parsing them.

  2. Deprecated

    API v1 deprecated

    REST API

    New features ship only in API v2 at https://api.emailit.com/v2. If you still call /v1, switch to the v2 endpoints and send your API key in the Authorization: Bearer header.

    See Versioning.

October 2025

  1. New

    API v2

    REST APIAPI keysSending domainsAudiencesSuppressions

    API keys replace credentials. A key has the full or sending scope, a sending key can be restricted to one sending domain, and you can manage keys through the API. API v1 stayed available while you migrated.

    See the API reference.

Was this page helpful?

Thanks for the feedback.

Thanks, we read every message.