Openapi.com pricing and alternatives: email verification API, POST / email-advanced/ {email}
- Top-up, Single requestSingle request$55.14 per 1,000
- €45 monthly1000 API Calls/month (Pay Monthly)$50.639 per 1,000
- €190 monthly5000 API Calls/month (Pay Monthly)$42.761 per 1,000
- €290 monthly10000 API Calls/month (Pay Monthly)$54.39 per 1,000
- €500 monthly20000 API Calls/month (Pay Monthly)$28.133 per 1,000
- €950 monthly50000 API Calls/month (Pay Monthly)$21.381 per 1,000
- €250 yearly100000 API Calls/year$2.813 per 1,000
- €504 yearly1000 API Calls/month (Pay Annually)$47.263 per 1,000
- €1,150 yearly500000 API Calls/year$2.588 per 1,000
- €2,000 yearly1000000 API Calls/year$2.251 per 1,000
- €2,040 yearly5000 API Calls/month (Pay Annually)$38.26 per 1,000
- €3,120 yearly10000 API Calls/month (Pay Annually)$48.763 per 1,000
- €5,000 yearly5000000 API Calls/year$1.125 per 1,000
- €6,000 yearly20000 API Calls/month (Pay Annually)$28.133 per 1,000
- €8,000 yearly10000000 API Calls/year$0.90 per 1,000
- €11,400 yearly50000 API Calls/month (Pay Annually)$21.381 per 1,000
POST / email-advanced/ {email} one of Openapi.com's 2 callsPOST /Top-up, Single request$55.14 per 1,000email-advanced/ {email} POST /Top-up, Single request$3.376 per 1,000email-start/ {email}
- Email verification API
- Phone validation API
POST /mobile-advanced/ {mobile-phone-number} - Phone validation API
POST /phone-advanced/ {phone-number} - Phone validation API
POST /mobile-start/ {mobile-phone-number}
About this item
- Freshness. We don't know how fresh this plan's data is.
- 4 of the 6 key fields we check. Address, Deliverability, Confidence, Name.
- A balance you top up. You pay any amount. You spend all of it on calls.
- One call. You send
emailtoPOST /. You can also sendemail-advanced/ {email} callback. The call returns the answer when the provider is quick. When the provider is slow, the call returns a job. You fetch the answer once the job is done. - Who can get it: with conditions. Keep data: no limit. Use data: with conditions.
Openapi.com: email verification API alternatives
We list other providers' plans closest to this plan in price per 1,000 emails.
| This planOpenapi.com, top-up, Single request, POST /email-advanced/{email} | DeBounce, top-up from $25, 10K credits, GET /v1/, Single email validation, full | TrekMail, $96 yearly, Pro, POST /verify, Verify one address (deep) | Dropcontact, €288 yearly | Tomba, $3,648 pack, Scale 400k, GET /email-verifier, Email Verifier, full | |
|---|---|---|---|---|---|
| $ per 1,000 | $55.14 | $52.50 | $53.333 | $54.014 | $54.72 |
| Completeness | 67% | 50% | 50% | 33% | 50% |
| Billing | pay first | pay first | yearly | yearly | pay first |
| Pay | any amount | $25 | $96 | €288 | $3,648 |
| Enough for | as many as you pay for | about 476 calls | 150 calls a month | 500 results a month | about 66,666 calls |
| Freshness | unknown | live | live | live | live |
| Who can get it | anyone acting in the course of their business, entrepreneurial or professional activity | anyone over 18 | anyone at least 18 years of age (or the age of majority in their jurisdiction) and not barred from receiving services under sanctions laws | professionals acting within their activity (a natural person with the power to commit, or a legal person) | anyone 18 or over |
Sources
From each provider's own pricing page and docs, and from what providers tell us. We read this row from these pages on 2026-10-25.
Product details
The key fields this plan's answer can hold, then each filled column in its row on the sheet.
- Address
- Deliverability
- Confidence
- Name
- Place, not in the answer
- Company, not in the answer
| $ per 1,000 | $55.14 |
|---|---|
| Billing | pay first |
| Aggregators | none |
|---|
| Per | call |
|---|---|
| Also pays for | from the same budget: API Services |
| Their pitch | Verify the validity and characteristics of an email address, with more detailed data than the Start service, such as deliverability rate and unsubscription frequency, in just a few seconds and on a global level. |
|---|
| Keep data | no limit |
|---|---|
| Use data | The data and information provided by Openapi are for the exclusive use of the Customer, who is prohibited from copying, reproducing, assigning to third parties on any grounds and/or using them for purposes other than those expressly established in the Agreement, unless expressly authorised by Openapi and subject to the Customer undertaking to comply with the instructions provided. In particular, to obtain such authorisation, the Customer must provide Openapi with assurances: (i) that it has informed its customers that the data they provide will be transmitted to third parties for the provision of the requested service, (ii) that it has adopted an adequate privacy policy and processes its customers’ data according to security and confidentiality standards no lower than those offered by Openapi’s Privacy Policy, (iii) that it adopts all measures required by applicable law or otherwise suitable to preserve the confidentiality and security of the data provided by its customers. [...] The Customer is also prohibited from: [...] (v) using the APIs and/or the Services for purposes or in a manner that causes damage to Openapi, the Suppliers or third parties and/or violates any provision of law [...] |
| Expires | 12 months after the last top-up |
|---|
| Per second | 20 |
|---|---|
| Batch | 1 |
| Answer | in the call or by polling |
|---|
| You send | email. Optional: callback |
|---|---|
| Method | POST |
| Path | /email-advanced/{email} |
| Plan | Single request |
|---|---|
| Who can get it | anyone acting in the course of their business, entrepreneurial or professional activity |
The 37 fields the plan's answer can hold
request ID, email, SPF details, DMARC details, SPF record, DMARC record, valid, disposable, SMTP score, overall score, first name, generic address, known provider, DNS valid, honeypot, deliverability, frequent complainer, spam trap score, catch-all, timed out, suspect, recent abuse, fraud score, suggested domain, leaked, sanitized email, identity data, domain age, first seen, risky TLD, MX records, A records, request state, created at, updated at, message, success
Best GTM APIs
- Best LinkedIn profile API in 2026
- Best cached LinkedIn profile API in 2026
- Best email finder API in 2026
- Best cached email finder API in 2026
- Best email verification API in 2026
- Best cached email verification API in 2026
- Best phone finder API in 2026
- Best cached phone finder API in 2026
- Best LinkedIn company data API in 2026
- Best cached LinkedIn company data API in 2026
- Best phone validation API in 2026
- Best LinkedIn post comment API in 2026
- Best LinkedIn post reaction API in 2026
- Best company technology API in 2026
- Best cached company technology API in 2026
- Best LinkedIn person post API in 2026
- Best LinkedIn company post API in 2026
- Best company funding API in 2026
- Best LinkedIn people search API in 2026
- Best cached LinkedIn people search API in 2026
- Best LinkedIn company search API in 2026
- Best cached LinkedIn company search API in 2026
- Best LinkedIn job search API in 2026
- Best cached LinkedIn job search API in 2026
- Best reverse email lookup API in 2026
- Best cached reverse email lookup API in 2026
- Best LinkedIn post search API in 2026
- Best LinkedIn post details API in 2026
- Best LinkedIn job details API in 2026
- Best LinkedIn person comment API in 2026
- Best LinkedIn person reaction API in 2026
- Best company enrichment API in 2026
- Best people search API in 2026
- Best cached people search API in 2026
- Best company discovery API in 2026
- Best job postings API in 2026
- Best job posting details API in 2026
- Best people enrichment API in 2026