Commissions & Payout Overview
Understanding Commissions with Wildfire
Wildfire offers both a Commission API and Callbacks (Legacy) to ingest and call on affiliate commissions earned by users. Merchant commission reporting can vary, as such there are edge cases users need to account for.
Understanding Commission Data:
Key Response Fields | What | Tip |
|---|---|---|
CommissionID | CommissionID related to the sale | Ingest and use to reference as a commission moves through a lifecycle. |
SaleAmount | Total Amount of Sale | |
Amount | Total Amount of Commission (Base + Boost) | This is the Cashback rewards earned in total. Users handling UI will need to present the amount depending on the % they plan on passing to their users. |
Status | Status of commission/cashback to display to user | New commissions will come in as Pending. Wildfire recommends to never payout a user until a status is changed to "Ready" |
Tracking Code | User UUID passed during Authentication. | Reference returned UUID, to UUID's attached to user records. This is passed to us during authentication or in link creation. Ensures you map attribution correctly. |
{
"Commissions": [
{
**"CommissionID": 1234569625,
"ApplicationID": 0,
**"MerchantID": 1234569625,
"DeviceID": 0,
"DeviceXID": "0189ABEF",
**"SaleAmount": {
"Amount": "10.49",
"Currency": "BRL"
},
"Amounts": [
{
**"Amount": "0",
"Currency": "USD",
"SplitPart": "DEVICE",
"BaseCommissionAmount": "0",
"BoostedCommissionAmount": "0"
}
],
** "Status": "READY",
** "TrackingCode": "012345-6780a-bcdef0-50527",
** "EventDate": "2026-06-15T13:56:03Z",
"LockingDate": "2026-06-15T13:56:03Z",
"CreatedDate": "2026-06-15T13:56:03.618187Z",
"ModifiedDate": "2026-06-15T14:01:03.618187Z",
"MerchantOrderID": "1234513110",
"MerchantSKU": "C62-2770-006-04",
"CouponCodes": "",
"ShoppingTripCode": "stc-79066"
},Best Practices
- Utilize Modified Date Filters: Instead of paging backward through historical data until a match is found, your system should use the start_modified_date and end_modified_date query parameters
- Using the modified_date of the last record, you can pass this exact time as the start_modified_date in your next request. This ensures the API exclusively returns records that have been created or altered since your last pull, eliminating the need to page backward and significantly reducing your overall request volume
- Always apply a value for the end_modified_date; We recommend setting end_modified_date to the top of the current hour.
- Maximize Pagination Limits: To further reduce the number of API calls your job requires, ensure you are maximizing the payload size for each request.
- You can fetch up to 2,000 records per call by setting the limit=2000 parameter
- If the number of modified records in your requested date range exceeds 2,000, you can retrieve the complete data set by using the NextCursor value provided in the response to iterate through subsequent pages