POST /api/v1/bulk-taskscurl -X POST "https://carrierlookup.online/api/v1/bulk-tasks" \
-H "X-API-Key: sk_your_api_key" \
-F service_type=carrier_batch \
-F country=US \
-F file=@numbers.txtBulk product carrier_batch
Upload a whole file of numbers and download the carrier data when the task finishes.
An add-on for whole large lists — for a handful of numbers 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://carrierlookup.online/api/v1/bulk-tasks" \
-H "X-API-Key: sk_your_api_key" \
-F service_type=carrier_batch \
-F country=US \
-F file=@numbers.txt200 OK{
"code": 0,
"msg": "ok",
"data": {
"id": "3f9c2a7d8e4b4c1a9f0e6b2d5c8a7e13",
"product": "carrier_batch",
"status": "processing",
"country": "US",
"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://carrierlookup.online/api/v1/bulk-tasks/3f9c2a7d8e4b4c1a9f0e6b2d5c8a7e13" \
-H "X-API-Key: sk_your_api_key"200 OK{
"code": 0,
"msg": "ok",
"data": {
"id": "3f9c2a7d8e4b4c1a9f0e6b2d5c8a7e13",
"product": "carrier_batch",
"status": "success",
"country": "US",
"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 number per line. It is streamed straight through; nothing is written to disk.
Format and country 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 numbers that actually returned a result; the difference is refunded.
Result fields
The download is a zip containing the full result table.
number · 17253100591 — The original phone number written into the result file.carrier · T-Mobile — The carrier the number was originally allocated to; not the current carrier after porting.underlying_carrier — Underlying carrier information returned by the platform; empty when unavailable.number_type · Fixed Line or Mobile — The line type returned by the platform, such as fixed line or mobile.country_code · US — The ISO country code the number belongs to.region · NV — The allocation region; empty when the platform does not provide one.city · LAS VEGAS — The allocation city; empty when the platform does not provide one.Best for
Organise a full number list by original carrier, line type and allocation country or region in a downloadable result file.
Use carrier and region columns to compare internal routing, procurement or cost records without checking numbers one by one.
Find number records missing an original carrier, region or city and create a list for completion and human review. Separate empty, incomplete and inconsistent records so they do not enter later analysis unnoticed.
Suggested workflow: mark records for review, export the list for data completion, then write it back or run the lookup again.
Direct answer
Bulk carrier lookup is built for lists from a thousand numbers upward: upload a file, the task runs in the background, and you download a result archive when it completes. Pick the country the numbers belong to when you upload: it is submitted with the file, completes any number that has no country code, and the file is checked against it.
Clear boundaries
When bulk fits
| Realtime check | Bulk check | |
|---|---|---|
| How many numbers | 1 number 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 |
| Country | None to pick — each number carries its own country code, mix freely in one request | One country per task, selected at upload and submitted with the file |
| Result shape | JSON, fields per number | 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 numbers 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 numbers that remain, any the upstream cannot resolve are not charged either. You pay only for numbers that actually return a result.
It depends on the number 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 numbers 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.