Free
R$0/mo
20 lookups included per month, renewed every cycle
- Extra lookup
- Blocked (402 error)
- Rate limit
- 5 req/s
- Full access
- REST API
- Lookup history
- WhatsApp and email support
CPF Lookup API
Look up and validate CPFs with official data and high accuracy
CPF lookup and registration data API sourced directly from Brazil’s Federal Revenue Service (Receita Federal), for fintechs, e-commerce and SaaS. Protect your business from fake sign-ups with a simple, scalable, low-cost integration.
Free plan, no credit card required.
- Age check
- Identity check
- Registration status
How each lookup is served
Most lookups are answered from our own database. The official source is only queried when the record is missing or older than 30 days.
- 1
Local validation
Format and check digits verified at the edge, without touching a database.
- 2
In-memory cache
Records looked up in the last 30 days come back from Redis in milliseconds.
- 3
Own database
If it is not in memory, we read our PostgreSQL store and warm the cache again.
- 4
Official source
Only then do we call the provider. If it is unstable, we answer 503 and charge nothing.
Wherever the data comes from, a lookup that finds a record costs exactly 1 credit.
Clear pricing.No surprises at the end of the month.
Pro
R$149/mo
Credits per month
- Cost per lookup
- R$0.149
- Extra lookup
- R$0.15
- Rate limit
- 50 req/s
- Full access
- REST API
- Lookup history
- WhatsApp and email support
Corporate
On request
From 10,000 lookups included
- Extra lookup
- Contracted
- Rate limit
- 200+ req/s
- Full access
- REST API
- Lookup history
- WhatsApp and email support
- Only 200 responses use a credit. Validation, authentication, rate-limit and availability errors are free.
- The allowance lasts 30 days and does not roll over, free plan included (20 lookups per cycle).
- Email and webhook alerts when usage reaches 80% and 95% of your quota.
Integrate in any language
One HTTP request and an API key. See how to look up a CPF in your language and what the API returns.
cURL GET /v1/cpf/52998224725
1curl -X GET \2 'https://api.brazid.com/v1/cpf/52998224725' \3 -H 'x-api-key: YOUR_API_KEY'
1const res = await fetch(2 'https://api.brazid.com/v1/cpf/52998224725',3 {4 headers: { 'x-api-key': 'YOUR_API_KEY' },5 },6);7 8const { data } = await res.json();9console.log(data.name);
1import requests2 3res = requests.get(4 'https://api.brazid.com/v1/cpf/52998224725',5 headers={'x-api-key': 'YOUR_API_KEY'},6)7 8print(res.json()['data']['name'])
1<?php2$ch = curl_init('https://api.brazid.com/v1/cpf/52998224725');3curl_setopt_array($ch, [4 CURLOPT_RETURNTRANSFER => true,5 CURLOPT_HTTPHEADER => ['x-api-key: YOUR_API_KEY'],6]);7 8$data = json_decode(curl_exec($ch), true);9echo $data['data']['name'];
1var request = HttpRequest.newBuilder()2 .uri(URI.create("https://api.brazid.com/v1/cpf/52998224725"))3 .header("x-api-key", "YOUR_API_KEY")4 .GET()5 .build();6 7var response = HttpClient.newHttpClient()8 .send(request, HttpResponse.BodyHandlers.ofString());9 10System.out.println(response.body());
1req, _ := http.NewRequest("GET", "https://api.brazid.com/v1/cpf/52998224725", nil)2req.Header.Set("x-api-key", "YOUR_API_KEY")3 4res, _ := http.DefaultClient.Do(req)5defer res.Body.Close()6 7body, _ := io.ReadAll(res.Body)8fmt.Println(string(body))
1require 'net/http'2require 'json'3 4uri = URI('https://api.brazid.com/v1/cpf/52998224725')5res = Net::HTTP.get(uri, { 'x-api-key' => 'YOUR_API_KEY' })6 7puts JSON.parse(res)['data']['name']
1using var client = new HttpClient();2client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");3 4var body = await client.GetStringAsync("https://api.brazid.com/v1/cpf/52998224725");5Console.WriteLine(body);
Response
1{2 "success": true,3 "data": {4 "cpf": "52998224725",5 "name": "MARIA SOUZA LIMA",6 "birthdate": "26/11/1982",7 "day": 26,8 "month": 11,9 "year": 1982,10 "gender": "M",11 "deceased": false12 }13}
1{2 "error": "CPF not found"3}
Lookup completed successfully.
CPF not found in the official database.
Frequently asked questions
Where does the data come from?
From the official CPF registry through an accredited provider. We keep results for up to 30 days to answer repeated lookups faster.
What counts as a billed lookup?
Only 200 responses, meaning the CPF was found. Invalid format (400), wrong check digit (422), not found (404), rate limit (429) or unavailability (503) never use a credit.
What happens when my quota runs out?
On the free plan the API answers 402 (Payment Required) once the cycle’s 20 lookups are used, until it renews. On Pro and Corporate plans it keeps answering and each extra lookup is billed at the end of the cycle at your plan’s rate.
How do you handle personal data?
All traffic uses TLS, API keys are stored only as SHA-256 hashes and CPFs are masked (123.***.***-00) in every log and report.
Can I cancel at any time?
Yes. When you cancel, your account returns to the free plan at the end of the paid cycle.
Run your first lookup in a few minutes.
Create an account, confirm your email and generate your API key in the dashboard.