Affiliate Introduction

The Affiliate API is for approved affiliates. It does not accept trades or offer a WebSocket or FIX feed; all requests use REST on https://api.kraken.com. The API uses the account that owns your key to determine which referrals you can see.

​

What you can do

Each daily activity item is one referred user, split by plan and then by product (volume, fees, commission). In full-roster and person-history requests, opted-out users remain visible as existence stubs with a stable reference, enrollment time, and referral code, but no account identifier or individual trading data. Users sharing activity also include their full Kraken account identifier in iiban. Schemas are in Get Daily Activity, Get CPA Progress, and Get Payout History. A referred user who shares activity does not need to trade to appear in the results. On their enrollment day, they have an entry with enrolled_at and empty products, confirming that they are enrolled. Empty products may be omitted. Use all_users=true to include quiet users on later requested days while they remain enrolled. See the request and response examples for trading users, users who have not traded, and users who opted out.

​

Prerequisites

• An approved affiliate account with your own active affiliate plan
• An API key with Query affiliate participants enabled
• Your API secret for request signing

​

API key permission

When creating or editing your API key, select the Query affiliate participants checkbox and save the key. This is the permission required for the Affiliate API. See API key setup for the general setup steps.

​

Conventions

• UTC calendar days (YYYY-MM-DD) for daily activity. Today or one of the previous 89 UTC days.
• Daily activity reporting currency is USD today — not the payout asset. CPA rewards and payout rows identify their asset in reward_asset or asset.
• Authentication is the same HMAC-SHA512 key as other private Exchange REST calls. The signed path includes the query string.

​

Getting started