The Temp Email Detector API will allow you to know if a given email is a disposable/temporary account. So, you won't be worried about letting temporary emails go through your forms. Also, you will be able to recognize if a given email is invalid or not.
Just with the email domain, you will be able to know if the address is valid or not and if it's a disposable or temporary account as well.
This API is ideal to know beforehand if an email a user passing to your forms is a valid one, or if it's disposable or not. So you can use it as a filter on your login forms or contact forms as well. So only valid emails can be in touch or login into your products/services.
Also, you can search through your database, and detect if there are any invalid or disposable emails before sending an email campaign.
This will prevent a lot of bounce rates and will improve your campaigns or contacts a lot.
The only limitation is the number of API calls you can make per month.
Check if an e-mail domain is valid, if it's a temporary/disposable address, or even if the domain is not working.
Invalid domains (typos, non-responding mailserver, etc) will return "valid: false", "block: true".
Disposable e-mail domains will return "valid: true" (since it's a valid domain), but "block: true" and "disposable: true".
Endpoint JSON response example (if e-mail is not valid):
Continue with Google
Continue with Github{
"valid": false,
"block": true,
"disposable": false,
"domain": null,
"text": "Invalid domain",
"reason": "Domain is not a valid host",
"risk": 10,
"mx_host": null,
"possible_typo": null,
"mx_ip": null,
"mx_info": null,
"last_changed_at": "2022-06-22T17:47:02+00:00"
}
Endpoint JSON response example (if e-mail is valid):
{
"valid": true,
"block": false,
"disposable": false,
"domain": "gmail.com",
"text": "Looks okay",
"reason": "Whitelisted",
"risk": 8,
"mx_host": "gmail-smtp-in.l.google.com",
"possible_typo": [],
"mx_ip": "172.253.63.26",
"mx_info": "Using MX pointer gmail-smtp-in.l.google.com from DNS with priority: 5",
"last_changed_at": "2020-04-14T20:33:28+02:00"
}
{"valid":true,"block":false,"disposable":false,"domain":"gmail.com","text":"Looks okay","reason":"Whitelisted","risk":8,"mx_host":"gmail-smtp-in.l.google.com","possible_typo":[],"mx_ip":"172.253.63.26","mx_info":"Using MX pointer gmail-smtp-in.l.google.com from DNS with priority: 5","last_changed_at":"2020-04-14T20:33:28+02:00"}
| Object | Description |
|---|---|
domain |
[Required] Full e-mail, or domain to check if valid or temporary/disposable. You can enter an e-mail address, and it will be converted to a domain, but entering just the domain is recommended for user privacy reasons. |
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 E-Mail Verificator and Temp Emails Detector API REST 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 commitments. One click upgrade/downgrade or cancellation. No questions asked.
Zyla API Hub is, in other words, an API MarketPlace. An all-in-one solution for your developing needs. You will be accessing our extended list of APIs with only your user. Also, you won't need to worry about storing API keys, only one API key for all our products is needed.
Prices are listed in USD. 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 with paying by card, just contact us at [email protected]
Sometimes depending on the bank's fraud protection settings, a bank will decline the validation charge we make when we attempt to be sure a card is valid. We recommend first contacting your bank to see if they are blocking our charges. If more help is needed, please contact [email protected] and our team will investigate further
Prices are based on a recurring monthly subscription depending on the plan selected — plus overage fees applied when a developer exceeds a plan’s quota limits. In this example, you'll see the base plan amount as well as a quota limit of API requests. Be sure to notice the overage fee because you will be charged for each additional request.
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.
Just go to the pricing page of that API and select the plan that you want to upgrade to. You will only be charged the full amount of that plan, but you will be enjoying the features that the plan offers right away.
Yes, absolutely. If you want to cancel your plan, simply go to your account and cancel on the Billing page. Upgrades, downgrades, and cancellations are immediate.
You can contact us through our chat channel to receive immediate assistance. We are always online from 9 am to 6 pm (GMT+1). If you reach us after that time, we will be in contact when we are back. Also you can contact us via email to [email protected]
