---
title: Get average throughput for an app (v2)
source: https://docs.newrelic.com/docs/apis/rest-api-v2/application-examples-v2/get-average-throughput-app-v2
---

You can use the New Relic REST API (v2) to obtain the average throughput for your app, including [web application](https://docs.newrelic.com/docs/using-new-relic/welcome-new-relic/getting-started/glossary#transaction) and [non-web application](https://docs.newrelic.com/docs/using-new-relic/welcome-new-relic/getting-started/glossary#non-web-transaction) throughput. These values appear in the [Throughput chart](https://docs.newrelic.com/docs/apm/applications-menu/monitoring/apm-overview-page-view-transaction-apdex-usage-data#overview_charts) on your app's **APM Summary** page.

> #### ⚠️ IMPORTANT
>
> While the examples utilize New Relic's REST API v2, we recommend using [NRQL functions](https://docs.newrelic.com/docs/nrql/get-started/introduction-nrql-new-relics-query-language/) for executing metric timeslice queries. Each API value can be mapped to an equivalent NRQL function. To learn how to create NRQL queries based on these API examples, refer to our [documentation](https://docs.newrelic.com/docs/apis/rest-api-v2/migrate-to-nrql/).

1.  Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > APM & services > (select an app)**.
2.  Click the app's **Transaction time chart** title, then select your choice.

## Web app throughput [#api-call]

To find the average web application throughput value for a time period, use a single command to get the metric `HttpDispatcher`:`requests_per_minute`. This example shows the time range for a specific 24 hour period.

```bash
curl -X GET "https://api.newrelic.com/v2/applications/${APP_ID}/metrics/data.json" \
     -H "X-Api-Key:${API_KEY}" -i \
     -d 'names[]=HttpDispatcher&values[]=requests_per_minute&from=2014-02-21T23:59:00+00:00&to=2014-02-22T23:59:00+00:00&summarize=true'
```

-   Be sure to replace `${APPID}` and `${APIKEY}` with your [application ID](https://docs.newrelic.com/docs/apm/apis/requirements/identification-code) and [API key](https://docs.newrelic.com/docs/apis/rest-api-v2/requirements/rest-api-key) for the account.
-   To change the [time range](https://docs.newrelic.com/docs/apm/apis/requirements/extracting-metric-data), include `from` and `to` values.
-   To keep the [default time period](https://docs.newrelic.com/docs/apm/apis/api-v2-examples/specifying-time-range-api-v2) of the last 30 minutes, omit the `from` and `to` values.
-   To return a series of throughput values instead of an [average](https://docs.newrelic.com/docs/apm/apis/requirements/calculating-average-metric-values-summarize), omit `summarize`.

## Web app throughput (single host) [#api-call-web-single]

To find the average throughput from a single host, for a given time period, use a single command to get the metric `HttpDispatcher`:`requests_per_minute`, and specify the numeric `${HOST}`. To identify the host, use the [UI or the REST API](https://docs.newrelic.com/docs/apis/rest-api-v2/requirements/listing-host-instance-application-server-ids#locating_host_id).

This example shows the time range for a specific 24 hour period.

```bash
curl -X GET "https://api.newrelic.com/v2/applications/${APP_ID}/hosts/${HOST}/metrics/data.json" \
     -H "X-Api-Key:${API_KEY}" -i \
     -d 'names[]=HttpDispatcher&:values[]=requests_per_minute&from=2014-02-21T23:59:00+00:00&to=2014-02-22T23:59:00+00:00&:summarize=true'
```

## Non-web app throughput [#api-call]

To find the average non-web application throughput value for a given time period, use a single command to get the metric `OtherTransaction/all`:`requests_per_minute`.

This example shows the time range for a specific 24 hour period.

```bash
curl -X GET "https://api.newrelic.com/v2/applications/${APP_ID}/metrics/data.json" \
     -H "X-Api-Key:${API_KEY}" -i \
     -d 'names[]=OtherTransaction/all&values[]=requests_per_minute&;from=2014-02-21T23:59:00+00:00&to=2014-02-22T23:59:00+00:00&summarize=true'
```

-   Be sure to replace `${APPID}` and `${APIKEY}` with your [application ID](https://docs.newrelic.com/docs/apm/apis/requirements/identification-code) and [API key](https://docs.newrelic.com/docs/apis/rest-api-v2/requirements/rest-api-key) for the account.
-   To change the [time range](https://docs.newrelic.com/docs/apm/apis/requirements/extracting-metric-data) (as shown in this example), include `from` and `to` values.
-   To keep the [default time period](https://docs.newrelic.com/docs/apm/apis/api-v2-examples/specifying-time-range-api-v2) (last 30 minutes), omit the `from` and `to` values.
-   To return a series of throughput values instead of an [average](https://docs.newrelic.com/docs/apm/apis/requirements/calculating-average-metric-values-summarize), omit `summarize`.

## Non-web app throughput (single host) [#api-call-non-web-single]

To obtain the average throughput for a non-web app from a single host, for a given time period, use a single command to obtain the metric `OtherTransaction`:`requests_per_minute` and specify the numeric `${HOST}`. To identify the host, use the [UI or the REST API](https://docs.newrelic.com/docs/apis/rest-api-v2/requirements/listing-host-instance-application-server-ids#locating_host_id).

This example shows the time range for a specific 24 hour period.

```bash
curl -X GET "https://api.newrelic.com/v2/applications/${APP_ID}/hosts/${HOST}/metrics/data.json" \
     -H "X-Api-Key:${API_KEY}" -i \
     -d 'names[]=OtherTransaction/all&:values[]=requests_per_minute&from=2014-02-21T23:59:00+00:00&to=2014-02-22T23:59:00+00:00&:summarize=true'
```