Authentication — TropMail Docs

REST, SDKs, and MCP all use the same Bearer key.

Create a key

Open the TropMail dashboard
Create an API key
Store it as an environment variable. Do not commit it.

export TROPMAIL_API_KEY=your32charalphanumericapikeyhere

Keys are 32 characters of [A-Za-z0-9], optionally prefixed with tm_live_. Official clients validate that locally before the first request.

Send the header

Authorization: Bearer YOUR_API_KEY

Always include the Bearer prefix. Official SDKs set this header for you.

MCP

Remote Streamable HTTP at https://mcp.tropmail.com/mcp. Same Bearer key as REST.

Claude Code

claude mcp add --transport http \
  --header "Authorization: Bearer YOUR_API_KEY" \
  tropmail https://mcp.tropmail.com/mcp

Cursor

{
  "mcpServers": {
    "tropmail": {
      "url": "https://mcp.tropmail.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Full steps: Connect MCP.

Rate limits

Limits apply per account.

Tier	Requests / second
Pro	3
Ultimate	10
Enterprise	50

Response headers: X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset. On 429, honor Retry-After. Official SDKs pace themselves from those headers.

Recommended headers

Header	Notes
`Authorization`	Required on every route except health
`Content-Type`	`application/json` on POST bodies
`Accept`	`application/json`
`X-Request-ID`	Optional UUID. Echoed for support.

Official SDKs set these for you.