Busca de informações completas utilizando CPF, Nome completo, Data de Nascimento, Sexo, Óbito, Nome Da Mãe e Pai entre outros
{"success":true,"response_time_ms":174.479999999999989768184605054557323455810546875,"consulted_cpf":"60248327291","data":{"cpf":"602.483.272-91","cpf_sem_pontuacao":"60248327291","cpf_truncado":"602.xxx.xxx-91","nome":"EDILANIA ANTONIA DA COSTA","nascimento":"04/10/1977","sexo":"F","nome_mae":"NEUSA CARVALHO DA COSTA","nome_pai":null,"obito":false,"data_obito":null}}
curl --location --request GET 'https://zylalabs.com/api/10903/api+busca+cpf/20617/cpf?cpf=60248327291' --header 'Authorization: Bearer YOUR_API_KEY'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime.
The GET cpf endpoint returns detailed personal information associated with a CPF, including the individual's name, date of birth, gender, parents' names, and whether the individual is deceased.
Key fields in the response include "cpf," "nome," "nascimento," "sexo," "nome_mae," "nome_pai," "obito," and "data_obito," providing comprehensive identity details.
The response data is structured in JSON format, with a top-level object indicating success and response time, followed by a "data" object containing the individual's information.
The GET cpf endpoint provides information such as full name, date of birth, gender, parents' names, and death status, allowing for thorough identity verification.
Users can customize their requests by specifying the CPF number in the endpoint URL, allowing for targeted searches for specific individuals.
"obito" indicates if the individual is deceased (true/false), while "data_obito" provides the date of death if applicable. Other fields offer personal identification details.
Typical use cases include identity verification for financial services, background checks, and genealogical research, leveraging the comprehensive personal data provided.
Data accuracy is maintained through regular updates from official registries and databases, ensuring that the information retrieved is reliable and up-to-date.
The GET cpf endpoint retrieves personal information linked to a CPF, including full name, date of birth, gender, parents' names, and death status, providing a comprehensive profile for identity verification.
No, the GET cpf endpoint is designed to handle one CPF query at a time. Users must make separate requests for each CPF to retrieve individual data.
The "cpf_truncado" field provides a partially masked version of the CPF for privacy, displaying only the last three digits, which helps protect sensitive information while still confirming identity.
The "obito" field indicates whether the individual is deceased (true) or alive (false). This information is crucial for legal and administrative purposes, such as estate management.
If the response data is incomplete or missing, users should verify the CPF provided for accuracy. If issues persist, consider checking the source of the CPF or contacting support for assistance.
Yes, the GET cpf endpoint only accepts valid CPF numbers. Invalid or incorrectly formatted CPFs will result in an error response, ensuring data integrity.
The "response_time_ms" field indicates the time taken to process the request. Users can use this metric to assess API performance and optimize their applications for better user experience.
The API sources data from official registries and databases, ensuring high accuracy. Regular audits and updates are conducted to maintain data quality and reliability.
The "cpf_sem_pontuacao" field provides the CPF number without any formatting, making it suitable for database storage or processing where punctuation is not needed. This ensures consistency in data handling.
If an error response is received, users should check the CPF format for accuracy and ensure it is valid. Common errors include incorrect formatting or non-existent CPF numbers. If issues persist, consult the API documentation or support.
The "success" field indicates whether the request was processed successfully. Users can use this information to implement error handling in their applications, ensuring they only proceed with valid data when "success" is true.
Applications in finance, legal services, and genealogy can benefit from this API. It aids in identity verification, background checks, and family history research, leveraging the comprehensive personal data available.
The API employs data masking techniques, such as the "cpf_truncado" field, which displays only part of the CPF number. This protects sensitive information while still allowing for identity verification.
The "response_time_ms" field in the response indicates the time taken to process the request, typically in milliseconds. Users can use this metric to gauge API performance and optimize their applications accordingly.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
Service Level:
100%
Response Time:
2,363ms
Service Level:
100%
Response Time:
1,748ms
Service Level:
100%
Response Time:
45ms
Service Level:
100%
Response Time:
1,753ms
Service Level:
100%
Response Time:
241ms
Service Level:
100%
Response Time:
205ms
Service Level:
100%
Response Time:
42ms
Service Level:
100%
Response Time:
1,098ms
Service Level:
100%
Response Time:
9,458ms
Service Level:
100%
Response Time:
950ms
Service Level:
100%
Response Time:
16ms
Service Level:
100%
Response Time:
18ms
Service Level:
100%
Response Time:
16,893ms
Service Level:
100%
Response Time:
8,966ms
Service Level:
100%
Response Time:
16ms
Service Level:
100%
Response Time:
14,691ms
Service Level:
100%
Response Time:
16ms
Service Level:
100%
Response Time:
6,749ms
Service Level:
100%
Response Time:
16ms
Service Level:
100%
Response Time:
11,049ms