{
"success": true,
"data": {
"valid": true,
"block": false,
"disposable": false,
"mx_found": true,
"mx_host": "gmail-smtp-in.l.google.com.",
"risk": 0,
"reason": "OK"
},
"error": null
}
curl --location --request GET 'https://zylalabs.com/api/13465/go+temp+email+blocker+api/29510/[email protected][email protected]' --header 'Authorization: Bearer YOUR_API_KEY'
{
"success": true,
"data": {
"summary": {
"total": 3,
"valid": 2,
"invalid": 1,
"risky": 0,
"duplicates": 0,
"processing_time_ms": 139
},
"results": [
{
"email": "[email protected]",
"valid": true,
"block": false,
"disposable": false,
"mx_found": true,
"mx_host": "gmail-smtp-in.l.google.com.",
"risk": 0,
"reason": "OK"
},
{
"email": "[email protected]",
"valid": false,
"block": true,
"disposable": true,
"mx_found": true,
"mx_host": "mail.mailinator.com.",
"risk": 100,
"reason": "Disposable domain"
},
{
"email": "[email protected]",
"valid": true,
"block": false,
"disposable": false,
"mx_found": true,
"mx_host": "outlook-com.olc.protection.outlook.com.",
"risk": 0,
"reason": "OK"
}
]
},
"error": null
}
curl --location --request POST 'https://zylalabs.com/api/13465/go+temp+email+blocker+api/29511/bulk+validate+emails' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"emails": [
"[email protected]",
"[email protected]",
"[email protected]"
]
}'
{
"success": true,
"data": {
"domain": "gmail.com",
"valid": true,
"disposable": false,
"blacklisted": false,
"WHOIS": {
"registrar": "MarkMonitor Inc.",
"registered_at": "1995-08-13T04:00:00Z",
"expires_at": "2027-08-12T04:00:00Z",
"age_days": 11316,
"country": "US",
"expired": false
},
"DNS": {
"has_mx": true,
"has_spf": true,
"has_dmarc": true,
"has_a": true,
"mx_records": [
"gmail-smtp-in.l.google.com.",
"alt1.gmail-smtp-in.l.google.com.",
"alt2.gmail-smtp-in.l.google.com.",
"alt3.gmail-smtp-in.l.google.com.",
"alt4.gmail-smtp-in.l.google.com."
],
"spf_record": "v=spf1 redirect=_spf.google.com",
"dmarc_record": "v=DMARC1; p=none; sp=quarantine; rua=mailto:[email protected]"
},
"risk": 0,
"reason": "OK"
},
"error": null
}
curl --location --request GET 'https://zylalabs.com/api/13465/go+temp+email+blocker+api/29514/validate+domain?domain=gmail.com&domain=gmail.com' --header 'Authorization: Bearer YOUR_API_KEY'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Go Temp Email Blocker API simply include your bearer token in the Authorization header.
| 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.
Production-ready email validation API built with Go. Detect disposable emails, validate MX records, check domain reputation, WHOIS data, DNS analysis and risk scoring.
Each endpoint returns detailed validation data. The GET Validate Email endpoint provides analysis on a single email, including validity, disposable status, and risk score. The POST Bulk Validate Emails endpoint returns a summary of multiple emails, including counts of valid, invalid, and risky emails, along with individual results. The GET Validate Domain endpoint offers comprehensive domain analysis, including WHOIS data, DNS records, and blacklist status.
Key fields in the response data include "valid" (indicating if the email/domain is valid), "disposable" (whether it's from a disposable provider), "mx_found" (MX record verification), "risk" (risk score from 0-100), and "reason" (explanation for the validation result). For domain validation, additional fields like "WHOIS" and "DNS" provide insights into domain registration and DNS records.
The response data is structured in a JSON format. Each response contains a "success" boolean, a "data" object with relevant details, and an "error" field if applicable. For example, the "data" object in the GET Validate Email response includes fields like "valid," "disposable," and "risk," allowing users to easily access and interpret the validation results.
The GET Validate Email endpoint provides email validity, disposable status, and risk scoring. The POST Bulk Validate Emails endpoint offers a summary of multiple email validations, including counts of valid and invalid emails. The GET Validate Domain endpoint delivers WHOIS data, DNS records, blacklist checks, and risk scoring, giving users a comprehensive view of the domain's reputation and status.
Users can customize requests by specifying the email addresses or domains they wish to validate. For the POST Bulk Validate Emails endpoint, users can submit a list of emails, and the API will automatically deduplicate them before processing. This allows for efficient validation of multiple emails in a single request.
The data sources include DNS records for MX, SPF, and DMARC checks, WHOIS databases for domain registration information, and various blacklist services like Spamhaus and Barracuda. This multi-source approach enhances the accuracy and reliability of the validation results provided by the API.
Typical use cases include validating user sign-ups to prevent fake accounts, ensuring email deliverability for marketing campaigns, and assessing domain reputation for security purposes. Businesses can leverage this data to improve their email communication strategies and reduce risks associated with invalid or disposable emails.
Users can utilize the returned data by analyzing the "valid," "disposable," and "risk" fields to make informed decisions. For instance, if an email is marked as disposable, it may be excluded from marketing lists. The risk score can help prioritize follow-up actions, while WHOIS and DNS data can inform domain-related decisions.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
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.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund