The Affilibee API reference describes how your platform sends completed, attributed orders into Affilibee. It is intended for teams that already understand the integration flow and need the request contract, authentication requirements, and endpoint details in one place.
Use this section after you have reviewed API integration. That guide explains when to submit an order and how attribution should move through your platform. The API reference explains how to make the request correctly once that workflow is in place.
The current API reference is organized around three pieces:
Affilibee expects your platform to do three things before an API request is made. It should capture the affiliate slug when the customer arrives, persist that attribution to the order in your own system, and submit the order only once it reaches a valid state for commission tracking.
That means the API is not designed to manage storefront attribution or checkout state for you. It assumes those concerns are already handled upstream and that the submitted request represents an order your platform is ready to report.
The create order endpoint accepts JSON and expects monetary values in the smallest currency unit, such as cents for USD. If your platform operates in multiple currencies, convert the values before submission and make sure they match the currency registered for your merchant account.
It is also worth treating the API reference as a contract rather than an implementation guide. The reference tells you what to send. The decisions around timing, retries, and attribution persistence should still live in your own platform.
If you need the required token format, continue with Authentication. If you are ready for the request schema itself, continue with Create order.
We help teams run affiliate programs through API-first integrations that fit the platform they already use.
© 2025 Affilibee Handelsbolag (969802-2481)
