Batch CPF lookup: up to 1,000 CPFs per request
Send the whole list in one call and follow the progress or get a webhook when it finishes. Ideal to clean up databases and check registrations in bulk.
Only the CPFs found spend credits. Free sandbox.
Batch progress
- Total
- 1,000 CPFs
- Processed
- 1,000
- Found
- 968
- Not found
- 32
Built for volume
The same official CPF lookup, without having to manage thousands of calls.
- Up to 1,000 CPFs per request
- Each item carries the CPF and the birth date. CPFs repeated in the list count once.
- Asynchronous processing
- The API answers 202 right away with a batch_id and processes the list in the background, without holding your application.
- Webhook notification
- Register a webhook and receive the batch.completed event when it ends, with counters and dates only, no personal data.
- Paginated results
- Each item comes back with a status (found, not found, invalid or error) and, when found, the CPF data.
- Retry only what failed
- Invalid items, not found items and provider failures are not charged, and you resubmit only those.
- Same rules as the single lookup
- Same balance, same plan rate limit and the same response per item.
How it works
- 1
You send the list
The API validates each item and reserves the processing. The 202 response carries the batch_id.
- 2
We resolve it in the background
Whatever was looked up recently is resolved right away. The rest goes to the official source.
- 3
You follow along and read the results
Check the progress until the status is completed, or wait for the webhook. Results stay available for 24 hours.
Send the list, follow up later
One POST with the list of CPFs and birth dates returns the batch_id to follow.
Endpoint documentationcURL POST /v1/cpf/batch
Response
Batch accepted. Follow it by its batch_id.
Not enough balance to cover the batch: nothing was processed.
What it costs
1 credit per CPF found
Invalid items, not found items and provider failures are not charged. Your balance must cover the whole batch unless your plan allows overage.
Free sandbox
In the sandbox the batch runs with test CPFs, including a mixed example batch, without debiting credits.
Same balance as the other lookups
Plan credits work for CPF, CNPJ, batches and the dossier. The batch respects the account rate limit.
Where to use it
Database cleanup
Check thousands of records at once and find suspended or canceled CPFs, or data that does not match.
System migration
Validate the whole registry before importing customers into a new platform.
Collections and recovery
Refresh the registration status of an entire portfolio in a single run.
Frequently asked questions
What is the maximum batch size?
Up to 1,000 items per request. For bigger lists, send several batches in sequence; each account has a cap on items waiting to be processed to protect the queue.
How long does a batch take?
It depends on the size and on how many CPFs were looked up recently. Follow the batch status or receive the batch.completed webhook when it ends.
How long do the results stay available?
For 24 hours after submission. After that the batch is gone and you have to look the CPFs up again.
Who pays for CPFs that were not found?
Nobody: only the CPFs found spend credits. Invalid items, not found items and provider failures are not charged.
What if my balance runs out mid-batch?
The API checks the balance before starting and answers 402 if it does not cover the batch (unless your plan allows overage). A batch never starts halfway.
More BrazID products
They all share the same API key and the same credit balance.
Check thousands of CPFs at once
Create your account, test the batch in the sandbox and process your base with the production key.
Only the CPFs found spend credits. Free sandbox.