Docs · 0 articles
Reacheffect API
What the public API covers and where the reference lives.
The public API gives programmatic access to campaigns, statistics, funds and publisher inventory, authenticated with an account-level key from Settings. The published reference lists every endpoint; this page covers what the API is for, how to get and rotate a key, and when the RTB integration is the better fit.
What the API covers
The Reacheffect public API gives programmatic access to the same account you use in the browser: campaign and ad management, statistics, funds and, for publishers, websites and ad zones. Anything an authorized integration does with your key is scoped to your account.
Reference
The full reference, with every endpoint, parameter and response, is published at panel.reacheffect.com/api/docs. It can be downloaded as PDF, YAML or JSON for use in your own tooling.
Getting a key
- Open your account menu → Settings.
- Make sure API access is enabled; on some accounts an administrator switches it on.
- Copy the API key, or click Generate to create one. Rotating the key disables the old one immediately, so update every integration that used it.
Treat the key like a password: never paste it in shared documents, screenshots or support tickets. On team accounts the key stays with the account owner; members work through the dashboard with their own permissions.
Programmatic buying over RTB
DSPs and bidders that want a server-to-server connection instead of the account API use the RTB integration: OpenRTB for CPM formats, XML or JSON feeds for CPC formats.