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 possible steps and outcomes of a transaction, including successful completion, cancellation, and instances of loss. The enumeration includes intermediate states, such as when a transaction is incomplete or a label has been printed but not yet concluded in a purchase. These states are useful for tracking the transaction status in in-store scales or other non-POS devices. Loss tracking states are also included to mark cases of theft or loss, and whether action has been taken or acknowledged without any immediate action. Finally, states representing the final stages of a transaction are included, such as the successful completion of a purchase or the cancellation of a transaction. These final states represent the ultimate conclusion of a transaction from a POS device perspective.

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