---
title: "Get Tenant Status Endpoint"
method: GET
path: "/api/v1/tenants/{tenant_id}/status"
tags: ["tenants"]
---

# Get Tenant Status Endpoint

`GET /api/v1/tenants/{tenant_id}/status`

## Request

- Base URL: `https://api.aws.cognee.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api.aws.cognee.ai/api/v1/tenants/{tenant_id}/status`
- Auth: API key in header `X-Api-Key`

Single-shot k8s status for a tenant, backed by the k8s control plane —
covers provisioning, readiness, and health, not just the initial
provisioning phase. Lets the frontend tell "still provisioning" apart
from a genuine failure instead of guessing from how long a direct pod
ping has been failing (see wait_for_tenant_instance_provisioning for
the equivalent polling loop used synchronously during creation itself).

## Response
`{"tenant_id": str, "status": "provisioning" | "healthy" | "suspended" | "failed" | "terminating" | "unknown"}`

`suspended` means the tenant is scaled to zero with its data intact. It
will not come up on its own — the client should offer a restore action
(POST /{tenant_id}/restore) rather than keep polling.

## Path parameters

- `tenant_id` string, uuid, required

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/cognee/apis/cognee-api.md) - [All operations](https://skmtc.dev/cognee/apis/cognee-api/llms.txt) - [OpenAPI document](https://skmtc.dev/cognee/apis/cognee-api/revisions/a7b6c6cb8212?raw)