# Postman & Interactive Documentation At Prioticket, we want to make integration as easy and developer-friendly as possible. That’s why our **API is fully documented using OpenAPI**, the world’s most widely adopted standard for API definitions. Whether you prefer to explore the API through **interactive documentation**, generate your own client libraries, or test calls directly in **Postman**, we’ve got you covered. *** ### Our OpenAPI Definition For the latest version of our API definition, please visit:\ [**Working with OpenAPI**](https://swagger.prioticket.com/definitions/Prio-Distributor-API/v38/distributor.json) **(**[**previous versions**](https://docs.prioticket.com/resources/api-specifications)**)** This definition gives you a complete, machine-readable blueprint of our entire API, including: * Endpoints * Request/response schemas * Parameter details * Authentication requirements *** ### Works Seamlessly with Postman Prefer to work with **Postman**? No problem! [![Run In Postman](https://run.pstmn.io/button.svg)](https://god.gw.postman.com/run-collection/5979375-7e7fcc90-6dd6-411f-ad82-38dd0c06f8c9?action=collection%2Ffork\&source=rip_markdown\&collection-url=entityId%3D5979375-7e7fcc90-6dd6-411f-ad82-38dd0c06f8c9%26entityType%3Dcollection%26workspaceId%3D3ba039ca-9116-4cce-bb71-9f5aeaf37fe5) *** ### Instant Client Libraries with OpenAPI Generator Because our definition is publicly available, you can use powerful open-source tools like **OpenAPI Generator** to **automatically generate client libraries** in your preferred programming language, from Python and JavaScript to PHP, Java, and many more. {% hint style="danger" %} **Important Note:** These libraries are auto-generated and should be considered experimental. While we cannot guarantee backward compatibility and do not provide support for these third-party tools, we *do* use these SDKs internally in our own product and highly recommend them as a starting point if you prefer working with SDKs. {% endhint %} *** ### Test and Explore Instantly with Interactive Documentation Want to experience our API **hands-on** without writing any code? Our documentation is **interactive**, meaning you can send actual API calls directly from your browser. *** ### Advanced Functionality Throughout the documentation, you’ll also find sections labeled **Advanced Functionality**. These features are intended for more **complex use cases** and **deep integrations**. Implementing advanced functionality is **optional** and not required for basic API connectivity. If you’re interested in exploring these advanced capabilities, simply reach out to your **Account Manager** for guidance and best practices. *** {% hint style="warning" %} ### Important Notes on Schema Reuse To keep things efficient, some schemas are reused across multiple endpoints, for both requests and responses. This means: * Some properties are **read-only** (included in responses but not in requests). * Other properties are **write-only** (sent in requests but not returned in responses). Since all responses use **JSON format**, the **order of fields may vary** and might also change over time. Rest assured, the actual content and structure remain compliant with the OpenAPI specification. {% endhint %} --- # 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://docs.prioticket.com/getting-started/postman-and-interactive-documentation.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.