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

# Keen API

> Programmatically manage leads and channels in your Keen partnerships.

## What is Keen?

Keen is a B2B partner management platform that enables companies to scale through structured referral and reseller partnerships. The platform provides shared lead visibility, attribution by channel, and partnership performance tracking.

Every partnership on Keen has two sides:

* **Receiving company** — the program owner that receives referred leads.
* **Referring company** — the partner that refers leads into the channel.

The Keen API lets you integrate your systems with these partnerships — sync leads from your CRM, submit leads from custom forms, update lead statuses, and record purchases.

## Core concepts

<CardGroup cols={2}>
  <Card title="Channel" icon="arrows-left-right">
    A partnership surface between two companies. Each channel has its own lead statuses, custom properties, and reward triggers.
  </Card>

  <Card title="Lead" icon="user-plus">
    A shared contact record within a channel — the core unit of partnership activity. Leads move through statuses and can have purchases recorded against them.
  </Card>

  <Card title="API key" icon="key">
    A UUID credential scoped to your company. Used in the `X-Api-Key` header to authenticate requests.
  </Card>

  <Card title="Action" icon="bolt">
    The Keen API uses a single endpoint. The `action` field in the request body determines the operation.
  </Card>
</CardGroup>

## Get started

<Steps>
  <Step title="Get your API key">
    Navigate to **Settings > API keys** in your Keen dashboard and generate a new key.
  </Step>

  <Step title="List your channels">
    Make a `get_channels` request to see which channels your company has access to.
  </Step>

  <Step title="Create your first lead">
    Use `create_lead` with a channel ID to submit a lead through the API.
  </Step>
</Steps>

Follow the [quickstart guide](/quickstart) for a step-by-step walkthrough, or jump directly to the [API reference](/api-reference/introduction).