The ClickFlare REST API,for bulk launches and automation

The ClickFlare REST API lets your own code do what you repeat in the interface: launch campaigns, offers and landers in bulk, keep ClickFlare in step with your systems and pull report data anywhere. It covers 54 endpoints, and every request uses your API key.

API
REST API
ClickFlare public API

REST API integration at a glance

How it connects
Secure API requests authenticated with your API key
What syncs
Campaigns, offers, landers, flows, reports and logs
How fresh the data is
On demand, per request
What you can optimize
Report data by any breakdown, in your own tools
Works with
Any language or tool that can send HTTPS requests
Good to know
A key has your account's access. Keep it on your server.
Public API
54 endpoints
Bulk launches

Script the work you repeat in the interface

Launch in bulk

Create, clone, archive and unarchive campaigns, offers and landers from code when you launch dozens at once.

Sync with your systems

Keep ClickFlare in step with internal tools by managing traffic sources, affiliate networks, domains and integrations through the API.

Reports anywhere

Pull report data into a BI tool, a warehouse or your own scripts, grouped the way you need it.
How it works

From ad click to profit per campaignattributed revenueattributed salesa matched conversionautomated actionyour dashboardsclosed revenue

01
Your ad
Visitor clicks
Ad on REST API
02
ClickFlare
Click recorded
Every click gets its own ID
03
Your offer
Conversion
Lead, sale or custom event
04
ClickFlare
Sent back to REST API
Through the Conversion API or postback
05
Cost API
Spend pulled in
REST API cost matched to each campaign
01
Your ad
REST API click
Placement, device and country come along
02
ClickFlare
Click recorded
Zone, site and device data stored
03
Offer or lander
Visitor converts
On your page or the offer
04
ClickFlare
Conversion logged
With payout and event type
05
Postback
Reported to REST API
So its optimization sees the result
01
Your ad
Visitor clicks
Any traffic source
02
ClickFlare
Click recorded
Every click gets its own ID
03
Your article
Keyword block
Click ID passed to the feed
04
Results page
Paid click
Conversion fired to ClickFlare
05
REST API API
Revenue matched
Pulled on a schedule and reconciled
01
Your ad
Visitor clicks
Any traffic source
02
ClickFlare
Click recorded
The click follows the visitor to the offer
03
REST API
Offer or call
The network tracks the action
04
REST API
Conversion
Lead, sale, call or rebill
05
Postback
Payout in ClickFlare
Matched to the original click
01
Your ad
Visitor clicks
Any traffic source
02
ClickFlare
Click recorded
Every click gets its own ID
03
REST API
Store or funnel
Click ID kept through checkout
04
Events
View, cart, checkout
Each step tracked
05
ClickFlare
Purchase recorded
Order value matched to the ad
01
Your ad
Visitor clicks
Form, call or landing page
02
ClickFlare
Click recorded
Every click gets its own ID
03
REST API
Lead or call stored
The ad stays linked to the lead
04
REST API
Qualified or closed
Workflow or call rule fires
05
ClickFlare
Revenue recorded
Tied to the ad that drove it
01
ClickFlare
Event happens
Click, conversion or custom event
02
Webhook or API
Data goes out
Or comes back in
03
REST API
Your workflow
Rules, apps or an AI assistant
04
REST API
Action
Alert, update, pause or scale
05
ClickFlare
Back in reports
Changes show in your data
01
ClickFlare
Report data
Campaigns, sources, offers
02
ClickFlare API
Your numbers go out
Secured with your API key
03
Your setup
Scheduled refresh
A sheet, script or connector
04
REST API
Data lands
Tables refreshed on schedule
05
REST API
Dashboards
Blended with your other data
Public API

How the ClickFlare API is organized

The API mirrors the objects in the interface with the same required fields, so a valid offer in ClickFlare is a valid offer in the API. Every request carries your API key.
  • Same objects and fields as the interface
  • Full reference on the developer portal
  • Requests without a valid key are refused
Today, one campaign
example
Spend pulled from REST API
cost
$412.30
Conversions recorded
today
38
Sent back to REST API
per event
38/38
Profit
campaign
$227.70
Example numbers. Cost and conversions sit in the same report row.
ROI per placement
example
Placement A · mobile
cost
$38.20
Placement A
revenue
$71.40
Placement A
ROI
+87%
Placement B · desktop
ROI
−42%
Example numbers. Keep the placements that pay and cut the ones that lose money.
Revenue for one click
example
Paid click
day 0
$0.00
First revenue pull
+1h
$0.41
Scheduled updates
next days
$0.58
Final pull
last sync
$0.62
Example amounts. Sync timing for REST API is in the facts above.
Events for one click
example
Lead
day 0
$0.00
Sale
day 0
+$40.00
Upsell
day 1
+$15.00
Refund
day 9
−$15.00
Example events. Each one arrives by postback and is matched to the click.
One visitor's path
example
Product view
step 1
—
Add to cart
step 2
—
Checkout
step 3
—
Purchase
step 4
$68.00
Example order. Each event is tied to the ad that brought the visitor.
One lead, followed to revenue
example
Lead created
day 0
$0.00
Qualified
day 2
+$25.00
Deal closed
day 14
+$480.00
Renewal
day 45
+$120.00
Example values. Each stage can be its own event type in ClickFlare.
A scheduled report refresh
example
Campaigns
in the report
1,240 rows
Cost, revenue, profit
per campaign
included
Refresh
your schedule
done
Dashboards fed
REST API
3
Example numbers. You choose the breakdowns, date range and schedule.
One event, end to end
example
Conversion recorded
event
sent
Event delivered
REST API
received
Workflow ran
REST API
done
Team notified
your apps
done
Example run. What happens after the event is up to your workflow.
54
API endpoints
2.3B
Events tracked
Setup

Connected in three steps

You need a ClickFlare account, an API key and a script or tool that can send HTTPS requests.
  1. Generate an API key Create a key in ClickFlare. Keep it out of client-side code, landing pages and anything you share.
  2. Send it with every request Your key goes with each request. There is no separate sign-in flow, and requests without it are refused.
  3. Start from a working example Build one campaign by hand first, then fetch it through the API to see what a valid object looks like before you script more.
app.clickflare.com/integrations
API
REST API
Public API
Connected
REST API account connected
Signed in from ClickFlare
Cost syncing
Spend matched to campaigns
Conversions sent back
Your chosen events
REST API template selected
Macros pre-filled
Tracking URL in REST API
Click ID captured
Conversions reported
Payout included where supported
REST API connected
Credentials saved in ClickFlare
Conversion event set
Click ID passed to the feed
Revenue syncing
On the feed's schedule
REST API added
Offer URL carries the click ID
Postback set in REST API
Payout and event included
Conversions arriving
Matched to the click
REST API connected
Click ID kept to checkout
Events mapped
View, cart, checkout, purchase
Purchases tracked
Order value in reports
Click ID stored in REST API
Hidden field or call data
Workflow or rule set
Fires on the stage you choose
Conversions arriving
With payout and event type
API key created
Settings, then Security
Report pull scheduled
Dimensions and date range set
REST API dashboards live
Refreshed on schedule
Connection set up
Webhook, API key or MCP
Events chosen
Only what the workflow needs
Workflow running
Tested end to end
Ready to track
The API creates objects but doesn't check tracking. Campaigns made through it still need the click ID passed to the offer and a postback on the network side.
ClickFlare API overview
Open the guide
In your reports

What you see once it's connected

  • Report data by any breakdown
  • Event and system activity logs
  • Campaign, offer and lander lists
  • Manual cost uploads
  • Raw conversion uploads
Use cases

How media buyers run it

Bulk campaign launches

Clone a proven campaign for each new geo or offer from a script, reusing existing offers and traffic sources instead of duplicating them.

Cost from your own feed

Upload manual cost to campaigns through the API when spend comes from a source ClickFlare doesn't pull for you.

Reports into your stack

Pull report data on a schedule into a BI tool or warehouse, grouped by campaign, offer or traffic source.
Frequently asked questions

REST API integration FAQ

Does ClickFlare integrate with other tools through an API?

Yes. ClickFlare's public REST API has 54 endpoints for campaigns, offers, landers, flows, traffic sources, affiliate networks, domains, integrations and reporting.

How do I authenticate API requests?

Generate an API key in ClickFlare and send it with every request. There is no separate sign-in flow, and requests without a valid key are refused.

Where is the full endpoint reference?

On the ClickFlare developer portal, which also offers the full API description if you want to generate a client.

Can I pull reports through the API?

Yes. You can pull report data grouped the way you need it, so you can feed BI tools, warehouses or your own scripts.

Does the API check that my tracking works?

No. It creates objects only. Campaigns still need the click ID passed to the offer and a postback set up on the network side.

Should I create a new offer for each campaign?

No. Offers, landers, traffic sources and affiliate networks are shared across campaigns. Reuse the existing one, or your reporting splits apart.

No items found.
Setup guides
ClickFlare API overview
{"@context": "https://schema.org", "@graph": [{"@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Does ClickFlare integrate with other tools through an API?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. ClickFlare's public REST API has 54 endpoints for campaigns, offers, landers, flows, traffic sources, affiliate networks, domains, integrations and reporting."}}, {"@type": "Question", "name": "How do I authenticate API requests?", "acceptedAnswer": {"@type": "Answer", "text": "Generate an API key in ClickFlare and send it with every request. There is no separate sign-in flow, and requests without a valid key are refused."}}, {"@type": "Question", "name": "Where is the full endpoint reference?", "acceptedAnswer": {"@type": "Answer", "text": "On the ClickFlare developer portal, which also offers the full API description if you want to generate a client."}}, {"@type": "Question", "name": "Can I pull reports through the API?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. You can pull report data grouped the way you need it, so you can feed BI tools, warehouses or your own scripts."}}, {"@type": "Question", "name": "Does the API check that my tracking works?", "acceptedAnswer": {"@type": "Answer", "text": "No. It creates objects only. Campaigns still need the click ID passed to the offer and a postback set up on the network side."}}, {"@type": "Question", "name": "Should I create a new offer for each campaign?", "acceptedAnswer": {"@type": "Answer", "text": "No. Offers, landers, traffic sources and affiliate networks are shared across campaigns. Reuse the existing one, or your reporting splits apart."}}], "dateModified": "2026-11-12"}, {"@type": "BreadcrumbList", "itemListElement": [{"@type": "ListItem", "position": 1, "name": "Integrations", "item": "https://www.clickflare.com/integrations"}, {"@type": "ListItem", "position": 2, "name": "Automation", "item": "https://www.clickflare.com/integrations/automation"}, {"@type": "ListItem", "position": 3, "name": "REST API"}]}]}