The Kiflo REST API gives you programmatic control over your partner program data. It follows REST conventions with predictable, resource-oriented URLs, standard HTTP verbs, and JSON responses — so any HTTP client, backend language, or integration platform can talk to it without friction.
Base URL
All API requests go to:
For the interactive API reference with full endpoint documentation, request/response schemas, and live examples, visit https://docs-api.kiflo.com.
Authentication
Every request must include an API Access Token in the Authorization header:
Generate your token from Account Settings → Integration inside your Kiflo account. See the Authentication guide for step-by-step instructions, including how to revoke a token when it is no longer needed.
Your API Access Token is shown only once at generation time. Copy it immediately — Kiflo does not store it, and you will need to generate a new one if you lose it.
API vs. JS SDK — when to use each
Kiflo offers two integration surfaces. Choose based on where your code runs:
When you create a customer from your backend, use kiflo('getTrackingCode') in the browser to retrieve the referral cookie value, pass it to your server, and then include it in your API request so Kiflo can attribute the conversion to the correct partner. Full API reference
The complete reference — including all endpoints, parameters, and example responses — is available at https://docs-api.kiflo.com.
Use the interactive “Try it” panel in the API reference to test requests directly from your browser with your own Access Token.
