Postman & Interactive Documentation
Getting Started with the Prioticket API
Last updated
Was this helpful?
Distributor API
Getting Started with the Prioticket API
Last updated
Was this helpful?
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.
For the latest version of our API definition, please visit: ()
This definition gives you a complete, machine-readable blueprint of our entire API, including:
Endpoints
Request/response schemas
Parameter details
Authentication requirements
Prefer to work with Postman? No problem!
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.
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.
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.
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.
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.
