Skip to main content
The ClickFlare public API exposes the same objects you work with in the interface — campaigns, offers, landers, flows, traffic sources, affiliate networks, domains and integrations — so you can create and maintain them from your own code instead of clicking through the UI. It is the right tool when you are launching campaigns in bulk, syncing ClickFlare with an internal system, or building automation on top of your account. For everyday work, the interface is faster.

​
Base URL

Endpoints sit under /api, so a request for your campaigns goes to:

​
Authentication

Every request is authenticated with an API key sent in a header named api-key. There is no OAuth flow and no bearer token.
1

Create a key

In ClickFlare, go to Settings → API Keys and generate a key.
2

Send it with every request

Add it as the api-key header. A request without it returns 401 unauthorized.
An API key carries the same permissions as your account. Keep it out of client-side code, out of landing pages, and out of anything you share — anyone holding it can read and modify your campaigns.

​
What you can reach

The API covers 54 endpoints. The larger groups are the ones you would expect to automate: Smaller groups cover scripts, boards, columns, settings and the raw conversion uploader.

​
Full endpoint reference

The complete specification — every path, parameter, request body and response — lives on the developer portal:

ClickFlare Public API reference

Browse all 54 endpoints with their full request and response schemas.
The raw OpenAPI document is served at https://public-api.clickflare.io/api/swagger.json if you want to generate a client from it.

​
Before you automate

Build a working campaign through the interface before you script it. The API mirrors the same objects and the same required fields, and it is far easier to see what a valid offer or flow looks like when you can inspect one you already made.
Offers, landers, traffic sources and affiliate networks are shared across campaigns. Creating a new offer for every campaign fragments your reporting. Fetch the existing element and reference it instead.See Offers: What They Are and How Payout Works.
The API creates objects; it does not verify that your tracking works. A campaign created through the API still needs the click ID appended to the offer URL and a postback configured on the network side.See Tracking Conversions Using S2S Postback.

MCP server

Connect ClickFlare to an AI assistant and query your account in plain language.

Tracking URLs

The click and postback URLs your campaigns use, and where to find them.