Prosper202 ClickServer API
Pull Prosper202 report data into your own apps and scripts with an API key and the v1 reports endpoint.
The Prosper202 ClickServer API lets your own dashboards, scripts and apps work with ClickServer without opening the web interface. The REST API is open on every install, free or Pro.
REST API v3
The current API is v3. It authenticates with a bearer token and covers campaigns, goals, events, apps, customer LTV, subscriptions, forecasts, sync and system operations. Listing campaigns looks like this:
curl https://your-domain.com/api/v3/campaigns \
-H "Authorization: Bearer YOUR_API_TOKEN" \
-H "Accept: application/json"
Your own backend can also send conversion events to POST /api/v3/events.
The API is strict about input. A body field it doesn't recognise gets a 422 that names the field rather than being dropped. Amounts and counts arrive as JSON numbers. time_from and time_to accept unix seconds, a YYYY-MM-DD day in your account's time zone, or an ISO time that carries its offset.
API keys
- Find or create keys under My Account > Personal Settings > API keys. A key an AI app's connection created is labelled with the app's name.
- Give each app or integration its own key, so you can cut one off without breaking the rest.
- A key works as the user it belongs to.
- Keep keys secure: whoever holds one can read your data.
The original v1 reports endpoint
Older integrations pull reports from v1, at your tracking domain:
http://[[your-Prosper202-domain]]/api/v1/
Its one method is reports.
Report arguments
| Argument | Required | Notes |
|---|---|---|
type | Yes | keywords, ips, text_ads, referers, countries, cities, carriers or landing_pages |
apikey | Yes | A key created in ClickServer |
date_from | No | mm/dd/yyyy. Send it together with date_to; leave both out for today |
date_to | No | mm/dd/yyyy. Only one of the two dates gets "Wrong date format" |
cid | No | One of your campaign ids, written exactly. Left out, empty or 0, every campaign is included; anything else gets "Campaign not found" |
c1, c2, c3, c4 | No | One value each, matched against what that variable stored (0 counts as a value). A list such as c1[]=x gets "c1 takes one value" |
A countries report for campaign 1 over a date range:
http://[[your-Prosper202-domain]]/api/v1/reports/?type=countries&apikey=YOUR_API_KEY&date_from=03/24/2014&date_to=04/27/2014&cid=1
Attribution over REST
Multi-touch attribution models are managed under /api/v3/attribution/models, for example PUT /api/v3/attribution/models/{id} with {"status": "inactive"} to switch one off. Older /api/v2/attribution endpoints were never in a release. The Multi-touch Attribution QA Runbook covers the details.
AI assistants (1.9.78 and later)
AI apps that speak MCP can read your reports and setup, and change things only if you allow it. Both routes need ClickServer Pro:
- claude.ai and other hosted apps: add the connector
https://mcp.tracking202.com/mcp, typed exactly, with/mcpat the end (in ChatGPT, custom connectors need developer mode). You sign in on your own install, which must be reachable from the internet over HTTPS, and pick read only, read and propose changes, or read and change. That approval creates an API key labelled after the app, so your role must be allowed to create keys; revoke that key to disconnect. The key never reaches users, API keys or system settings. - Desktop apps such as Claude Desktop, Claude Code and Cursor: point them at
p202 mcp, covered in the p202 CLI Reference.
A hosted connection reads at most about 1 MB from your install per tool call. A big list or a long-range forecast can pass that, and the assistant is then asked to narrow it. Local p202 mcp has no such cap.
From the command line
The p202 CLI uses the same API key, data and permissions as the web UI, and returns JSON. Unlike the REST API, it needs Prosper202 Pro on the install (a 7-day trial is enough). See the p202 CLI Reference.
Full guide on prosper.tracking202.com
Key setup, token authentication and every report argument, with a complete example call: the Prosper202 ClickServer reporting API guide
Updated 13 days ago