> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/settings/observability/api-call-stats.md). # API Call Stats **Settings → API Call Stats** shows aggregate statistics for calls made to your tenant's API — volumes, endpoints, and outcomes — so you can monitor how your integrations and AI agents are using the platform and spot errors or hotspots before they affect customers. ## Why it matters Integrations, agents, and partner systems all reach PeakCommerce through the same API. This page is your single view of that traffic: it tells you whether callers are succeeding, which endpoints carry the load, and where latency or errors are creeping in — without having to read raw logs. ## What it shows Statistics are aggregated over a selectable time window and broken down by **integration** and by **endpoint**: * **Total calls** — request volume in the window. * **Errors / error rate** — failed calls and their share of the total. * **Latency** — average, p95, and p99 response times, so a slow tail shows up even when the average looks fine. Figures combine recently recorded activity with historical snapshots, so the view stays current between background flushes. ## How to use it * Watch the **error rate** per endpoint — a spike usually means a misconfigured caller or a broken integration credential. * Use the **endpoint breakdown** to find hotspots driving most of your volume, and the **latency percentiles** to catch a degrading dependency early. * Sudden volume changes can flag a runaway agent loop or a new integration behaving unexpectedly. ## Gotchas * Stats are **aggregate**, not a per-request log — use the audit trail for individual events. * Background jobs are attributed to the tenant they run for; unattributed calls indicate an internal caller that hasn't been scoped yet. ## Related * [API Usage](/product/settings/observability/api-usage.md) — consumption trends over time. * [Audit Trail & Logs](/product/reporting-and-analytics/audit-trail-and-logs.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.peakcommerce.com/product/settings/observability/api-call-stats.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.