Skip to main content
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.

​
Using your API key

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

​
Test keys

To build without spending credits or touching real data, use your test key (it starts with pc_test_) or the public demo key pc_test_demo. They call the same endpoints and return sample data. See Sandbox.

​
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.
Send one or the other, not both. A request carrying X-WORKSPACE-KEY does not need X-API-KEY.

​
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. A member that LinkedIn rate limited is left out of the rotation for 12 hours, as long as another member is available. Every response carries a Pipecorn-Account header with the email of the member whose account served it, and a LinkedIn 429 names that member in account_email. To check every member’s LinkedIn and Sales Navigator session at once, call GET /account with the workspace key.
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.
Workspace API keys are only available on the Scale plan. On other plans, use a personal key. See pricing for what each plan includes.