/integrations/orders endpoint, which every other earning and redemption flow builds on.
Submit an Order
After payment is confirmed, send the order to Gameball:This is the basic earn flow with no redemption. To let customers spend points on this order, see Redeem Points at Checkout, which adds a hold step before this same call.
Request Fields
string
required
Unique identifier for the customer. See Choosing Your Customer ID.
string
required
A unique transaction ID from your POS. Must be unique per store environment, duplicates are rejected.
string
required
The time the order occurred, in ISO 8601 format.
number
required
Amount paid by the customer after discounts and redemptions.
number
required
Full value of the order before any discounts.
number
Tax portion of the order. Include if it affects point calculation.
number
Shipping portion of the order, if applicable.
Response Fields
number
Points awarded for this order. Display this to the customer to show what they earned.
number
Points earned based on the transaction value and your earning rules.
string
Order processing status, for example
completed.Behind the scenes, Gameball evaluates your earning rules against the transaction value, issues points accordingly, logs the order in the customer’s purchase history, and may trigger campaign or tier logic based on cumulative spend.
Automatic customer creation: If the
customerId doesn’t exist yet, Gameball creates the profile automatically when you track the order, no separate create call required.Tips & Gotchas
- Submit final prices with tax and shipping if they affect point logic.
- Use ISO 8601 timestamps for
orderDate. - Never reuse an
orderId, duplicates are rejected. - Track the order after payment is confirmed but before closing the POS session.