Line Profile Checker API: Bulk Account Profile Detection
Check Line registration and return the fields available in the current Line sample output.. The task uses the standard asynchronous batch workflow.
Input format
Upload a text file with one phone numbers per line. Normalize values before upload; for phone numbers, E.164 format is recommended.
+14155552671+442071838750Create a task
POST https://api.numberchecker.ai/v1/tasks
curl --location 'https://api.numberchecker.ai/v1/tasks' \--header 'X-API-Key: YOUR_API_KEY' \--form 'file=@"./input.txt"' \--form 'task_type="line_senior"'The API returns a task ID. Keep this ID and use it to poll the task status.
Upload response
{ "task_id": "d4g8o46p2jvh04o9uolg", "status": "pending", "total": 5000, "estimated_amount": { "amount": "0.500000", "currency": "USD" }, "message": "Task created successfully"}Check task status
POST https://api.numberchecker.ai/v1/gettasks
curl --location 'https://api.numberchecker.ai/v1/gettasks' \--header 'X-API-Key: YOUR_API_KEY' \--form 'task_id="d4g8o46p2jvh04o9uolg"'Poll until status becomes exported. Do not treat pending or processing as a completed result.
Processing response
{ "task_id": "d4g8o46p2jvh04o9uolg", "status": "processing", "total": 5000, "success": 2500, "failure": 0}Exported response
{ "task_id": "d4g8o46p2jvh04o9uolg", "status": "exported", "total": 5000, "success": 5000, "failure": 0, "result_url": "https://example-link-to-results.zip", "actual_amount": { "amount": "2.000000", "currency": "USD" }}Result Fields
| Field | Description | Example |
|---|---|---|
number | Input phone number from the submitted file. | +14155552671 |
activated | Whether the input was detected as active or registered. | yes |
Note: No profile columns appeared in the selected live sample; current profile-field availability remains unverified.
Result file handling
Download the file from result_url only after the task is exported. Preserve the returned column names when processing the file downstream.
Response fields
| Field | Description |
|---|---|
created_at | Timestamp when the task was created. |
updated_at | Timestamp of the latest task status update. |
task_id | Unique task identifier. |
status | pending, processing, exported, or failed. |
total | Total input values processed. |
success | Values processed successfully. |
failure | Values that failed processing. |
result_url | Download URL when the task is exported. |
actual_amount | Final settled amount, when available. |
estimated_amount | Estimated amount returned when the task is created. |
Status codes
| Status | Description |
|---|---|
200 | Request successful. |
202 | Task created successfully and estimated charge applied. |
400 | Invalid file, unsupported task type, or too few valid entries. |
401 | Missing or invalid API key. |
402 | Insufficient account balance. |
404 | Task not found. |
413 | Uploaded file is too large. |
500 | Internal server error; retry later. |
Operational notes
- The task is asynchronous; use the task ID for status polling.
- Check product-specific input limits before uploading.
- Failed rows are reported in the exported result and reflected in the task counters.
- The fields above are based on the current live sample and may change when the upstream export schema changes.