Comment on page
🧾
Tickets
This page provides a description of the available API routes for managing tickets.
Before you dive into the tickets API reference, it's a great idea to check out some articles that talk about different ticket states, the math used in tickets.
Additionally, if you plan to both read and edit tickets, don't miss the article on how tickets work with users' permissions.
get
http://{server-address}
/tickets
Get tickets
get
http://{server-address}
/tickets/{id}
Get ticket
post
http://{server-address}
/tickets
Create ticket
put
http://{server-address}
/tickets/{id}
Create or update ticket
patch
http://{server-address}
/tickets
Batch tickets update
delete
http://{server-address}
/tickets/{id}
Delete ticket
These API methods trigger specific actions on server. However, it's important to note that depending on the type of selected fiscal device or order endpoint device, some methods may not be supported. Furthermore, if an action is attempted on an inactive fiscal device or order endpoint device, it will lead to failure. In both scenarios, making API calls will generate an HTTP status code of 403.
post
http://{server-address}
/tickets/{id}/close
Close ticket
post
http://{server-address}
/tickets/{id}/print_preliminary_ticket
Print preliminary ticket
Last modified 3mo ago