Create Transaction Event

The Create Transaction Event function allows the Device to report the product
the user purchased to the Tiliter Recognition API.
This is used to close the loop on the transaction and record when the Device
was used to follow through and purchase a product.
This also eliminates irrelevant data from reports that may result from
incomplete transactions.
Every recognition requires a transaction report; if no transaction occurs,
that can also be reported.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
uuid
required
Body Params
string
enum
required

Represents the various states and outcomes of a transaction. These states encapsulate all steps and outcomes, including successful completion, cancellation, and instances of loss. The enumeration includes intermediate states, like when a transaction is incomplete or a label is printed but the purchase is not yet concluded. These states are useful for tracking transactions in in-store scales or non-POS devices. Loss tracking states mark instances of theft or loss, and indicate whether action has been taken or just acknowledged. Finally, final stages of a transaction are included, such as the successful completion of a purchase or the cancellation. These states conclude a transaction from a POS device view.

Allowed:
date-time
required

The date and time at which the transaction event occurred

string
meta_data
object
Responses

429

Request Throttled - reduce request rate and retry

Language
Credentials
Header
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json