> For the complete documentation index, see [llms.txt](https://docs.appetize.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appetize.io/account/reporting/usage-summary.md).

# Usage Summary

### With Reporting Page

You can access your usage summary by navigating to your [Reports Dashboard](https://appetize.io/reports) and selecting **download** under:

* **Monthly usage report**
* **Daily usage report** after specifying the month that you are interested in e.g. May 2023

<figure><img src="/files/2clopV6IbkRNW0slqNNR" alt=""><figcaption><p>Select "Download" under Monthly or Daily usage report</p></figcaption></figure>

{% hint style="info" %}
All reports are downloaded in UTC (Coordinated Universal Time) times.
{% endhint %}

### With REST API

You can access your usage report via our REST API. For more information, see

{% content-ref url="/pages/-MJVCSOMbSlFIuVYMwAz" %}
[Usage summary](/rest-api/v1/usage-summary.md)
{% endcontent-ref %}

## Glossary

{% hint style="warning" %}
Please note, depending on the activity and actions you take within Appetize, not all fields may be populated in your reports.
{% endhint %}

| Field                      | Description                                                                                                                   |
| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| **month**                  | The month being reported on                                                                                                   |
| **publicKey**              | The App's publicKey                                                                                                           |
| **numSessions**            | How many sessions were run that month/day on that publicKey                                                                   |
| **minutes**                | How many total minutes for that day/month                                                                                     |
| **platform**               | *iOS* or *Android*                                                                                                            |
| **name\_latest**           | <p>The current name of the app</p><p><br><strong>NOTE</strong>: May differ from when the app was run</p>                      |
| **appdisplayname\_latest** | <p>The current display name of the app</p><p><br><strong>NOTE</strong>: May differ from when the app was run</p>              |
| **bundle\_latest**         | <p>The current <em>bundleId</em> of the app</p><p><br><strong>NOTE</strong>: May differ from when the app was run</p>         |
| **note\_latest**           | <p>The current notes for the app from the dashboard</p><p><br><strong>NOTE</strong>: May differ from when the app was run</p> |

{% hint style="info" %}
Should you have a desire to report on additional fields, please [reach out to us](mailto:hello@appetize.io) and we'll consider it for our roadmap.
{% 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.appetize.io/account/reporting/usage-summary.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.