# Describe a namespace

For guidance and examples, see [Manage namespaces](/guides/manage-data-manage-namespaces).

**Note:** This operation is not supported for pod-based indexes.

```bash curl theme={null}
PINECONE_API_KEY="YOUR_API_KEY"
INDEX_HOST="YOUR_INDEX_HOST"
NAMESPACE="YOUR_NAMESPACE"  # To target the default namespace, use "__default__".

curl "https://$INDEX_HOST/namespaces/$NAMESPACE" \
    -H "Api-Key: $PINECONE_API_KEY" \
    -H "X-Pinecone-Api-Version: 2026-07"
```

`GET /namespaces/{namespace}`

:::code-group
```bash title="cURL"
curl --request GET \
  --url https://{index_host}/namespaces/{namespace} \
  --header 'Authorization: Bearer <token>'
```

```json title="200"
{
  "name": "example-namespace",
  "record_count": "20000",
  "schema": {
    "fields": {
      "description": {
        "filterable": true
      },
      "genre": {
        "filterable": true
      },
      "year": {
        "filterable": true
      }
    }
  },
  "indexed_fields": {
    "fields": [
      "genre",
      "year",
      "author"
    ]
  },
  "size_bytes": "1048576"
}
```
:::

## Authorizations

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

## Path Parameters

- `namespace` (path, string, required) — The namespace to describe. Must be ASCII, must not contain the NUL character, and must be 1-512 characters long. Use `__default__` to describe the namespace that requests address when they omit a namespace.

## Headers

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

## Response

- `200` — A description of a namespace.
- `400` — Bad request. The request body included invalid request parameters.
- `401` — Unauthorized. Possible causes: missing or invalid API key.
- `404` — Namespace not found. No namespace of the given name exists on the index.
- `429` — Too many requests. This operation is rate limited per index and per namespace. Prefer `GET /namespaces` when describing more than one namespace: it returns the same information for every namespace in a single request.
- `4XX` — An unexpected error response.
- `5XX` — An unexpected error response.

## Related pages

- [List namespaces](./database-2026-07-data-plane-listnamespaces.md)
- [Create a namespace](./database-2026-07-data-plane-createnamespace.md)
- [Delete a namespace](./database-2026-07-data-plane-deletenamespace.md)
- [List namespaces](./database-2026-04-data-plane-listnamespaces.md)
- [Create a namespace](./database-2026-04-data-plane-createnamespace.md)
- [Describe a namespace](./database-2026-04-data-plane-describenamespace.md)
- [Delete a namespace](./database-2026-04-data-plane-deletenamespace.md)
- [List namespaces](./database-2025-10-data-plane-listnamespaces.md)
- [Create a namespace](./database-2025-10-data-plane-createnamespace.md)
- [Describe a namespace](./database-2025-10-data-plane-describenamespace.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.