Developers
API reference
Integrate verifications, placement tests, infrastructure checks, and billing with the LitInboxes REST API. All responses use a consistent JSON envelope.
- Authenticate with JWT (login) or API keys (Bearer lit_…) from Settings → API Keys.
- Success: { data, meta? }. Errors: { error: { code, message, details? } }.
- API keys are scoped per resource; see the scope list when creating a key in the app.
- Production applies per-IP and per-API-key rate limits; 429 responses include Retry-After.
Download the OpenAPI 3.0 spec: openapi.yaml
MCP server
Connect your AI assistant
LitInboxes ships a hosted MCP server, so Claude and other AI assistants can query your deliverability data and answer questions like "why are my emails going to spam?" against your own workspace.
- 10 tools covering domain health, DNS records, DMARC summaries, Google Postmaster data, blocklist status, email events, alerts, and email verification (1 verification credit per address).
- OAuth 2.1 with PKCE. No API keys to paste: your client registers itself and opens a browser for consent. Revoke access anytime from Settings.
- Works with Claude Code, Claude Desktop, Cursor, and any client that supports remote MCP servers over Streamable HTTP.
- Available on the Pro plan, with the same access entitlement as the REST API.
Add it to Claude Code:
claude mcp add --transport http litinboxes https://api.litinboxes.com/mcpIn other MCP clients, add a remote server pointing at https://api.litinboxes.com/mcp and sign in when the browser opens.