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

# Authentification

> How to authenticate your requests ?

To authenticate your requests to the Pipecorn API, you'll need to include your API key in the request headers.

## Getting your API key

You can find your API key in your [Pipecorn dashboard settings](https://app.pipecorn.com/settings/apis/keys).

## Using your API key

Include your API key in the `X-API-KEY` header with all API requests:

```json theme={null}
X-API-KEY: your_api_key
```

## Personal and workspace API keys

Every plan gives each user a **personal API key**, sent in the `X-API-KEY`
header. Workspaces on the **Scale plan** can also create a **workspace API
key**, sent in the `X-WORKSPACE-KEY` header instead.

```json theme={null}
X-WORKSPACE-KEY: your_workspace_key
```

Send one or the other, not both. A request carrying `X-WORKSPACE-KEY` does not
need `X-API-KEY`.

|                          | Personal API key                                            | Workspace API key                                          |
| ------------------------ | ----------------------------------------------------------- | ---------------------------------------------------------- |
| **Header**               | `X-API-KEY`                                                 | `X-WORKSPACE-KEY`                                          |
| **Available on**         | All plans                                                   | Scale plan                                                 |
| **Belongs to**           | One user                                                    | The workspace                                              |
| **Accounts used**        | Yours only                                                  | Rotates across the accounts connected by workspace members |
| **When a member leaves** | Their key stops working, and integrations built on it break | Keeps working                                              |
| **Credits and limits**   | Your workspace's balance and plan limits                    | The same workspace balance and plan limits                 |

### Account rotation

Requests authenticated with a workspace key are not tied to one member's
LinkedIn or Sales Navigator session. Pipecorn rotates them across the accounts
connected by the members of your workspace, so live extraction throughput
grows with the size of your team and no single account carries the whole load.

<Tip>
  Use a **workspace API key** for anything that should outlive one person's
  account or needs sustained volume: production integrations, CRM syncs,
  scheduled jobs, and shared agents or MCP clients. Keep **personal API keys**
  for scripts and experiments you run yourself.
</Tip>

<Note>
  Workspace API keys are only available on the Scale plan. On other plans, use
  a personal key. See [pricing](https://pipecorn.com/pricing) for what each
  plan includes.
</Note>