Get user details

Get a user in the caller’s organization by ID.

GET /admin/users/{user_id}

curl

PINECONE_ACCESS_TOKEN="YOUR_ACCESS_TOKEN"
PINECONE_USER_ID="e2e92523-85dc-4142-b8c2-e681be8b78df"

curl -X GET "https://api.pinecone.io/admin/users/$PINECONE_USER_ID" \
	-H "Authorization: Bearer $PINECONE_ACCESS_TOKEN" \
	-H "accept: application/json" \
	-H "X-Pinecone-Api-Version: 2026-04"

curl

{
  "id": "e2e92523-85dc-4142-b8c2-e681be8b78df",
  "email": "[e-mail]",
  "name": "Alice Example",
  "created_at": "2026-04-10T15:23:00Z",
  "updated_at": "2026-04-12T09:11:00Z"
}

curl

PINECONE_ACCESS_TOKEN="YOUR_ACCESS_TOKEN"
PINECONE_USER_ID="e2e92523-85dc-4142-b8c2-e681be8b78df"

curl -X GET "https://api.pinecone.io/admin/users/$PINECONE_USER_ID" \
	-H "Authorization: Bearer $PINECONE_ACCESS_TOKEN" \
	-H "accept: application/json" \
	-H "X-Pinecone-Api-Version: 2026-04"

curl

{
  "id": "e2e92523-85dc-4142-b8c2-e681be8b78df",
  "email": "[e-mail]",
  "name": "Alice Example",
  "created_at": "2026-04-10T15:23:00Z",
  "updated_at": "2026-04-12T09:11:00Z"
}

Authorizations

Authorization · string · header · required

An access token must be provided in the Authorization header using the Bearer scheme.

Headers

X-Pinecone-Api-Version · string · default: 2026-04 · required

Required date-based version header

Path Parameters

user_id · string<uuid> · required

User ID

Response

200

application/json

The user's details. Role bindings are not included; use GET /admin/role-bindings to list the user's roles.

A user who is a member of the organization.

id · string<uuid> · required

The unique ID of the user.

email · string<email> · required

The user's email address.

name · string

The user's display name. Omitted from the response if the user has not set one.