API Access

Integrate disposable email into your applications

Free

For personal use

$0 forever
  • ✓Private token-protected inboxes
  • ✓Selectable 10-minute to 7-day lifetime
  • ✓REST API and WebSocket
  • ✓1,000 API requests / month
  • ✓1 API key
  • ✓Automatic OTP and verification links
  • ✓Attachment support
  • ✓Community support

Starter

For indie developers

$9/mo
  • ✓Everything in Free
  • ✓10,000 API requests / month
  • ✓2 API keys
  • ✓1 signed webhook endpoint
  • ✓Webhook delivery history
  • ✓JavaScript and Python SDK source
  • ✓Playwright and Cypress helpers
  • ✓Email support
Most Popular

Pro

For growing teams

$29/mo
  • ✓Everything in Starter
  • ✓100,000 API requests / month
  • ✓5 API keys
  • ✓3 signed webhook endpoints
  • ✓Email forwarding
  • ✓API usage analytics
  • ✓Priority email support
  • ✓Developer integration assistance

Business

For enterprises

$99/mo
  • ✓Everything in Pro
  • ✓Unlimited API requests
  • ✓Unlimited API keys
  • ✓10 signed webhook endpoints
  • ✓Custom domain onboarding
  • ✓Email forwarding
  • ✓Custom integration assistance
  • ✓Invoice billing

All API plans include access to api.inboxburn.com — API Documentation →

Frequently Asked Questions

How API plans and quotas work

What counts as a request

Every call to an /api endpoint that carries your API key counts as one request: creating an inbox, listing its messages, reading a single message, downloading an attachment, extending or deleting an inbox. The counter is updated before the endpoint runs, so a call that later returns an error such as 404 still counts. Calls rejected during key checks, for example with an unknown, expired or inactive key or from an IP address the key does not allow, do not use quota. Using the website or your dashboard does not consume API quota.

Polling is the usual way quotas disappear quickly: checking one inbox every two seconds for ten minutes costs 300 requests. The WebSocket stream and, on paid plans, signed webhooks tell you when mail arrives, so you only spend requests on fetching the message itself.

Monthly reset and what happens at the limit

Quotas are counted per calendar month and start again from zero on the first day of each month. All keys of a personal account share one counter; team keys share the team counter. Each request reserves its slot atomically, so many parallel requests cannot push you past the limit.

When the quota is used up, the API answers 429 with a Retry-After header containing the seconds until the next month begins (midnight UTC on the first), plus a JSON body with your plan, quota and usage. Because that wait can be days long, treat it as a signal to alert your team or upgrade rather than something to sleep on. If a plan has an end date and it has passed, the API returns 403 with the expiry time until the plan is renewed.

Short-term limits are separate. Requests without a key are limited per IP address, for example 10 inbox creations and 20 inbox reads per minute, and also receive 429 with Retry-After. Requests with a valid key skip those per-IP limits; your plan quota applies instead.

Trials

Accounts are created by the InboxBurn team rather than by self-service sign-up. On the API access form you choose Starter (10,000 requests) or Pro (100,000 requests) and describe your application. A person reviews each request. If it is approved, the team sets a trial length of 1 to 30 days (7 by default), creates the account and emails a single-use link to set your password, valid for 24 hours. A trial allowance covers the whole trial and does not reset at a month boundary; access stops when the allowance is used or the trial ends, whichever comes first.

Keys, webhooks and team features by plan

Webhooks are signed with HMAC-SHA256 using a secret per endpoint. Each delivery carries X-InboxBurn-Timestamp and X-InboxBurn-Signature headers, so your server can verify that the call came from InboxBurn and is recent. Failed deliveries are retried after 1, 5, 15 and 60 minutes, and the delivery history in the dashboard shows status codes and response times. Webhook deliveries do not count as API requests.

On Business, the account owner can create a team, invite existing InboxBurn users by email (invitations expire after 7 days) and remove members. Team API keys and team webhooks use the owner’s plan, and their usage is collected on one shared counter.

  • Free: 1 API key and no webhook endpoints; use polling or the WebSocket for notifications.
  • Starter: 2 keys and 1 signed webhook endpoint.
  • Pro: 5 keys, 3 webhook endpoints and email forwarding.
  • Business: unlimited keys, 10 webhook endpoints, forwarding and team accounts.

Estimating the plan you need

Estimate per test run, then multiply. A CI suite that creates 20 inboxes per run, learns about new mail through a webhook and reads each message once uses about 40 requests per run. At 10 runs per working day, that is roughly 8,800 requests a month: above Free, comfortably within Starter. The same suite polling every 2 seconds for an average of 30 seconds per inbox adds about 300 list calls per run and needs Pro. Usage alerts in the dashboard, for example at 80% of the quota, warn you before requests start failing.

Frequently Asked Questions