# Integration and usage

Where operators and developers see API keys, per-key usage and webhook health.

The WireBloom console shows how an integration behaves, so you can confirm a key rotation, spot errors and see webhook health without asking support.

## Operators: the Integration page

Operator staff open **Integration** in the operator console for each tenant. It shows:

- the active banking connection and its environment and health;
- the provider webhook registration state;
- every API key with its usage per key: requests per day, error rate, last used and rate-limit hits;
- the status of the customer's integrator webhook endpoints;
- links to this portal and to the sandbox.

## Developers: your keys only

Customer users with API-key management (Settings → Integrations) see a developer view with **their own keys and their usage only**: the same per-key figures and the last 100 requests of each key over 7 days (method, route, status, time taken, request id), never other customers' data. The same data is available from `GET /v1/developer/api-usage` and `GET /v1/developer/api-keys/{apiKeyId}/requests`.

## How usage is counted

Every API request made with a key is counted per key and per day (UTC). Usage is aggregated daily; today and yesterday are computed live from the request log, so a call appears within a few seconds. The request log is kept 7 days, daily figures 400 days. Request and response bodies are never stored for usage. Rate-limit hits are `429` [`rate-limited`](/errors#rate-limited) responses.
