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

# Platform API overview

> Automate the sourcings, candidates, and outreach sequences your team runs in the Kalent app.

The **Platform API** is for teams that recruit with the Kalent app and want to automate part of that work: create a sourcing from your ATS, push candidates into it, launch outreach sequences, and read their status back. Everything you create through this API shows up in the app, and everything your recruiters do in the app is visible through it.

## What it covers

<CardGroup cols={3}>
  <Card title="Sourcing" icon="folder-open" href="/api-reference/create-sourcing">
    Create sourcing campaigns and list the ones your workspace owns.
  </Card>

  <Card title="Candidates" icon="users" href="/api-reference/add-talent-to-sourcing">
    Add talents to a sourcing, read and update candidates, and enrich their contact details.
  </Card>

  <Card title="Sequences" icon="paper-plane" href="/api-reference/create-sequence-blueprint">
    Create outreach blueprints, start sequences for candidates, and follow their progress.
  </Card>
</CardGroup>

## What it assumes

* A workspace that your team uses in the Kalent app, with an active Kalent subscription. Sourcings, candidates, and sequences live in that workspace; routes such as [create sourcing](/api-reference/create-sourcing) answer `402 plan_upgrade_required` when the subscription does not include the capability.
* An API key for that workspace; see [Authentication](/authentication).
* API credits for the routes that spend them, such as contact enrichment.

## Same key, same credits as the Embedded API

The [Embedded API](/embedded-api-overview) covers talent search, qualified search, and LinkedIn contact enrichment without any dependency on the app. Both APIs authenticate with the same workspace API key and spend the same API credits. A common pattern is to find talents with the Embedded API, then add the ones you keep to a sourcing with the Platform API so your recruiters take over in the app.

## Next steps

1. Read [Authentication](/authentication) and [Non-deterministic results](/non-deterministic-results).
2. Create a sourcing with [`POST /v1/sourcings`](/api-reference/create-sourcing), then add a talent with [`POST /v1/sourcings/{sourcingId}/candidates`](/api-reference/add-talent-to-sourcing).
3. Import the [Postman collection](/introduction#try-it-in-postman): its Sourcing, Candidates, and Dynamic sequences folders follow the same order.