> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kraken.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Affiliate Introduction

> Overview of the Affiliate REST API — referred-user activity for approved partners

The Affiliate API is for approved affiliate (KOL) partners. It is not a trading
surface. There is no WebSocket or FIX feed; everything is REST on
`https://api.kraken.com`.

You only ever see your own referrals. The caller is the API-key owner.

<Card title="Affiliate REST OpenAPI" icon="download" href="/openapi/affiliate-rest.yaml">
  Download the Affiliate REST OpenAPI spec (YAML)
</Card>

## What you can do

| Workflow                                                    | Endpoint                                                        |
| ----------------------------------------------------------- | --------------------------------------------------------------- |
| Activity for one UTC trade day                              | `GET /affiliate/v1/daily-activity?activity_date=`               |
| Activity for up to ten known participants over a date range | `GET /affiliate/v1/daily-activity?iiban=&start_date=&end_date=` |

Each item is one referred user, split by plan and then by product (volume, fees,
commission). Schemas are in [Get Daily Activity](/api-reference/affiliate/get-daily-activity).

Further affiliate endpoints will land in this section.

## Prerequisites

* An approved affiliate (KOL) account that is the main referrer on a live KOL plan
* An API key with permission to query referrals
* Your API secret for request signing

<Note>
  A key that is not the main referrer on a live KOL plan receives `403`
  (`ReferrerNotWhitelisted`). Cashback-only or extra unmarked plans do not count.
</Note>

## Conventions

* **UTC calendar days** (`YYYY-MM-DD`). Today or one of the previous 89 UTC days.
* **Reporting currency** is `USD` today — not the payout asset.
* **Authentication** is the same HMAC-SHA512 key as other private Exchange REST
  calls. The signed path includes the query string.

## Getting started

<CardGroup cols={3}>
  <Card title="REST" icon="code" href="/exchange/guides/affiliate/rest">
    Signing, day vs history, product keys, pagination
  </Card>

  <Card title="Rate limits" icon="gauge" href="/exchange/guides/affiliate/ratelimits">
    Call counter, polling cadence, and throttle errors
  </Card>

  <Card title="Get Daily Activity" icon="book" href="/api-reference/affiliate/get-daily-activity">
    Request and response schemas
  </Card>
</CardGroup>