Transaction

These endpoints handle ticket transaction.

🗃Redirections

8 elemek

📄️Start transaction

After ticket calling, the clerk should start transaction on ticket service(s). To start a transaction on the ticket, call this endpoint with the following parameters:

📄️Add ticket comment

This endpoint adds a new comment to the ticket. The comments appear in the Monitoring and Statistics modules.

📄️Save customer data

This endpoint saves customer data for the ticket. The customer data object can contain fields from data1 to data10.

📄️Stop voice recording

This endpoint stops the ongoing voice recording. Use it, if the customer disallows making a record.

📄️Add new task

This endpoint adds a new service (task) to the ticket. To get a list of available services, use the List for new task endpoint.

📄️List for new task

This endpoint lists all available service keys for Add new task endpoint.

📄️Stop transaction

This endpoint stops a transaction on the ticket. The next step depends on the status value in the response.

📄️Start afterwork

After transaction, the clerk can start afterwork about the ticket. Call this endpoint with the following parameters:

📄️Stop afterwork

This endpoint stops the afterwork of the ticket. The next step depends on the status value in the response.

📄️Abort ticket

This endpoint aborts the ticket flow. It can be useful, if the ticket has multiple services but the clerk should abort the transaction flow and skip the further services.

📄️Missing ticket

This endpoint marks the ticket as missing. Use it, if the customer doesn't appear at the counter at calling.

📄️Restore missing ticket

This endpoint restores a missing ticket to callable ticket.