canonical: https://jentic.com/apis/temp-mail.org/temp-mail

# Temp Mail API

Temporary disposable email API. Generate temporary email addresses using available domain names, receive emails, and manage messages. Messages are automatically deleted within 1-2 hours. Provided by Privatix Ltd via temp-mail.org. The API exposes 8 endpoints secured with apiKey authentication.

## For AI agents

Programmatically domains list, get emails. Covers 8 operations with apiKey authentication.

## Scope

Does not handle payments, crm, or developer tools - use for communications only.

## Capabilities

- Domains list
- Get emails
- Source message
- Delete message
- Monitor Temp Mail API operational status and events

## Use cases

### Communications Operations

Use the Temp Mail API to perform communications operations programmatically. The API provides 8 endpoints covering core functionality including domains list, get emails, get one message.

Example prompt: Call GET `/request/domains`/ to domains list

### Automated Domains Management

Automate domains operations by combining multiple Temp Mail API endpoints. Agents can get emails and then get one message in a single workflow.

Example prompt: Call GET `/request/mail/id/{md5}`/ to get emails, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Temp Mail API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'domains list', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/request/domains/` | Domains list |
| GET | `/request/mail/id/{md5}/` | Get emails |
| GET | `/request/one_mail/id/{mail_id}/` | Get one message |
| GET | `/request/source/id/{mail_id}/` | Source message |
| GET | `/request/delete/id/{mail_id}/` | Delete message |
| GET | `/request/attachments/id/{mail_id}/` | Get message attachments (legacy) |
| GET | `/request/atchmnts/id/{mail_id}/` | Get message attachments |
| GET | `/request/one_attachment/id/{mail_id}/{atId}/` | Get one attachment |

## Key resources

- **Domains** — Operations for retrieving available email domains
- **Messages** — Operations for managing email messages
- **Attachments** — Operations for retrieving email attachments

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 65 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 73 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 55 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 69 / 100
- **View full report:** https://jentic.com/apis/temp-mail.org/temp-mail/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Temp Mail API by hand means provisioning its RapidAPI key, attaching that header to every call against the RapidAPI host, and building the mailbox polling and retry handling yourself. Through Jentic you install once, import the Temp Mail API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The Temp Mail API puts the mailbox id in the URL path (`/request/one_mail/id/{mail_id}`/), so a rule can pin your agent to one mailbox: it can read that mailbox's messages and attachments and nothing else. You choose the operations it may call, so destructive ones like deleting a message are not included unless you add them.
- **Credential handling:** Your Temp Mail API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list available domains' or 'read a temporary inbox', and Jentic returns the matching Temp Mail API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### What authentication does the Temp Mail API use?

The Temp Mail API uses an API key passed in the `x-rapidapi-key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I domains list with the Temp Mail API?

Yes. Use the GET `/request/domains`/ endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Temp Mail API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I domains list through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'domains list'. Jentic returns the matching Temp Mail API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Temp Mail API have?

The Temp Mail API exposes 8 endpoints covering domains, messages, attachments operations.

### Can I limit what my agent is allowed to do with the Temp Mail API?

Yes. Because you run Jentic One yourself, your own rules decide which Temp Mail API operations and credentials the agent may use. Since the mailbox id sits in the URL path, such as GET `/request/one_mail/id/{mail_id}`/, you can pin the agent to one mailbox so it only reads that inbox's messages and attachments and nothing else. You also choose the exact operations it may call, so a destructive one like GET `/request/delete/id/{mail_id}`/ stays out of reach unless you explicitly grant it.