Email Verification API
Email Verification Icypeas API
Verify an email address. A valid negative verdict is a successful, billable result.
POST/v1/run/email_verification.icypeas
Uptime
54.55%
30d · 88 calls
Requests
88
30d
Response
5.8s
median · 30d
Try it
Make your first request
Sample response
Free runs return only the first 3 results. Fund a key to get the full response.
{
"data": {
"certainty": "example",
"createdUtc": 12.5,
"email": "alex@example.com",
"firstname": "Alex",
"fullname": "Alex Rivera",
"gender": "example",
"lastname": "Rivera",
"linkedinUrl": "https://example.com/page",
"modifiedUtc": 12.5,
"mxProvider": "a1b2c3d4",
"mxRecords": [
"example"
],
"phones": null,
"saasServices": null,
"scanId": "a1b2c3d4",
"scanName": "Example title",
"scanOrder": 1,
"scanUser": "example",
"status": "active"
},
"found": true
}Response interface
interface EmailVerificationIcypeasResponse {
data: {
certainty?: string;
createdUtc?: number;
email?: string;
firstname?: string;
fullname?: string;
gender?: string;
lastname?: string;
linkedinUrl?: string;
modifiedUtc?: number;
mxProvider?: string;
mxRecords?: string[];
phones?: any;
saasServices?: any;
scanId?: string;
scanName?: string;
scanOrder?: number;
scanUser?: string;
status: string;
} | null;
found: boolean;
}Full parameter and response reference - every field, type, and example for this endpoint.
Reference
Request, response, and price
Last verified 2026-09-16 · uptime and latency measured over 30dPOST /v1/run/email_verification.icypeas
curl -X POST https://api.getanyapi.com/v1/run/email_verification.icypeas \
-H "Authorization: Bearer $ANYAPI_KEY" \
-H "Content-Type: application/json" \
-d '{"email":"support@stripe.com"}'| Field | Type | Example value |
|---|---|---|
| Request body | ||
| string | "support@stripe.com" | |
| Response | ||
| data | object | Normalized verification result. |
| data.certainty | string | Confidence rating for the address, returned verbatim as the source spells it (ultra_sure in the captured response). It is not remapped to another verdict vocabulary. |
| data.createdUtc | number | UTC epoch timestamp in seconds (Unix time). Multiply by 1000 for a JS Date in milliseconds. |
| data.email | string | The verified email address as the source returned it. |
| data.firstname | string | First name carried by the source's scan record. Present only when that record holds identity data, which the verification path usually does not. |
| data.fullname | string | Full name carried by the source's scan record. Present only when that record holds identity data, which the verification path usually does not. |
| data.gender | string | Gender carried by the source's scan record, returned verbatim. Present only when that record holds identity data, which the verification path usually does not; the source's UNKNOWN sentinel is reported as absent. |
| data.lastname | string | Last name carried by the source's scan record. Present only when that record holds identity data, which the verification path usually does not. |
| data.linkedinUrl | string | LinkedIn profile URL carried by the source's scan record. Present only when that record holds identity data, which the verification path usually does not. |
| data.modifiedUtc | number | UTC epoch timestamp in seconds (Unix time). Multiply by 1000 for a JS Date in milliseconds. |
| data.mxProvider | string | Mail provider detected from the address domain's MX records. |
| data.mxRecords | string[] | MX record hosts published by the address domain. |
| data.phones | any | Phone numbers carried by the source's scan record, passed through in whatever shape the source returns them. Empty in the captured response and absent when the source holds none, so this field is not type-constrained. |
| data.saasServices | any | SaaS services carried by the source's scan record, passed through in whatever shape the source returns them. Empty in the captured response and absent when the source holds none, so this field is not type-constrained. |
| data.scanId | string | The source's own identifier for the scan record behind this verification, surfaced so a result can be traced back to it at the source. |
| data.scanName | string | The source's own label for the kind of scan record it created, returned verbatim (__icypeas__individual in the captured response). It is not a person's name. |
| data.scanOrder | integer | Position the source assigned to this record within the scan it belongs to; 0 for a single-address verification. |
| data.scanUser | string | The source's own identifier for the account that ran the scan. |
| data.status | string | Scan outcome for the address, returned verbatim as the source spells it (FOUND in the captured response; the scan also reports NOT_FOUND). This is not the good/risky/bad vocabulary used by email.verify. |
| found | boolean | Whether the source returned a completed verification. A negative verdict is a successful, billable result. |
| Price | ||
| Price per request | USD | $0.0024 |
| Price /1k req | USD | $2.40 |
FAQ
About the Email Verification Icypeas API
The AnyAPI Email Verification Icypeas API returns Email Verification icypeas data as normalized JSON from one POST call to /v1/run/email_verification.icypeas. Verify an email address. A valid negative verdict is a successful, billable result. AnyAPI returns one normalized schema whichever source serves it. It costs from $2.40 per 1,000 requests, in US dollars with no subscription and no monthly minimum. Over the last 30 days, 54.5% of Email Verification icypeas calls through AnyAPI succeeded, with a median response time of 5.8 seconds across 88 measured calls.
It costs from $2.40 per 1,000 requests, in US dollars with no subscription and no monthly minimum. You fund one USD wallet, each call draws it down, and a failed request costs $0.
Verify an email address. A valid negative verdict is a successful, billable result. The response is normalized JSON with the same envelope every AnyAPI endpoint returns, so parsing a second endpoint is a change of URL and nothing else.
Over the last 30 days, 54.5% of Email Verification icypeas calls through AnyAPI succeeded, with a median response time of 5.8 seconds across 88 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.
More to call