Create a batch of email address lookups
Assesses up to 1,000 email addresses synchronously and returns one result per input in submission order. Malformed addresses receive individual assessments. Duplicate addresses remain separate entries and each answered entry is billed at the email lookup rate. Use Create an email address lookup for a single address. A batch consumes one request allowance under the shared lookup rate limit, regardless of its number of addresses.
Requests must fit within 128 KiB. Split larger lists into separate requests. Reuse an Idempotency-Key for retries of the same batch. Successful responses up to 256 KiB can be retained for replay; larger responses are returned but are not retained, so retrying can perform and charge for another batch. An unavailable lookup returns 503 without charging for the batch.
Request
- Base URL: https://us1.platform.bird.com
- URL: https://us1.platform.bird.com/v1/lookup/email/batch
- Auth: one of:
- HTTP bearer
- API key in cookie bird_session
Headers
Client-supplied key. On operations supporting request deduplication, a retained response is replayed for duplicate requests with the same key within the idempotency window (3 hours by default). This protection requires a workspace, organization, or staff-account scope. User-only and unscoped unauthenticated operations, streams, and operations with a separate replay contract do not use this response replay.
On a supported operation, if idempotency protection is unavailable before execution, the API returns 503 IdempotencyUnavailable (E01033) without executing this attempt. Retry with backoff using the same key and request. An operation that takes effect before its response is retained can still execute again on retry.
Two distinct 409 errors signal misuse:
- request_in_progress (E01004): The same key is currently being processed by a concurrent request. Wait briefly and retry. The lock expires within 30 seconds.
- idempotency_key_reuse (E01005): The same key has already completed against a different request body or method. Generate a new key.
Recommended key format is <event-type>/<entity-id> (for example welcome-user/usr_abc123).
Workspace context for the request. Required for dashboard authentication and master keys. Workspace keys and access tokens already identify their workspace; send that workspace or omit the header. A different one is rejected.
Organization context for the request. Required for dashboard authentication. An API key or access token carries its own organization, so send either that organization or no header at all; a different one is rejected.
Request body
Example request
{
"emails": [
"aisha.khan@example.com",
"not-an-email"
]
}Response
Completed assessments in submission order.
Example response
{
"data": [
{
"email": "aisha.khan@example.com",
"valid": true,
"result": "risky",
"delivery_confidence": 42,
"flags": [
"role",
"free_provider"
]
}
]
}Changes
No recorded changes to this operation across all 2 revisions of this API.