API observability
Last updated 2026-06-15
Definition
API observability is the per-endpoint view of your own backend: how often each route is called, how many calls fail, how slow they run, and which endpoints are bottlenecks. You add a one-line Quri meter, and your API's behaviour shows up next to your marketing and revenue numbers. No agent, no console, no second dashboard to babysit.
How to do this in Quri
- Create an API write key in your Quri workspace.
- Install the meter in your backend: npm i @quri/api-meter.
- Add the one-line middleware and pass your deploy version.
- Open API Health to see the per-endpoint breakdown within minutes.
Frequently asked
- Does the meter capture request bodies or personal data?
- No. It records metadata only — a normalized route, the method, the status, and timing. Ids in the path are collapsed to :id inside the SDK, so raw values never leave your server.
- Which endpoint is my slowest?
- API Health ranks routes by latency and flags bottlenecks. You can also just ask Quri in chat — "what is my slowest endpoint?" — and it answers from the same data.