Skip to main content

​
Usage

​
What this is for

Your plan includes a number of API requests each month. Usage shows how much of that allowance you have used, whether those requests were live or test, and how requests, errors and speed have looked over the last day or week. Use it to spot a runaway script, plan an upgrade, or just confirm your app is healthy.

​
Before you start

  • Any member can view Usage.
  • The figures cover your whole organization, not a single project. The project Usage page and the Usage section of Organization settings show the same numbers.
  • Numbers appear after requests have been made.

​
Read your usage

1

Open Usage

Choose Usage in the sidebar. The page is titled Usage: “Requests, errors and latency for this project.”
2

Check the meter

The Requests this month card shows a count and your limit, such as “120 / 1,000”, a bar, and when it resets: “Resets in N days” (or “Resets tomorrow”). The month resets at midnight UTC on the 1st.
3

Check the split

This month by environment shows Live requests, Test requests, Active live keys and Active test keys.
4

Look at the charts

The Usage section has three charts, Requests, Errors and Latency. Switch between 24 hours and 7 days.

​
What you’ll see

  • What counts toward the limit. On a paid plan the meter counts live requests; test requests are free. A line under the bar reads, for example, “Live (billable): 120 · Test (free): 50”. On the Free plan every test request counts: “Free plan: test requests count toward the quota (N so far).”
  • No limit recorded: the meter shows ”/ —” and “No monthly limit is recorded for this organization.”
  • Errors shows the number of failed requests and the share, such as “12 (2.4%)”. It shows — when there were no requests.
  • Latency shows the average time in milliseconds, such as “140 ms avg”, or — when there was no traffic. Latency simply means how long the API took to answer.
  • A note says compute and storage usage arrive with dedicated projects.

​
Common questions

Past the limit the API answers with a 429 error (MONTHLY_QUOTA_EXCEEDED for the monthly pool). The Errors page explains exactly what happens, including overage on paid plans: see Errors: rate limits and quotas.
On Free, test requests count toward the 1,000 requests a month. On paid plans test requests are free.
Usage is organization-wide, so every project shows the same totals.
A request that returned a failure status (4xx or 5xx). A few errors are normal during development.
No requests in that window. Send one and look again.

​
Troubleshooting