Tempgbox APItempgbox.net ↗
Generate disposable Gmail-compatible email addresses and check their inboxes via API. No registration required. Aliases expire after 24 hours.
What is the Tempgbox API?
The Tempgbox.net API provides 2 endpoints to generate short-lived disposable email addresses and retrieve their incoming messages. The generate_email endpoint creates a fresh anonymous alias returning 7 fields including the address, expiry timestamp, and seconds remaining. The get_inbox endpoint returns the full message list alongside active/expired status — useful for automated account verification flows, testing pipelines, and spam-free signups.
No input parameters required.
curl -X POST 'https://api.parse.bot/scraper/a15cdec8-1084-4759-8f5a-ce98d0186f78/generate_email' \
-H 'X-API-Key: $PARSE_API_KEY' \
-H 'Content-Type: application/json' \
-d '{}'Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace tempgbox-net-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
from parse_apis.tempgbox_temporary_email_api import TempGBox, Email, Inbox, Message
client = TempGBox()
# Generate a new temporary email address
email = client.emails.generate()
print(email.email, email.alias_tag, email.is_active, email.time_remaining_seconds)
# Check the inbox for the generated email
inbox = email.inbox.get()
print(inbox.email, inbox.is_active, inbox.is_expired, inbox.total_messages)
# Iterate over messages if any exist
for msg in inbox.messages:
print(msg.from_address, msg.subject, msg.preview)
Generate a new temporary email address. Creates a fresh anonymous session, solves the Turnstile challenge, and generates a random Gmail-compatible alias that expires after 24 hours. The generated email is stored in the session for subsequent get_inbox calls.
No input parameters required.
{
"type": "object",
"fields": {
"email": "string — the generated temporary email address (Gmail plus-alias format)",
"alias_tag": "string — the unique random tag portion of the email alias",
"is_active": "boolean — whether the alias is currently active",
"base_email": "string — the base Gmail address the alias forwards to",
"created_at": "string — ISO 8601 timestamp when the alias was created",
"expires_at": "string — ISO 8601 timestamp when the alias expires (24h after creation)",
"time_remaining_seconds": "integer — seconds until the alias expires"
},
"sample": {
"data": {
"email": "[email protected]",
"alias_tag": "3ykzkw2902",
"is_active": true,
"base_email": "[email protected]",
"created_at": "2026-06-10T23:08:22.707915Z",
"expires_at": "2026-06-11T23:08:22.669028Z",
"time_remaining_seconds": 86399
},
"status": "success"
}
}About the Tempgbox API
Generating a Temporary Email
The generate_email endpoint takes no inputs and returns a ready-to-use disposable address in the email field, along with alias_tag (the unique portion of the alias), base_email (the underlying Gmail address the alias forwards to), is_active status, and both created_at and expires_at ISO 8601 timestamps. The time_remaining_seconds field gives the exact countdown to expiry, which is always 24 hours from creation. Each call starts a fresh anonymous session that ties the generated address to subsequent inbox lookups.
Checking the Inbox
The get_inbox endpoint accepts an optional email parameter. If omitted, it falls back to the address generated in the active session, so a typical flow is a single generate_email call followed by repeated get_inbox polls. The response includes a messages array for all received mail, total_messages as a count, is_active and is_expired booleans to confirm the alias state, and time_remaining_seconds to track how long the address remains usable. The session_id and encryption_key returned from the generate step are required inputs to authenticate the inbox request.
Alias Lifecycle
Each alias has a hard 24-hour lifetime. Once is_expired returns true and time_remaining_seconds reaches zero, the alias stops accepting mail and inbox calls will reflect the expired state. There is no endpoint to extend or renew an alias — a new generate_email call is required to get a fresh address.
The Tempgbox API is a managed, monitored endpoint for tempgbox.net — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when tempgbox.net changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official tempgbox.net API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Automate email verification steps in QA test suites using generated aliases that expire cleanly after each test run
- Sign up to third-party services in scraping workflows without exposing a real inbox
- Poll
get_inboxfor confirmation codes or magic links during integration testing - Generate isolated throwaway addresses for each test user in load-testing scenarios
- Monitor
time_remaining_secondsto decide when to rotate to a fresh alias mid-workflow - Use
is_activeandis_expiredflags to gate downstream automation steps on alias validity
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Tempgbox.net have an official developer API?+
What does the `messages` array in `get_inbox` contain?+
messages field is an array of message objects found in the inbox at the time of the call. The top-level response also includes total_messages as a count, plus is_active, is_expired, and time_remaining_seconds to describe the alias state at that moment. Individual message fields such as subject, sender, or body content depend on what is received.Can I reuse or extend an alias beyond 24 hours?+
is_expired is true, the alias no longer accepts mail and cannot be extended. A new generate_email call is needed to start a fresh session with a new address.Can I look up the inbox for an arbitrary email address that I did not generate in the current session?+
email parameter to get_inbox is supported, but session_id and encryption_key from the originating generate_email call are required. There is no endpoint for querying inboxes without those session credentials. You can fork this API on Parse and revise it to add a stateless inbox lookup if your use case requires it.Does the API return email message content such as subject lines, sender addresses, or body text?+
get_inbox endpoint exposes a messages array and a total_messages count, but the detailed fields within each message object are not explicitly documented in the current schema. Structured per-message fields like subject or body are not guaranteed. You can fork this API on Parse and revise it to extract and surface specific message fields if your workflow depends on them.