> ## Documentation Index > Fetch the complete documentation index at: https://docs.pinecone.io/llms.txt > Use this file to discover all available pages before exploring further. # Remove a user from the organization > Remove a user from the organization and revoke their role bindings. Does not delete the user's Pinecone account. Returns `202`. The user's role bindings are revoked immediately, so the user no longer appears in get or list requests and instead returns `404`. A repeat request for the same user returns `404`. Returns `409` when removing the last `OrgOwner` in the organization. ```bash curl theme={null} PINECONE_ACCESS_TOKEN="YOUR_ACCESS_TOKEN" PINECONE_USER_ID="YOUR_USER_ID" curl -X DELETE "https://api.pinecone.io/admin/users/$PINECONE_USER_ID" \ -H "X-Pinecone-Api-Version: 2026-04" \ -H "Authorization: Bearer $PINECONE_ACCESS_TOKEN" ``` ## OpenAPI ````yaml https://raw.githubusercontent.com/pinecone-io/pinecone-api/refs/heads/main/2026-04/admin_2026-04.oas.yaml delete /admin/users/{user_id} openapi: 3.0.3 info: title: Pinecone Admin API description: > Provides an API for managing a Pinecone organization and its resources, including projects, API keys, organization users and invites, service accounts, and role bindings. contact: name: Pinecone Support url: https://support.pinecone.io email: support@pinecone.io license: name: Apache 2.0 url: https://www.apache.org/licenses/LICENSE-2.0 version: 2026-04 servers: - url: https://api.pinecone.io description: Production API endpoints security: - BearerAuth: [] tags: - name: API Keys description: Actions that manage API Keys. - name: Organizations description: Actions that manage organizations. - name: Projects description: Actions that manage projects. - name: Users description: Actions that manage users. - name: Invites description: Actions that manage invites. - name: Service Accounts description: Actions that manage service accounts. - name: Role Bindings description: Actions that manage role bindings. paths: /admin/users/{user_id}: delete: tags: - Users summary: Remove a user from the organization description: > Remove a user from the organization and revoke their role bindings. Does not delete the user's Pinecone account. Returns `202`. The user's role bindings are revoked immediately, so the user no longer appears in get or list requests and instead returns `404`. A repeat request for the same user returns `404`. Returns `409` when removing the last `OrgOwner` in the organization. operationId: delete_user parameters: - in: header name: X-Pinecone-Api-Version description: Required date-based version header required: true schema: default: 2026-04 type: string style: simple - in: path name: user_id description: User ID required: true schema: type: string format: uuid style: simple responses: '202': description: User removal request accepted. '401': description: 'Unauthorized. Possible causes: Invalid API key.' content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: unauthorized: summary: Unauthorized value: error: code: UNAUTHENTICATED message: Invalid API key. status: 401 '403': description: Forbidden content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: Not found content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '409': description: >- 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. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: last-org-owner: summary: Cannot delete the last OrgOwner value: error: code: ABORTED message: >- Cannot delete the last OrgOwner role binding for this organization. status: 409 invite-not-pending: summary: 'Resend rejected: invite is not pending' value: error: code: ALREADY_EXISTS message: Invite has already been accepted and cannot be resent. status: 409 invite-already-pending: summary: >- Invite rejected: pending invite already exists for this email value: error: code: ALREADY_EXISTS message: A pending invite already exists for this email. status: 409 already-member: summary: 'Invite rejected: email already belongs to an org member' value: error: code: ALREADY_EXISTS message: >- This email already belongs to a member of the organization. status: 409 '500': description: Internal server error. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: internal-server-error: summary: Internal server error value: error: code: UNKNOWN message: Internal server error status: 500 4XX: description: Unexpected error on request. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' components: schemas: ErrorResponse: example: 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 description: The response shape used for all error responses. type: object properties: status: example: 500 description: The HTTP status code of the error. type: integer error: example: code: INVALID_ARGUMENT message: >- Index name must contain only lowercase alphanumeric characters or hyphens, and must not begin or end with a hyphen. description: Detailed information about the error that occurred. type: object properties: code: description: >- The error code. Possible values: `OK`, `UNKNOWN`, `INVALID_ARGUMENT`, `DEADLINE_EXCEEDED`, `QUOTA_EXCEEDED`, `NOT_FOUND`, `ALREADY_EXISTS`, `PERMISSION_DENIED`, `UNAUTHENTICATED`, `RESOURCE_EXHAUSTED`, `FAILED_PRECONDITION`, `ABORTED`, `OUT_OF_RANGE`, `UNIMPLEMENTED`, `INTERNAL`, `UNAVAILABLE`, `DATA_LOSS`, `FORBIDDEN`, or `UNPROCESSABLE_ENTITY`. x-enum: - OK - UNKNOWN - INVALID_ARGUMENT - DEADLINE_EXCEEDED - QUOTA_EXCEEDED - NOT_FOUND - ALREADY_EXISTS - PERMISSION_DENIED - UNAUTHENTICATED - RESOURCE_EXHAUSTED - FAILED_PRECONDITION - ABORTED - OUT_OF_RANGE - UNIMPLEMENTED - INTERNAL - UNAVAILABLE - DATA_LOSS - FORBIDDEN - UNPROCESSABLE_ENTITY type: string message: example: >- Index name must contain only lowercase alphanumeric characters or hyphens, and must not begin or end with a hyphen. type: string details: description: >- Additional information about the error. This field is not guaranteed to be present. type: object required: - code - message required: - status - error securitySchemes: BearerAuth: type: http scheme: bearer description: > An [access token](https://docs.pinecone.io/guides/organizations/manage-service-accounts#retrieve-an-access-token) must be provided in the `Authorization` header using the `Bearer` scheme. ````