How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

TempMailGrab REST API

Versioned v1 REST API for creating private disposable inboxes, reading parsed messages with extracted OTPs and verification links, managing webhooks, and registering custom domains. Machine-readable OpenAPI 3.1 contract available.The declared apis.json at tempmailgrab.com/apis.json 404s, but the OpenAPI is real and served at /api/openapi.json -- OpenAPI 3.1.2, 15 operations, verified live. Their llms.txt names it, along with the npm SDK and a versioned, CC-licensed compatibility dataset published as both JSON and CSV. Probing the conventional root paths finds none of it. Verified 2026-09-01.

This API exposes 15 operations across 12 paths, and defines 5 schemas. It is described by OpenAPI 3.1.2, at version 1.0.0.

Requests are made against a single base URL, https://tempmailgrab.com/api/v1.

15 operations 12 paths 5 schemas 3 DELETE6 GET6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.2
API Version
1.0.0
Base URL
https://tempmailgrab.com/api/v1
Authentication
HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 2

TempMailGrab REST API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). An API key is passed in the header as X-API-Key (apiKey). By default, every request must be authenticated.

Paths & Operations 15

Across 12 paths, the API surfaces 15 operations — 3 DELETE, 6 GET, 6 POST. Each is listed below with its method, path, parameters, and response codes.

Operations 15
POST
/inbox
Create a disposable inbox
createInbox body → 201400429
DELETE
/inbox/{id}
Delete an inbox and all of its mail
deleteInbox 1 param → 200404
GET
/inbox/{id}/messages
List messages (newest first)
listInboxMessages 1 param → 200401
DELETE
/inbox/{id}/messages
Delete every message in an inbox, keeping the address
deleteInboxMessages 1 param → 200401
GET
/inbox/{id}/messages/{mid}
Fetch one full message
getInboxMessage 2 params → 200404
POST
/inbox/{id}/test-message
Inject a synthetic message through the parsing and realtime pipeline
createTestMessage 1 param body → 200404
GET
/messages
List messages using the flat endpoint alias
listMessages 1 param → 200404
GET
/messages/{id}
Fetch one message by ID (flat alias)
getMessage 1 param → 200404
POST
/inbox/{id}/webhook
Register a delivery webhook for one inbox
createInboxWebhook 1 param → 201401
GET
/webhooks
List account webhooks
listWebhooks → 200401
POST
/webhooks
Register an account webhook (fires for every inbox)
createWebhook body → 201401
DELETE
/webhooks/{id}
Delete an account webhook
deleteWebhook 1 param → 200401
GET
/byod
List custom domains registered to this API key
listCustomDomains → 200401
POST
/byod
Register a custom domain and receive its DNS requirements
createCustomDomain body → 201409
POST
/byod/{domain}/verify
Verify custom-domain TXT ownership and MX routing
verifyCustomDomain 1 param → 200404

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are MessageDetail (10 properties), WebhookMessage (9 properties), MessageSummary (6 properties), Inbox (4 properties). Each schema is shown below with its type and property counts.

Inbox
object
4 properties 4 required
MessageSummary
object
6 properties 6 required
MessageDetail
object
10 properties 10 required
WebhookMessage
object
9 properties 9 required
Error
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tempmailgrab-openapi.json Raw ↑
Where this information came from

This is an independent, third-party profile of TempMailGrab REST API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.