Create orders in Gameball to award points for customer purchases.
apikey and secretkey headers.Unique identifier for the customer that you can reference across the customer's whole lifetime. Could be a database ID, random string, email or anything that uniquely identifies the customer.
"cust_123456789"
Unique identifier for the order on your system. This ID is case-sensitive.
"ORD12345"
Timestamp of when the order was placed.
"2024-10-16T08:13:29.290Z"
The actual amount paid by the customer for the order, accounting for any discounts or coupons applied. Unlike totalPrice, which reflects the original cost of the order, totalPaid represents the final amount the customer paid at checkout after all adjustments. This value is used for reward calculations in Gameball to determine the points or benefits earned from the order. Example: A customer purchases items worth $120, including taxes and shipping. If a $20 coupon is applied, the totalPaid becomes $100, reflecting the discounted amount the customer paid.
250.75
Customer's email address. Note: This is required if your account uses email-based channel merging.
"john.doe@example.com"
Customer's mobile number. Note: This is required if your account uses mobile-based channel merging.
"+1234567890"
The total cost of the order, including all item prices, shipping, taxes, and tips. This value does not account for any discounts or coupons applied and is not used for calculations in Gameball; it is solely saved as historical data linked to the order. Must be a positive value. Example: A customer purchases items worth $120, including taxes and shipping. Even if a $20 coupon is applied, the totalPrice remains $120 as it represents the original cost of the order before any discounts are applied.
300
Total discount applied to the order.
50
Total shipping cost associated with the order.
10
Total tax amount for the order.
15
An array containing details about each product in the order. If not provided, the calculation will only consider the total order values.
Redemption details for the order, including points held for redemption.
Key-value pairs containing any extra information about the order. The values must be of type string or number. Example: If your business offers gift options, you might want to include a personalized gift message with the order. Additionally, specific delivery instructions can be recorded to ensure smooth delivery and provide a personalized experience.
{ "paymentMethod": "CREDIT CARD" }This object contains details about the specific merchant involved in the transaction, which is particularly important for businesses managing multiple merchants or branches under the same Gameball account. This object can provide identifying information about both the main merchant and any associated branch where the transaction took place.
Indicates whether the customer is a guest (not signed up). Set this to true for guest users; otherwise, they are treated as registered customers by default.
false
The channel through which the order was placed helps track the origin of the order, particularly useful for systems that support multiple sales or communication channels. By identifying the channel, you can gain valuable insights into customer behavior, optimize channel-specific strategies, and ensure efficient handling of orders across platforms. Possible values: mobile - The order was placed through your mobile application. pos - The order was placed in person using a Point of Sale (POS) system, such as at a physical store or outlet. web - The order was placed through your website. callcenter - The order was placed over the phone by contacting a customer service representative or a call center.
mobile, pos, web, callcenter "pos"
Identifier for the shopping cart associated with the order.
"CART98765"
This object contains configurations related to the cashback settings.
Order tracked successfully
Unique identifier for the customer that you can reference across the customer's whole lifetime. Could be a database ID, random string, email or anything that uniquely identifies the customer.
"cust_123456789"
Points redeemed by the customer for this order, if applicable. Example: If a customer has accumulated 500 points and decides to redeem 100 points for a discount on their current order, the redeemedPoints value for that transaction will be 100. This helps track how many points were used in the transaction and what benefits were applied to the order based on the customer's redeemed points.
1000
The total number of points rewarded to the customer for making this order. These points are typically awarded based on your configured cashback rewards. Example: If the store rewards 10 points for every $1 spent, and a customer places an order worth $50, the rewardedPoints for this order would be 500 points.
101
Details about each product or service in the order, including points rewarded.