# Enable or disable a connector for a context

`PUT /contexts/{slug}/connectors/{connector_id}`

:::code-group
```bash title="cURL"
curl --request PUT \
  --url https://{host}/api/contexts/{slug}/connectors/{connector_id} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "enabled": true
}'
```

```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

- `slug` (path, string, required) — Context slug or UUID.
- `connector_id` (path, string, required) — Connector id.

## 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

- `enabled` (body, boolean, required) — Whether this context may import from the connector.

## Response

- `200` — The updated context connector
- `400` — Provider does not support this context kind
- `404` — Context or connector not found

## 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)
- [Link a connector with an API key](./data-plane-connectors-link-a-connector-with-an-api-key.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)

# 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.