```javascript JavaScript theme={null}
// Requires Node.js SDK v8.2.0 or later
import { AdminClient } from '@pinecone-database/pinecone';

// Reads PINECONE_CLIENT_ID and PINECONE_CLIENT_SECRET from the environment
const admin = new AdminClient();

await admin.roleBindings.delete('YOUR_ROLE_BINDING_ID');
```

```go Go theme={null}
// Requires Go SDK v6.0.0 or later
package main

import (
    "context"
    "log"
    "os"

    "github.com/pinecone-io/go-pinecone/v6/pinecone"
)

func main() {
    ctx := context.Background()

    adminClient, err := pinecone.NewAdminClientWithContext(ctx, pinecone.NewAdminClientParams{
        ClientId:     os.Getenv("PINECONE_CLIENT_ID"),
        ClientSecret: os.Getenv("PINECONE_CLIENT_SECRET"),
    })
    if err != nil {
        log.Fatalf("Failed to create AdminClient: %v", err)
    }

    if err := adminClient.RoleBinding.Delete(ctx, "YOUR_ROLE_BINDING_ID"); err != nil {
        log.Fatalf("Failed to delete role binding: %v", err)
    }
}
```

```hcl Terraform theme={null}
# Requires Terraform provider v4.0.0 or later
# This block defines the role binding. To revoke the role, either remove the
# block and run `terraform apply`, or run:
#   terraform destroy -target=pinecone_role_binding.ci_data_plane_editor
resource "pinecone_role_binding" "ci_data_plane_editor" {
  principal_type = "service_account"
  principal_id   = "f8a3b2c1-4d5e-6f7a-8b9c-0d1e2f3a4b5c"
  resource_type  = "project"
  resource_id    = "a2f7dddb-1597-4eff-9f71-535fde243f58"
  role           = "DataPlaneEditor"
}
```

```bash curl theme={null}
PINECONE_ACCESS_TOKEN="YOUR_ACCESS_TOKEN"
PINECONE_ROLE_BINDING_ID="YOUR_ROLE_BINDING_ID"

curl -X DELETE "https://api.pinecone.io/admin/role-bindings/$PINECONE_ROLE_BINDING_ID" \
	-H "X-Pinecone-Api-Version: 2026-04" \
	-H "Authorization: Bearer $PINECONE_ACCESS_TOKEN"
```

**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)
- [Delete a role binding](./admin-2-2026-07-admin-role-bindings-delete-a-role-binding.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)

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