# Overview *** ### Definitions * **Bundle Key:** the key used to identify the bundle and it's activated services * **Access Token:** an authentication token used to access Valify's Service APIs * **Transaction ID:** a record of each attempt to use one of Valify's services * **Trials:** the limit by which the same token can be used to access a Service API. (3 trials by default) ### Authentication All Valify Service APIs are authenticated using OAuth 2.0 access tokens. Tokens are generated using our OAuth Token API and must be provided with each service request. Click [here](/documentation/apis/oauth-token.md) for details. ### Service APIs The Valify Service APIs are built using RESTful API standards and can be easily integrated within any system using an HTTP Client.\ Our APIs accept and returns data in JSON format (content-type: application/json). All API calls must be made over HTTPS, and must be authenticated using OAuth 2.0, as described in the Authentication section. A Service API response often includes a Transaction ID and the number of trials remaining for this service, indicating that a record of the attempt was created. For each service API, a sample Python code snippet and postman collection are provided. Click [here](/documentation/apis.md) for details. {% hint style="info" %} To generate OAuth access tokens and use Valify's service APIs, you need to be provided with API credentials. Please contact **** for more information. {% endhint %} {% hint style="warning" %} You should never share your API credentials with other parties. If this happens, please contact **** to disable them and generate a new set of credentials. {% endhint %} ### Valify API Collection To streamline your integration process, we've prepared a comprehensive Postman collection encompassing all our API endpoints. You can access and import it using the link below: [Access the Valify API Postman Collection](https://drive.google.com/file/d/1LhjRuYjPAyzufXl1VBKVKmnT7GR1M_eG/view?usp=sharing) ### Error Codes This section covers all the HTTP codes returned by the Service APIs, as well as custom error codes specified by Valify, their meanings and recommended actions. Click [here](broken://pages/-MPEhRiTjJh-QWD-KYF6) for details. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://valify.gitbook.io/documentation/introduction/master.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.