Who can use this: Tech admin, Business admin
Available on: Any Gong plan
Ideal for: RevOps
Generate the API / MCP usage & rate limit report to see which endpoints, tools, integrations, keys, and team members use your company's API and MCP quota.
Generate the report
Generate the report when you hit a rate limit and need to find the integration, key, or team member behind it.
To generate the report:
- From the left sidebar, click Admin center.
- In the Settings tab, click API / MCP usage & rate limit under Reports.
- Under Choose Domain, deselect API or MCP if you don't want the report to include both domains.
- Under Timeframe, select Last 30 days, Last 60 days, Last 90 days, or Custom date range.
Note: A custom range can cover up to three months. - (Optional) In the Maximum rows field, enter the maximum number of rows you want in the report.
Note: The default is 100,000, and the maximum is 1,000,000. If the data has more rows than this number, the report leaves out the newest hours. [VERIFY: Does the report keep the oldest hours and drop the newest when it reaches the maximum? Source: placeholder SQL in an open pull request. Ask Yuval Cohen Mednyk.] - Click Email report.
Gong sends the report to your email as a CSV file. It can take a few minutes to arrive.
API / MCP usage & rate limit fields
Each row covers one hour of calls to one API endpoint or MCP tool, from one caller, for one team member.
Column name | Description |
|---|---|
Hour | The start of the hour the row covers, in UTC. For example, 2026-06-14 09:00 covers 09:00 to 10:00 UTC. |
Domain | Whether the calls came through the API or MCP. |
Endpoint / tool | The endpoint path for API calls, or the tool name for MCP calls. |
Integration / key ID | The ID of the integration or API key that made the calls. The report never shows the key's secret. |
User ID | The team member the calls were made for. This is blank when no team member applies, such as calls made with a standalone API key. |
Calls succeeded | The number of calls that went through. |
Calls failed | The number of calls rejected because they went over a rate limit. |
Calls total | Calls succeeded plus Calls failed. |
Note:
The data refreshes every hour, so the most recent hour can be missing or incomplete.
Find the cause of a rate limit event
Use the hourly rows to see when calls started failing and which caller made them. Start with the Calls failed column, then compare the hours that have failures with the limit your company reached.
- Hours where nearly every call failed point to the daily limit.
- Hours with many successful calls and some failed calls point to the per-second limit.
To find who used the quota:
- Open the CSV file from the email in a spreadsheet.
- Filter the rows to the hours that have a Calls failed value above zero.
- Group the rows by Integration / key ID and User ID.
- Sort by Calls total to see the heaviest caller.
The heaviest caller is often not the one that received the failures.
Daily totals in the report might not match the moment you reached the limit. The daily limit is a rolling 24-hour period that starts with the first request after a period of no activity, not a calendar day. To see the period that applied, add up the hourly rows for the 24 hours before the event.
Frequently asked questions
The report didn't arrive. What should I check?
Check your spam folder first, then confirm the email address on your Gong account.
How can I change my limits?
Contact your Gong customer success representative or Gong Support to request a limit change. The report shows usage only and can't change your limits.