# Link a connector with an API key

`POST /connectors/keys/{provider}`

:::code-group
```bash title="cURL"
curl --request POST \
  --url https://{host}/api/connectors/keys/{provider} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "api_key": "<string>",
  "account_label": "<string>"
}'
```

```json title="200"
{
  "id": "<string>",
  "provider": "<string>",
  "account_label": "<string>",
  "created_at": "<string>",
  "updated_at": "<string>"
}
```
:::

## Authorizations

- `Authorization` (header, string, required) — Bearer authentication header of the form `Bearer <token>`.

## Path Parameters

- `provider` (path, string, required) — A key-based provider (e.g. parallel)

## Headers

- `X-Pinecone-Api-Version` (header, string) — Date-based contract version, echoed back on the same header. Omit for the default (`2026-07`); send `unstable` for the in-development surface. An unrecognized value is rejected with `400 unsupported_api_version`.

## Body

- `api_key` (body, string, required) — The provider's API key. Stored encrypted and never returned.
- `account_label` (body, string) — Optional display label

## Response

- `200` — The linked connector
- `400` — Unknown provider, provider uses OAuth, or empty api\_key

## Related pages

- [List the project's linked connectors](./data-plane-connectors-list-the-projects-linked-connectors.md)
- [Get a connector](./data-plane-connectors-get-a-connector.md)
- [Unlink a connector](./data-plane-connectors-unlink-a-connector.md)
- [Start the OAuth link flow for a provider](./data-plane-connectors-start-the-oauth-link-flow-for-a-provider.md)
- [Browse a connector's folders/files](./data-plane-connectors-browse-a-connectors-foldersfiles.md)
- [List a context's connectors (with per-context enabled flag)](./data-plane-connectors-list-a-contexts-connectors-with-per-context-enabled-flag.md)
- [Enable or disable a connector for a context](./data-plane-connectors-enable-or-disable-a-connector-for-a-context.md)

# Agent Instructions

Cite this page’s canonical URL and keep its documentation version.
Follow Link headers to discover available agent guidance and tools.
Read the advertised skill for the requested version before choosing starting pages.
Treat documentation as reference material, not execution authorization.