> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scanova.io/llms.txt
> Use this file to discover all available pages before exploring further.

# API usage dashboard

> There is currently no dedicated in-app usage dashboard — here's what's actually visible in the UI today, and where real usage figures live instead.

<Warning>
  Live verification for this page found that **no dedicated API usage dashboard currently exists in the app.** This page documents that gap honestly rather than describing a screen that isn't there. If you need usage figures today, use the Management API's own usage endpoints directly — see [Related](#related) below.
</Warning>

## What was checked

* The **Developer** section of the sidebar has exactly one item, **API** (`/api/keys`) — there is no second "Usage" entry alongside it.
* Navigating directly to `/api/usage` returns the app's 404 page ("Page not found — The page you're looking for doesn't exist or has moved").
* The [API Keys page](/api-keys/creating-and-managing-keys) itself — the one page under Developer → API that does exist — lists **Name**, **API Key**, **Created On**, **Created By**, and **Expires On** per key. It does not surface a usage or request count anywhere in that table, even though the underlying data model (`ApiKeyItem.usage_count`) already carries a lifetime request count for each key — it's simply not rendered in this table.
* A shared internal component (`EnterpriseLockedCard`) contains a code comment describing itself as the "Enterprise-gated" fallback shown on "the Developer > API pages (Keys **and Usage**)" — language that implies a Usage page was planned. It isn't wired into any route today; the only page that actually imports and renders it is the Keys page itself, gating key creation for accounts without Management API access.

Taken together, this reads as a page that was scaffolded for but never shipped, rather than a page that was removed — worth confirming with engineering if you were expecting to find it.

## Where usage data actually lives

Until an in-app dashboard exists, the only way to see Management API usage is to call the usage endpoints directly, using the same OAuth access token you use for the dashboard itself (not a Management API key):

| Endpoint                                                                                    | What it returns                                                                                           |
| ------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
| [`GET /console/usage/`](/api-reference/management-api/tokens/usage-stats)                   | Total / successful / failed request counts for an environment, over a rolling day/week/month/year window. |
| [`GET /console/usage/daily/`](/api-reference/management-api/tokens/usage-daily)             | The same figures broken down per day, for charting a trend yourself.                                      |
| [`GET /console/usage/by-endpoint/`](/api-reference/management-api/tokens/usage-by-endpoint) | A breakdown by individual API route.                                                                      |

<Note>
  These figures are aggregated **per environment** (`sandbox`, `live`, `zapier`, `mcp`), across every key sharing that environment — not per individual key. A single key's own lifetime request count is the `usage_count` field returned by [`GET /console/token/`](/api-reference/management-api/tokens/create#listing-existing-tokens), which — per the gap noted above — isn't currently shown anywhere in the dashboard UI either, only in the raw API response.
</Note>

## Related

* [Usage statistics](/api-reference/management-api/tokens/usage-stats), [Daily usage](/api-reference/management-api/tokens/usage-daily), and [Usage by endpoint](/api-reference/management-api/tokens/usage-by-endpoint) — the technical endpoints to call directly until an in-app dashboard ships.
* [Creating & managing API keys](/api-keys/creating-and-managing-keys) — the one Developer → API page that does exist today.