To use this endpoint, send a POST request and receive a temporary email address valid for use for 7 days.
Generate Temp Mail - Endpoint Features
Object | Description |
---|---|
Request Body |
[Required] Json |
{"id":"674642fae7ba1582460bc760","address":"[email protected]","quota":40000000,"used":0,"isDisabled":false,"isDeleted":false,"createdAt":"2024-11-26T21:51:54+00:00","updatedAt":"2024-11-26T21:51:54+00:00"}
curl --location --request POST 'https://zylalabs.com/api/5158/safe+mail+api/6579/generate+temp+mail' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"username": "johnspencer",
"password": "temp1234"
}'
To use this endpoint, make a POST request to obtain details of the temporary email account, such as its expiration date.
Fetch Mail Info - Endpoint Features
Object | Description |
---|---|
Request Body |
[Required] Json |
{"id":"66f14315e3b0f42dc107daab","address":"[email protected]","quota":40000000,"used":139343,"isDisabled":false,"isDeleted":false,"createdAt":"2024-09-23T10:29:41+00:00","updatedAt":"2024-09-23T10:29:41+00:00"}
curl --location --request POST 'https://zylalabs.com/api/5158/safe+mail+api/6580/fetch+mail+info' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"address": "[email protected]",
"password": "temp1234"
}'
To use this endpoint, send a POST request to list all messages received at the temporary email address.
List Inbox Messages - Endpoint Features
Object | Description |
---|---|
Request Body |
[Required] Json |
{"totalItems":1,"member":[{"@id":"\/messages\/66f14386e566add59c7c8b0e","@type":"Message","id":"66f14386e566add59c7c8b0e","msgid":"\[email protected]\u003E","from":{"address":"[email protected]","name":"Mike - API Factory"},"to":[{"address":"[email protected]","name":""}],"subject":"Hi there!","intro":"Hi, This is an example of an email which contains an attachment. I hope you enjoy our API.","seen":false,"isDeleted":false,"hasAttachments":true,"size":139343,"downloadUrl":"\/messages\/66f14386e566add59c7c8b0e\/download","sourceUrl":"\/sources\/66f14386e566add59c7c8b0e","createdAt":"2024-09-23T10:31:17+00:00","updatedAt":"2024-09-23T10:31:34+00:00","accountId":"\/accounts\/66f14315e3b0f42dc107daab"}]}
curl --location --request POST 'https://zylalabs.com/api/5158/safe+mail+api/6581/list+inbox+messages' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"address": "[email protected]",
"password": "temp1234"
}'
To use this endpoint, make a POST request to retrieve the details of a specific message received in the temporary account.
Fetch Single Message - Endpoint Features
Object | Description |
---|---|
Request Body |
[Required] Json |
{"id":"66f14386e566add59c7c8b0e","msgid":"\[email protected]\u003E","from":{"address":"[email protected]","name":"Mike - API Factory"},"to":[{"address":"[email protected]","name":""}],"cc":[],"bcc":[],"subject":"Hi there!","intro":"Hi, This is an example of an email which contains an attachment. I hope you enjoy our API.","seen":false,"flagged":false,"isDeleted":false,"verifications":{"tls":false,"spf":false,"dkim":false},"retention":true,"retentionDate":"2024-09-30T10:31:34+00:00","text":"Hi,\nThis is an example of an email which contains an attachment.\nI hope you enjoy our API.","html":["Hi,\u003Cbr\u003EThis is an example of an email which contains an attachment.\u003Cbr\u003EI hope you enjoy our API."],"hasAttachments":true,"attachments":[{"id":"ATTACH000001","filename":"test_file.pdf","contentType":"application\/octet-stream","disposition":"attachment","transferEncoding":"base64","related":false,"size":99,"downloadUrl":"\/messages\/66f14386e566add59c7c8b0e\/attachment\/ATTACH000001"}],"size":139343,"downloadUrl":"\/messages\/66f14386e566add59c7c8b0e\/download","sourceUrl":"\/sources\/66f14386e566add59c7c8b0e","createdAt":"2024-09-23T10:31:17+00:00","updatedAt":"2024-09-23T10:31:34+00:00","accountId":"\/accounts\/66f14315e3b0f42dc107daab"}
curl --location --request POST 'https://zylalabs.com/api/5158/safe+mail+api/6582/fetch+single+message' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"messageId": "66f14386e566add59c7c8b0e",
"address": "[email protected]",
"password": "temp1234"
}'
To use this endpoint, make a POST request to download the attachments of a message received at the temporary email address.
Download Mail Attachment - Endpoint Features
Object | Description |
---|---|
Request Body |
[Required] Json |
{ "response": "https://files.bemnacabine.com/temp/66f14386e566add59c7c8b0e_ATTACH000001.pdf" }
curl --location --request POST 'https://zylalabs.com/api/5158/safe+mail+api/6583/download+mail+attachment' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"attachmentId": "ATTACH000001",
"attachmentExtension": "pdf",
"messageId": "66f14386e566add59c7c8b0e",
"address": "[email protected]",
"password": "temp1234"
}'
Header | Description |
---|---|
Authorization
|
[Required] Should be Bearer access_key . See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
Send a POST request to generate a temporary email address, retrieve messages, or download attachments.
The Safe Mail API it is an API that generates temporary mails to protect the user's privacy and avoid spam in your personal inbox.
The API receives POST requests and generates temporary emails, displaying messages and allowing attachments to be downloaded.
Create temporary emails to register for services without compromising personal data. Retrieve verification messages in temporary emails for testing (QA). Download attachments without using a personal email.
Beside the number of API calls per month allowed, there are no other limitations.
There are different plans suits everyone including a free trial for small amount of requests, but itβs rate is limit to prevent abuse of the service.
The API uses API keys for authentication. To access the API, include your API key in the request header. The API key is provided upon registration and should be kept secure.
The API returns detailed information about the age and history of a domain, including years, months and days since its creation, as well as expiration and update dates.
Each endpoint returns JSON data. For example, the "Generate Temp Mail" endpoint provides an email address and metadata like creation date, while "List Inbox Messages" returns message details including sender, subject, and attachment information.
Key fields include "address" (temporary email), "createdAt" (creation timestamp), "msgid" (message ID), "subject" (email subject), and "downloadUrl" (for attachments). These fields help identify and manage emails effectively.
The endpoints primarily accept POST requests. For "Generate Temp Mail," no additional parameters are required, while "Fetch Mail Info" and "Fetch Single Message" require the email ID to retrieve specific data.
Response data is structured in JSON format, with nested objects for complex data. For instance, "List Inbox Messages" includes an array of messages, each with fields like "from," "to," and "hasAttachments," facilitating easy parsing.
The API provides information on temporary email addresses, inbox messages, message details, and attachments. Users can access metadata about emails, including sender details and message content.
Users can utilize the returned data to manage temporary emails, track received messages, and download attachments. For example, the "downloadUrl" field allows users to access files directly from the response.
Typical use cases include signing up for online services without revealing personal emails, testing email functionalities in applications, and retrieving verification emails for account setups.
Data accuracy is maintained through automated systems that ensure temporary emails are valid for the specified duration and that messages are correctly associated with their respective email addresses.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the worldβs most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]
Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the βX-Zyla-API-Calls-Monthly-Remainingβ field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.
To see the maximum number of API requests your plan allows, check the βX-Zyla-RateLimit-Limitβ response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.
The βX-Zyla-RateLimit-Resetβ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.
Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]
To give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.
After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, itβs important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.
Service Level:
100%
Response Time:
5,545ms
Service Level:
100%
Response Time:
330ms
Service Level:
100%
Response Time:
797ms
Service Level:
100%
Response Time:
120ms
Service Level:
100%
Response Time:
868ms
Service Level:
100%
Response Time:
1,449ms
Service Level:
100%
Response Time:
1,089ms
Service Level:
100%
Response Time:
10,123ms
Service Level:
100%
Response Time:
490ms
Service Level:
100%
Response Time:
1,600ms
Service Level:
100%
Response Time:
1,192ms
Service Level:
100%
Response Time:
764ms
Service Level:
100%
Response Time:
2,553ms
Service Level:
100%
Response Time:
621ms
Service Level:
100%
Response Time:
499ms
Service Level:
100%
Response Time:
1,956ms
Service Level:
100%
Response Time:
847ms
Service Level:
100%
Response Time:
3,064ms
Service Level:
100%
Response Time:
2,125ms
Service Level:
100%
Response Time:
696ms