The RefCampaign API powers everything you can do from the merchant dashboard — and a few things you can't, like server-to-server conversion tracking and bulk operations on commissions.

Endpoints are versioned under `/api/v1/*` and authenticated with Bearer JWT issued from the dashboard. Responses follow a consistent envelope, errors return machine-readable codes, and the spec is published as OpenAPI 3.1.

## Where to start

* **[Getting started](/docs/api/getting-started)** — sign up, generate an API key, send your first request.
* **[Authentication](/docs/api/authentication)** — how API keys work, header format, and rotation.
* **[Integration / SDK](/docs/api/integration/sdk)** — drop the official `@refcampaign/sdk` package into a JS / TS app.
* **[Integration / S2S postback](/docs/api/integration/postback)** — track conversions directly from your backend without the SDK.
* **[Error handling](/docs/api/error-handling)** — error envelope, codes, retries.
* **[API reference](/docs/api/reference)** — auto-generated, every endpoint with try-it-out.

## Stability and versioning

The current version is `v1`. All public endpoints live under `/api/v1/*`. Breaking changes ship behind a new version prefix; `v1` continues to receive non-breaking additions. Deprecations are announced via a `Deprecation` HTTP header at least 90 days before removal.

## Need help?

Open an issue on the [SDK repo](https://github.com/RefCampaign/sdk) or contact us through the merchant dashboard.