Developer documentation

Everything a developer needs to connect a merchant site to affilink's conversion tracking. Two documents, in reading order:

1. Integration guide

The four steps your site must implement: capture the click ID on landing, persist it as a first-party cookie, let it ride through checkout, and report the completed order server-to-server. Includes working code for WooCommerce (PHP) and Node.js.

2. Postback API reference

The full contract of POST /v1/postback: HMAC-SHA256 request signing, idempotency, refunds, recurring subscription renewals, staged (CRM/lead-gen) conversions, error codes, and the legacy GET fallback.

3. Troubleshooting

Conversion not recorded? A status-code-by-status-code debugging guide, ordered by how often each cause actually happens - including the classic async-order-completion trap and an HMAC self-check snippet.

4. Public API reference

Bearer-key REST API for everything the dashboard does: offers, tracking links, reports, applications, vendors. Keys are created in the dashboard (Growth plan and up) and expire after 30 days.