---
title: "Read everything this key did"
method: GET
path: "/v1/keys/report"
tags: ["API Keys"]
---

# Read everything this key did

`GET /v1/keys/report`

Self-service report for the presented key: daily traffic, endpoints called, what failed with a plain-language cause and a suggested fix, and how many distinct networks the key was called from. Authentication is the key itself, and the report only ever covers that key. A human-readable version of the same data is at https://ibanforge.com/en/account. The footprint reports `unusual: null`, never false, for a key with no traffic: a key that has never been called has not passed a leak check, it has nothing to judge. Its `usage` block is the one GET /v1/keys/usage serves, `basis` included.

## Query parameters

- `days` integer

## Response `200`

Usage, traffic shape, failures with their cause, and network footprint

## Other responses

- `401` — Missing or invalid API key

---

[API](https://skmtc.dev/ibanforge/apis/ibanforge-api.md) · [All operations](https://skmtc.dev/ibanforge/apis/ibanforge-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/ibanforge/ibanforge-api/revisions/9499dba434ea/schema)