> For the complete documentation index, see [llms.txt](https://docs.digitalapi.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalapi.ai/developer-portal/test-and-track-usage/app-analytics.md).

# App analytics and usage

The **Analytics** tab on your account tracks how your applications are using the APIs they subscribe to: call volume, success and failure counts, response time, and the most recent requests. Use it to confirm an integration is live, to watch error rates after a release, and to see how close you are to a plan's quota. Reach it from the account menu under **My Profile**, then the **Analytics** sub-tab.

![Figure. The API Usage Analytics view, with KPI tiles, the time-range selector, and the calls and status-code charts.](/files/pTjeVia0yfa9NrQ2EIwd)

### What you see

The page opens on an **Account Overview** that counts your applications as **Total Apps**, **Active**, and **Inactive**, with sub-tabs for **View Profile**, **Edit Profile**, **My Apps**, and **Analytics**. The **API Usage Analytics** section holds the metrics:

* **App filter**: choose which application to report on. It reads **No active apps** until you have one with an active subscription.
* **Time range**: **1H**, **6H**, **24H**, **7D**, **30D**, **90D**, or **Custom**.
* **KPI tiles**: **Total Calls**, **Success Calls**, **Failed Calls**, and **Avg Response Time** for the selected app and window.
* **API Calls Over Time**: a time-series chart of request volume across the window.
* **Status Codes**: the distribution of response codes, so a rise in 4xx or 5xx stands out.
* **Recent Requests**: a list of the latest individual calls for the selected application.

Until an application has an active subscription and has sent traffic, the tiles read as empty and the charts show *No active app subscriptions to show analytics for*.

### Read your usage

1. Open the account menu and choose **My Profile**, then the **Analytics** tab.
2. In the **App** filter, select the application you want to inspect.
3. Pick a **time range** that matches your question: **1H** or **6H** to watch a release, **7D** or **30D** for a trend.
4. Read the KPI tiles for the headline numbers: total calls, successes, failures, and average response time.
5. Use **API Calls Over Time** to spot volume changes and **Status Codes** to catch a spike in errors.
6. Open **Recent Requests** to inspect individual calls behind a number.

### Options

* **Per application**: analytics are scoped to one application at a time. Switch apps in the filter to compare.
* **Custom window**: pick **Custom** to bound the report to a specific incident or billing period.
* **Quota awareness**: rising **Total Calls** against a plan's limit is your early warning to request a higher tier before the gateway starts rejecting calls.

{% hint style="info" %}
The portal reports what the gateway meters. Numbers reflect calls your application made directly to the gateway with its credentials, not anything routed through the portal.
{% endhint %}

### Verify

* Subscribe an application and send a few calls from [Testing an API](/developer-portal/test-and-track-usage/testing-an-api.md).
* Return to **Analytics**, select that application, and confirm **Total Calls** and the **API Calls Over Time** chart reflect the traffic.
* Confirm a failed call appears under **Failed Calls** and in the **Status Codes** chart.

{% hint style="success" %}
**Result:** You can see, per application and per time window, how much your integration is calling, how often it succeeds, and where errors are coming from.
{% endhint %}


---

# 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.digitalapi.ai/developer-portal/test-and-track-usage/app-analytics.md?ask=<question>&goal=<endgoal>
```

`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.