# Delete a role binding

**DELETE** `/admin/role-bindings/{role_binding_id}`

:::code-group
```bash title="cURL"
curl --request DELETE \
  --url https://api.pinecone.io/admin/role-bindings/{role_binding_id} \
  --header 'Authorization: Bearer <token>'
```

```json title="401"
{
  "error": {
    "code": "QUOTA_EXCEEDED",
    "message": "The index exceeds the project quota of 5 pods by 2 pods. Upgrade your account or change the project settings to increase the quota."
  },
  "status": 429
}
```
:::

## Authorizations

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

## Path Parameters

- `role_binding_id` (path, string, required) — Role binding ID

## Headers

- `X-Pinecone-Api-Version` (header, string, required) — Required date-based version header

## Response

- `202` — Role binding deletion accepted. The binding is removed immediately; it then returns 404, and repeating the request returns 404 as well.
- `401` — Unauthorized. Possible causes: Invalid API key.
- `403` — Forbidden
- `404` — Not found
- `409` — Conflict. The request conflicts with the persisted state of the resource. Common causes include invariant violations (e.g., removing the last `OrgOwner`), lifecycle-state mismatches (e.g., resending an invite that is not pending), and constraint violations checked against persisted data.
- `500` — Internal server error.
- `4XX` — Unexpected error on request.

## Related pages

- [List role bindings](./admin-2-2026-07-admin-role-bindings-list-role-bindings.md)
- [Create a role binding](./admin-2-2026-07-admin-role-bindings-create-a-role-binding.md)
- [Get role binding details](./admin-2-2026-07-admin-role-bindings-get-role-binding-details.md)
- [Create a role binding](./admin-2-2026-04-admin-create-role-binding.md)
- [List role bindings](./admin-2-2026-04-admin-list-role-bindings.md)
- [Get role binding details](./admin-2-2026-04-admin-fetch-role-binding.md)
- [Delete a role binding](./admin-2-2026-04-admin-delete-role-binding.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.