---
title: "Check assistant status"
method: GET
path: "/assistants/{assistant_name}"
tags: ["Manage Assistants"]
---

# Check assistant status

`GET /assistants/{assistant_name}`

Get the status of an assistant.

For guidance and examples, see [Manage assistants](https://docs.pinecone.io/guides/assistant/manage-assistants#get-the-status-of-an-assistant)

## Path parameters

- `assistant_name` string, required

## Headers

- `X-Pinecone-Api-Version` string, required

## Response `200`

Poll request successful.

- AssistantControlAssistant — Describes the configuration and status of a Pinecone Assistant.
  - `name` string, required — The name of the assistant. Resource name must be 1-63 characters long, start and end with an alphanumeric character, and consist only of lower case alphanumeric characters or `-`.
  - `instructions` string, nullable — Guidance applied to all responses generated by the assistant.
  - `metadata` object, nullable — Optional metadata associated with the assistant. Metadata is a JSON object that can store custom organizational data, tags, and attributes.
  - `status` string, required — The current operational status of the assistant.
  - `host` string — The host where the assistant is deployed.
  - `region` string — The region where the assistant is deployed.
  - `created_at` string, date-time — The timestamp when the assistant was created, in ISO 8601 format (`YYYY-MM-DDTHH:MM:SSZ`).
  - `updated_at` string, date-time — The timestamp of the most recent update to the assistant, in ISO 8601 format (`YYYY-MM-DDTHH:MM:SSZ`).

## Other responses

- `401` — Unauthorized. Possible causes: Invalid API key.
- `404` — Assistant not found.
- `500` — Internal server error.

---

[API](https://skmtc.net/pinecone/apis/pinecone-api.md) · [All operations](https://skmtc.net/pinecone/apis/pinecone-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pinecone/pinecone-api/revisions/35876583485d/schema)