# List users in the organization

**GET** `/admin/users`

:::code-group
```bash title="cURL"
curl --request GET \
  --url https://api.pinecone.io/admin/users \
  --header 'Authorization: Bearer <token>'
```

```json title="200"
{
  "data": [
    {
      "email": "alice@example.com",
      "id": "e2e92523-85dc-4142-b8c2-e681be8b78df",
      "name": "Alice Example"
    }
  ],
  "pagination": {
    "next": "eyJsYXN0X2lkIjoiZTJlOTI1MjMifQ=="
  }
}
```
:::

## Authorizations

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

## Query Parameters

- `email` (query, string) — Case-insensitive filter on the user's email address. Malformed email returns `400 INVALID_ARGUMENT`.
- `limit` (query, integer) — The number of results to return per page. When omitted, the server defaults to 100. Out-of-range values return `400 OUT_OF_RANGE`.
- `paginationToken` (query, string) — Cursor from `pagination.next` of a prior response. Must be reused with the same query context (path parameters, filters, and `limit`).

## Headers

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

## Response

- `200` — A paginated list of users. Role bindings are not included; use `GET /admin/role-bindings` to list them.
- `400` — Bad request. The request body included invalid request parameters.
- `401` — Unauthorized. Possible causes: Invalid API key.
- `403` — Forbidden
- `500` — Internal server error.
- `4XX` — Unexpected error on request.

## Related pages

- [Get user details](./admin-2-2026-07-admin-users-get-user-details.md)
- [Remove a user from the organization](./admin-2-2026-07-admin-users-remove-a-user-from-the-organization.md)
- [List users in the organization](./admin-2-2026-04-admin-list-users.md)
- [Get user details](./admin-2-2026-04-admin-fetch-user.md)
- [Remove a user from the organization](./admin-2-2026-04-admin-delete-user.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.