> For the complete documentation index, see [llms.txt](https://developers.tiqets.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.tiqets.dev/basics/api-keys.md). # API Keys A valid API key is required to authenticate yourself while performing calls to the Tiqets Distributor API.\ Depending on the access level associated with your API key you'll be able to access more endpoints of the Distributor API. ## API Key Management To create and manage your API keys (also known as API tokens) you can login to your [partner portal](https://www.tiqets.com/affiliate/) and navigate to the ***API tokens*** section under the ***Tools*** menu. There you will find a list of your existing tokens and the option to create new tokens if needed. Keys generated by you will initially only give you access to our catalog (products) and availability endpoints. If you need access to more advanced endpoints please contact [affiliates@tiqets.com](mailto:undefined) so they can review your request and provide you with access. If you have any issues accessing the ***portal or*** ***API tokens*** section or generating a new token please contact your Tiqets account manager or . ## Booking API Acceptance Process To gain access to our API Production Environment including the ability to place orders, a successful demo of your integration with our Test environment is required. The following actions need to be performed via the Booking API against the [**test environment**](/basics/environments-and-testing.md)**.** Please record the screen when performing these actions and share the video file(s) with our API support team. * Create and confirm an order for a product with a timeslot, e.g. product 1006518 * Create at least two orders for different languages for product 1006523, of which at least one order must include the addon variant * Create at least two orders, one for a weekday and one for a weekend, for product 1010393 * Create at least one order for a product that requires additional checkout fields, e.g. product 975244 * Cancel an order Please also include a short description of your product and availability/pricing caching logic. This can be done in writing and does not require a video recording. Additionally, it is recommended to build these features (which are not mandatory to pass the API demo): * Implement logic to retrieve and cache availability and pricing information for at least three months for all products of interest * Implement logic to handle unavailable products and de-list products that are long-term unavailable --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://developers.tiqets.dev/basics/api-keys.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.