POST /api/v1/bulk-taskscurl -X POST "https://emailcheckpro.com/api/v1/bulk-tasks" \
-H "X-API-Key: sk_your_api_key" \
-F service_type=email_avatar_batch \
-F file=@emails.txtBulk product email_avatar_batch
Upload a whole file of addresses and download the public profile photos when the task finishes.
An add-on for whole large lists — for a handful of email addresses the realtime check answers in the same request. Realtime check →
API contract
Submitting returns a task id right away; check the task by that id and, once it succeeds, the response carries the result file download link. Each request is shown with its own response.
Balance for the valid lines is reserved, to be settled on completion, and the task starts running in the background.
POST /api/v1/bulk-taskscurl -X POST "https://emailcheckpro.com/api/v1/bulk-tasks" \
-H "X-API-Key: sk_your_api_key" \
-F service_type=email_avatar_batch \
-F file=@emails.txt200 OK{
"code": 0,
"msg": "ok",
"data": {
"id": "3f9c2a7d8e4b4c1a9f0e6b2d5c8a7e13",
"product": "email_avatar_batch",
"status": "processing",
"total": 1000,
"created_at": "2026-09-08T09:30:00Z"
}
}Poll by task id. A successful response carries the success and failure counts and the result file download link.
GET /api/v1/bulk-tasks/{id}curl "https://emailcheckpro.com/api/v1/bulk-tasks/3f9c2a7d8e4b4c1a9f0e6b2d5c8a7e13" \
-H "X-API-Key: sk_your_api_key"200 OK{
"code": 0,
"msg": "ok",
"data": {
"id": "3f9c2a7d8e4b4c1a9f0e6b2d5c8a7e13",
"product": "email_avatar_batch",
"status": "success",
"total": 1000,
"success_cnt": 990,
"failure_cnt": 10,
"result_url": "https://…/result.zip",
"created_at": "2026-09-08T09:30:00Z"
}
}How it runs
Bulk is not realtime made bigger — it is submit once, run in the background, collect later. You do not need to keep the page open; task state and results stay in your dashboard.
A .txt or .csv with one email address per line. It is streamed straight through; nothing is written to disk.
Format and provider-scope rules are checked first, then balance is reserved for the valid lines and settled on completion. Nothing is charged if the precheck fails.
The task runs on its own — close the page if you like. A failure is reported straight away and fully refunded.
Collect the file from the bulk check page. You pay only for email addresses that actually returned a result; the difference is refunded.
Result fields
The download is a zip: alongside this full table it splits registered and unregistered email addresses into separate lists.
email · alex.kim@gmail.comactivated · yesavatar · https://lh3.googleusercontent.com/a/exampleBest for
Direct answer
Bulk avatar check covers the three providers that expose a public profile photo — Gmail, Yandex and Mail.ru. Mix them freely in one file; each address is routed to the right provider. The result gives the address, whether a public photo is set, the photo URL, and the display name where the provider exposes one. Addresses outside these three are rejected before the file is billed.
Clear boundaries
When bulk fits
| Realtime check | Bulk check | |
|---|---|---|
| How many email addresses | 1 email address per single check; several per multi request — exact caps are in the API docs | A whole large list in one task — the current size range is on the pricing page |
| Getting results | Right away: single and multi-endpoint answer in the same response; the dashboard returns them one by one | Download a result file when the task finishes |
| Provider scope | No restriction — mix freely in one request | The full-address check takes any domain in one file; the avatar check accepts Gmail, Yandex and Mail.ru mixed in one file, and nothing outside those three |
| Result shape | JSON, fields per email address | Result file (zip with the full table and split lists) |
| Typical use | Form validation, agent lookups, pre-send gating | List hygiene, pre-campaign filtering, stored-data cleanup |
Product FAQ
Use bulk for a whole large list. For a handful of email addresses the realtime check answers in the same request, with no task to schedule.
The precheck drops malformed lines, so they never enter the billable count. Of the email addresses that remain, any the upstream cannot resolve are not charged either. You pay only for email addresses that actually return a result.
It depends on the email address count and the product. You can close the page after submitting; the task runs in the background and the result waits for you on the bulk check page.
Yes. A failed task is refunded in full. If the task succeeds but some email addresses return nothing, that portion is refunded automatically. The difference between the reserved amount and what was actually charged always comes back.
Bulk and realtime checks draw on the same balance — nothing extra to enable. Sign up and upload your first file on the bulk check page.