mailkite-dev

mailkite-dev API

mailkite-dev API as documented publicly: 38 operations. Contract generated from the documentation by API Evangelist (2026-10-29); not the provider's own document.

GitHub OpenAPI

Operations 38

GET /api/app-passwords List the account's app passwords. Each one opens a mailbox over IMAP and/or the mailbox API, scoped to a domain and an address pattern within it. #
POST /api/app-passwords Create a new app password. #
DELETE /api/app-passwords/{id} Revoke an app password. Takes effect immediately — any IMAP session or API call using it stops authenticating. #
PATCH /api/app-passwords/{id} Change what an app password covers — its label, address pattern, or protocols. #
POST /api/app-passwords/{id}/rotate Replace an app password's secret, keeping its scope. #
POST /api/auth/google Sign in with a Google auth code. Returns a session token. #
POST /api/auth/login Log in with email + password. Returns a session token. #
POST /api/auth/signup Create an account. Returns a session token. #
GET /api/billing/usage Current billing-period usage: emails used vs the plan's included bucket (null = unlimited), AI actions, and the overage state that gates sending. #
GET /api/domains/{id}/webhook/secret Read per‑route signing secret. #
GET /api/health Check service health any time with GET /api/health → { ok: true }. #
GET /api/keys Get the account's unrestricted API key (mk_live_…). Read-or-create: the first call mints it. #
POST /api/keys/rotate Rotate the account API key: the old key stops working immediately and a fresh one is returned. #
GET /api/keys/scoped List the account's domain-scoped API keys. A scoped key can send and manage only its one domain — hand one to each site or CI job so a leak burns only that surface. #
POST /api/keys/scoped Create a key scoped to one domain. Ideal for per-site installs (e.g. a WordPress plugin) — the site never holds the account master key. #
DELETE /api/keys/scoped/{id} Revoke a domain-scoped key. Takes effect immediately. #
GET /api/lists List your contact lists (static, curated broadcast audiences), each with its member count. #
POST /api/lists Create a contact list. Returns the list with its id (lst…); add contacts with addListContacts. #
DELETE /api/lists/{id} Delete a contact list. The list is removed; the contacts themselves are kept. #
GET /api/lists/{id} Get one contact list with its member count. #
PATCH /api/lists/{id} Rename a contact list. #
GET /api/lists/{id}/contacts List the contacts that are members of a list, newest first. Optionally page with `before` (a `last_seen_at`/`created_at` cursor) and `limit`. #
POST /api/lists/{id}/contacts Add contacts (by id, ctr_…) to a list. Returns how many were newly added; contacts already on the list are ignored. #
DELETE /api/lists/{id}/contacts/{contactid} Remove one contact from a list (the contact itself is kept). #
GET /api/routes List inbound routing rules. #
POST /api/routes Create a route (match, action, destination). #
DELETE /api/routes/{id} Delete an inbound routing rule by id. #
GET /api/routes/{id}/candidates Stored inbound messages this route could be asked to deliver. #
POST /api/routes/{id}/deliver POST stored messages to one webhook route. #
POST /api/v1/provision Create a MailKite account from just an email — no password. Returns the new account's API key immediately; a verification link is emailed, and SENDING stays blocked until the addre #
GET /v1/events List recorded events, newest first — the surface for confirming a POST landed and for debugging a sequence that did not trigger. #
POST /v1/events Record one application-level fact about a user — `user.created`, `trial.expiring`, `payment.failed`. #
GET /v1/events/names List the distinct event names this account works with, so an editor can offer them instead of asking you to remember one. #
GET /v1/me The account behind this credential: email, whether it is verified (sending is blocked until it is), and plan. #
GET /v1/schemas GET /v1/schemas #
GET /v1/schemas/email-received-event.json one schema — point a validator straight at it #
GET /v1/schemas/send-request.json one schema — point a validator straight at it #

Specifications

⚙
OpenAPI
https://artifacts.apis.io/mailkite-dev/openapi/_ae-authored/mailkite-dev-openapi-generated.yml

Schemas & Data

📊
JSONSchema
https://artifacts.apis.io/mailkite-dev/json-schema/mailkite-dev-get-api-routes-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/mailkite-dev/json-schema/mailkite-dev-get-api-lists-id-contacts-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/mailkite-dev/json-schema/mailkite-dev-get-api-billing-usage-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/mailkite-dev/json-schema/mailkite-dev-get-api-app-passwords-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/mailkite-dev/json-schema/mailkite-dev-post-v1-events-request-schema.json
📊
JSONSchema
https://artifacts.apis.io/mailkite-dev/json-schema/mailkite-dev-get-api-keys-scoped-response-schema.json

Other Resources

🔗
APIsJSON
https://artifacts.apis.io/mailkite-dev/apis.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/mailkite-dev:mailkite-dev-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

mailkite-dev-openapi-generated.yml Raw ↑ 
openapi: 3.1.0
info:
  title: mailkite-dev API
  version: '2026-10-29'
  description: 'GENERATED FROM DOCUMENTATION by API Evangelist on 2026-10-29: 38 operation(s) read from 8 public documentation page(s) (each operation
    names its page in x-source). This is not the provider''s published contract; mailkite-dev has published no machine-readable contract that
    the pipeline could find. Engine: local.'
  x-evidence-tiers:
    code-example: 1
    documentation: 37
    pages-with-code: 1
    pages-read: 8
  x-generated-from: documentation
  x-provenance: generated
  x-authored-by: API Evangelist
  x-generated: '2026-10-29'
  x-generator: generate-contract-from-docs.py
  x-engine: local
  x-sources:
  - https://mailkite.dev/api
  - https://mailkite.dev/api/auth
  - https://mailkite.dev/api/docs
  - https://mailkite.dev/api/lists
  - https://mailkite.dev/api/errors
  - https://mailkite.dev/api/events
  - https://mailkite.dev/api/routes
  - https://mailkite.dev/api/account
servers:


# --- truncated at 32 KB (57 KB total) ---
# Full source: https://artifacts.apis.io/mailkite-dev/openapi/_ae-authored/mailkite-dev-openapi-generated.yml