To get started with CRIF API, you need to sign up on CRIF Developer, sign in and get your Client Id and Client Secret, and then get an Access Token. All CRIF APIs require an Access Token to execute, 
and the authentication mechanism to obtain an Access Token is based on OAuth 2.0 (RFC 6749).

Running all CRIF APIs requires an access token; the authentication mechanism to obtain an access token is based on OAuth 2.0 (RFC 6749). Visit our Get Started page, for details.

To access APIs available for testing, you should start by visiting our Get Started page. There, you will find all the necessary information to begin. Firstly, you will need to create an account with us, which will give you access to our API library containing all the APIs available for testing. Once you have created an account, you can then request access to the APIs that interest you by filling out a request form. This form will ask for information such as your name, email address, and the type of API you are interested in. Once you have submitted the form, our team will review your request and grant you access if it is approved. After being granted access, you will be able to start testing the APIs. You can explore the different features and capabilities of the APIs using our API library and learn more about how to use them by reading our documentation. If you encounter any issues or have any questions about getting started, our team is here to help. You can get in touch with us via email or chat and we will be happy to assist you. Check out our Get Started page for more information and to begin your testing today.

To request production access to our APIs, you must follow the steps outlined in the API specifications. To get started, create an account on the Developer Portal and access the API Marketplace to view the API specifications. The specifications will provide detailed instructions on how to request production access. Depending on the API, you may need to provide additional information such as your company name, contact details, and a description of how you plan to use the API. Once you have submitted your request, our team will review it and notify you of the outcome. If your request is approved, you will be granted production access to the API. Our API specifications provide all the information you need to request production access, so be sure to read them carefully and follow the steps outlined to ensure your request is processed efficiently.

The main function is test the integration of CRIF services. 

The Enviromnents Configurations are UAT Environment and PRODUCTION Environment.

To register, use the Register page and follow the wizard, filling in all required information. Note that a valid email address is required to complete registration. Once registered, you can sign in and get your Client Id and Client Secret from the User page. For Authorization Code grant type, you will need to provide your redirect url. The Client Id and Client Secret are valid for UAT environment only; for PRODUCTION environment, please contact the Crif Support Team via the Support page. Depending on the products, you may need to contact CRIF to obtain additional permission via the Support page.

CRIF APIs support the following OAuth 2.0 grant types: Client Credentials, Resource Owner Password Credentials, Authorization Code + PKCE. Please refer to the specific API documentation for details. The Access Token has a limited time validity of 3600 seconds (1 hour). After this period, a new Access Token must be obtained. Refresh Token grant type can be used to obtain a new Access Token. Please refer to the specific documentation for details.

If your CRIF Developer account has been disabled, the recommended action is to contact the CRIF support team directly to identify the reason for the account deactivation and request reactivation.You can find the contact details for the CRIF Developer Portal support team by visiting Support page. You may also be able to locate the contact information within your account dashboard or the documentation provided for the CRIF Developer API. Keep in mind that the process for reactivating a disabled account can differ depending on the cause of deactivation, so it's important to seek assistance from CRIF support directly.

To delete your account, please send a deletion request email to our support team. In your email, please include your account details and the reason for the account deletion. Our team will then process your request and confirm the deletion of your account. Please note that this action is irreversible and will permanently delete all of your data associated with the account. If you have any concerns or questions about deleting your account, please do not hesitate to contact our support team for further assistance.

A Client SDK is a software library that facilitates interaction with an API by a client software. It provides a high-level interface for sending requests and receiving responses from the API, abstracting the low-level details of the network protocol.

A Client SDK generated by Open API Generator automates the writing of code for API interaction, reduces errors, and improves code maintenance.

Open API Generator supports the generation of Client SDKs in various programming languages, including Java (v. 17), Python, C#(v. 11) and for various framework including Asp Net Core and Spring.

To use a Client SDK, you need to generate it through the Developer Portal, add it to your project, and use it to send requests to the API and handle responses.

Documentation and code examples for a Client SDK are available online on the Developer Portal Documentation Apis Page.

Advantages include faster development, reduced errors, better maintenance, and improved code readability.

Limitations include lack of flexibility and difficulty in customizing generated code to meet specific needs.

Yes, you can manually write code or use third-party Client SDKs.

The produced code is supplied to facilitate the procedure; but, you must adjust or fix it to meet your individual requirements, and we cannot assist you with this.