How do I query a CPF against the Federal Revenue via API?

You send an HTTP GET request to the CPF.CNPJ API endpoint with the CPF and your authentication token in the header. The API queries the official Federal Revenue database and returns, in JSON, the holder name, the registration status and, where permitted, the date of birth. There is no captcha and no dependency on the government website.

Is the CPF lookup in real time?

Yes. The lookup hits the official source at call time (D+0) and returns the current registration status of the CPF, with no stale cache. The average response is between 0.4 and 2 seconds.

What data does the CPF API return?

The API returns the holder full name and the registration status (Regular, Pending Regularization, Suspended, Cancelled, Void or Deceased Holder). When the contracted package and usage rules allow it, it also returns the date of birth associated with the CPF.

Is it legal and LGPD-compliant to query a CPF?

Yes, provided there is a legal basis and a legitimate purpose, such as fraud prevention, regulatory compliance or contract execution. The lookup uses the official source and CPF.CNPJ operates with security and privacy certifications (ISO/IEC 27001 and 27701). It is up to the customer to ensure the legal basis for processing required by the LGPD.

How much does the CPF lookup API cost?

Pricing is per query and varies with the contracted volume, starting at R$ 0.13 per query on higher-volume packages. You create the account for free, receive trial credits and check the current plans on the pricing page.

//CPF API

CPF Lookup API — Brazilian Federal Revenue

At CPF.CNPJ, we simplify and streamline access to essential information about individuals and companies.

Why query the CPF directly against the Federal Revenue

The CPF is the official identifier for individuals in Brazil, but the number alone proves nothing: digits that pass the check algorithm do not mean the CPF exists, is regular or belongs to the person provided. Without querying the Federal Revenue database, companies accept sign-ups with non-existent, third-party or irregular CPFs, opening the door to identity fraud, document fraud and gaps in onboarding fraud-prevention duties.

The lookup returns the CPF registration status, which can be Regular, Pending Regularization, Suspended, Cancelled, Void or flag a Deceased Holder. Each status has a practical effect: a Suspended or Pending CPF blocks invoicing and contracting; a Cancelled CPF or one belonging to a deceased holder used in a new sign-up is a strong fraud signal. Validating this status before approving the customer is what separates a safe onboarding from a fraud and compliance liability.

Doing this manually does not scale. Teams processing thousands of sign-ups a day cannot check CPF by CPF on the Federal Revenue website, which still requires a captcha and offers no programmatic response. A CPF lookup API removes the bottleneck: it embeds verification directly into the sign-up flow, returns the registration status in real time and lets you automate the decision to approve, reject or route the case to human review.

What the CPF Lookup API delivers

1. Official name and registration status

The API returns the holder full name and the CPF registration status exactly as recorded in the Federal Revenue database: Regular, Pending Regularization, Suspended, Cancelled, Void or Deceased Holder. With this data you cross-check the name declared by the customer against the official name and automatically block CPFs that are not regular.

2. Date of birth, where permitted

When the contracted package and usage rules allow it, the response includes the date of birth associated with the CPF. This enables additional checks such as age verification (18+) and cross-matching the declared date against the official one, reinforcing prevention of synthetic identity fraud.

3. Real-time response (D+0)

The lookup hits the official source and responds in real time, with no stale cache. The registration status reflected is the one at the moment of the query (D+0), ensuring onboarding decisions use the current state of the CPF rather than an old snapshot.

4. REST/JSON with token authentication

The integration is a REST API returning JSON, authenticated by a token sent in the request header. No captcha, no dependency on a government screen: a single HTTP call from your backend returns the structured data for your flow to handle.

How to integrate the CPF Lookup

The lookup is an HTTP GET call authenticated with a Bearer token. Send the CPF as a parameter and receive the registration status in JSON. Example with cURL:

# CPF lookup against the Federal Revenue via API
curl -X GET "https://api.cpfcnpj.com.br/YOUR_TOKEN/9/12345678909" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Accept: application/json"

# Response (JSON)
{
  "status": 1,
  "cpf": "123.456.789-09",
  "nome": "JOSE DA SILVA",
  "situacao_cadastral": "REGULAR",
  "data_nascimento": "1990-05-14",
  "data_consulta": "2026-06-02T10:32:11Z"
}

Handle the situacao_cadastral field in your backend: approve only REGULAR CPFs, block CANCELLED, VOID and DECEASED HOLDER, and route PENDING or SUSPENDED to review. The full reference of endpoints, packages and return codes is at https://www.cpfcnpj.com.br/dev/.

What to expect from the CPF Lookup API

Low latency: Average response between 0.4 and 2 seconds per CPF lookup
99.9% uptime: Service availability to embed the lookup into your onboarding
Official Federal Revenue source: Registration status queried from the official base, no intermediary data
Nationwide coverage: Lookup of any CPF issued in Brazil, in real time (D+0)