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.

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.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world's most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.

The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.

Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]

Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.

API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.

Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.

To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.

To check how many API calls you have left for the current month, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.

To see the maximum number of API requests your plan allows, check the 'X-Zyla-RateLimit-Limit' response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.

The 'X-Zyla-RateLimit-Reset' header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.

Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.

You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

To give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it's important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.

When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.

Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.