Temporary and Disposable emails API - ApyHub
BO
Boomlify
25 atoms
Base tier

About

This API provides temporary and disposable email addresses with advanced features. Unlike typical services that expire in 10–60 minutes, the Boomlify API offers flexible email lifespans, including permanent options, along with enterprise-grade integration capabilities.
You can use this API to generate temporary inboxes for user sign-ups, protect your platform from spam during testing, and enable secure communication flows without exposing personal addresses.
To maintain a safe and responsible environment, the API automatically blocks domains and keywords related to gambling, betting, adult content, and other prohibited categories across multiple languages.
Try out the Boomlify API in the API playground and see how it can simplify email testing, protect user privacy, and streamline integrations with a single API call.
Select API Endpoints
Input(s)

API Playground

API Documentation

Create Temporary Email
POST
https://api.apyhub.com/boomlify/emails/create

Request example

1
```cURL
2
3
curl --location --request POST 'https://api.apyhub.com/boomlify/emails/create' \
4
--header 'apy-token: {{token}}'
Method: POST
Content Type: application/json
Query Parameter(s)
AttributeTypeMandatoryDescription
timeStringNoChoose how long your Boomlify temp mail should remain active. See options below for details.
domainStringNoSpecify a custom domain for your Boomlify temp mail. If not specified, the default Boomlify domain is used. Must be a valid domain format for professional use cases.

Email Lifetime Duration

Choose how long your Boomlify temp mail should remain active:
  • 10min — Quick testing (10 minutes) ← Default
  • 1hour — Standard use (1 hour)
  • 1day — Extended use (24 hours)
  • permanent — Until manually deleted
Sample Response
1
{
2
"success": true,
3
"email": {
4
"id": "e59d93b2-32c9-4208-b65d-5944944fd649",
5
"address": "qibydk46@xn--yaho-sqa.com",
6
"domain": "xn--yaho-sqa.com",
7
"time_tier": "10min",
8
"expires_at": "2025-08-27T10:38:00.331Z",
9
"created_at": "2025-08-27T10:28:00.331Z",
10
"is_custom_domain": false,
11
"time_remaining": {
12
"total_ms": 600000,
13
"minutes": 10,
14
"seconds": 0,
15
"human_readable": "10 minutes 0 seconds"
16
}
17
},
18
"meta": {
19
"user_id": "94fbea34-1cae-4a14-8a98-0b0650345e03",
20
"tier": "unlimited",
21
"request_time": "2025-08-27T10:28:00.331Z"
22
}
23
}

HTTP Response Codes

The method may return one of the following HTTP status codes:
Status CodeDescription
200The request was successful .
401Required authentication information is either missing or not valid for the resource.
400Invalid domain or Invalid time parameter
500If any unexpected error occurs while submitting the request.

Authentication

All API requests to ApyHub services need to be authenticated. Currently we support tokens or basic authentication mechanisms. You can generate and view your existing credentials from your workspace settings (on the left side of the navbar) and go to “API Keys".
Points to note:
  • Credential secrets are generated on the fly and are not stored in plain text, so on generating a credential please save the secrets somewhere safe.
  • Use the apy-token as the header parameter to pass the token.
  • Use the Authorization header to send the basic authentication credentials.

Error codes

1
{
2
"error": {
3
"code": 105,
4
"message": "Invalid URL"
5
}
6
}
To search for a specific error code, enter the code in the search box below. Alternatively, you can click on the button to view a complete list of all error codes.
Table of contents
AboutAPI PlaygroundAPI DocumentationAuthenticationError codesRelated Utility APIsRelated Articles