All docs pages (49)

API Dashboard

See your org's API limits, the Salesforce API calls the extension made with the query or error behind each, and which client apps used the API most.

Updated 2026-11-09

API Dashboard shows how close the org is to its API limits, next to a log of the calls SFDC Police itself made. Open Develop → API Dashboard.

How to use it

  1. Open the page. It loads on its own and keeps itself up to date while the tab is open. Refresh reads everything now.
  2. Under Org API Limits, click Show All N Limits to see every limit the org reports, with a search box. Collapse hides it again.
  3. Under Recent Calls, type in Search endpoint, query or error... to find a call. Copy copies a query's SOQL.

What you see

Summary cards about the extension's own calls: Total Calls, Cache Hit Rate, Avg Duration, Error Rate, and, when known, SF API Limit (used and total, from the usage header Salesforce sends back on API responses for the org you are connected to). A banner appears when that usage passes 80% or 90%.

Limit Forecast. When the org's Daily API Requests limit is known and the extension has made calls in the last 24 hours, it shows roughly how long until the daily limit runs out, a 24h projection percentage, and a trend (Rising, Declining or Stable). The rate is a weighted average of the extension's calls over the last six hours, the latest hour weighted highest.

24-Hour Call Volume. A line chart of the extension's calls per hour.

Org API Limits. Bars for seven limits, when the org reports them: Daily API Requests, Daily Bulk API Requests, Concurrent Long Transactions, Daily Async Apex, Hourly Dashboard Results, Hourly OData Callouts and Streaming API Clients. Each shows used, maximum and percent; amber above 70%, red above 90%. The full table lists every limit with Used, Max, Remaining and Usage, highest usage first.

Calls by Endpoint lists the 15 endpoints the extension called most. Calls by Source appears when more than one module made calls.

Cache Performance shows Hits, Misses, Entries and Hit Rate. A hit is a read answered from the extension's cache without calling Salesforce.

Top API Consumers. The ten client IDs with the most API requests in the org's API event log files. The panel notes this data can be up to 24 hours old.

Recent Calls. The latest 50 calls the extension made, newest first: Time, Method, Request (the endpoint, the SOQL of a query, and Salesforce's error text when a call failed), Status, Duration, Source and Cached.

What it reads and writes

  • The org's limits from the REST /limits resource: about once a minute while the numbers move, slowing to every five minutes when they don't.
  • For Top API Consumers: up to five Event Log Files of type API from the last day, downloaded and counted by client ID. This starts every 5 minutes and slows to every 30.
  • Everything else comes from the extension's own record of its calls, which needs no Salesforce call.

It changes nothing in the org. No Salesforce reads run while the tab is hidden, and reading stops after a limit, session or permission error until you click Refresh or Retry.

Limits

  • The call log, the forecast and the call volume chart cover only SFDC Police's own calls, not traffic from other apps and integrations. The org-wide picture is the limits panel and the SF API Limit card.
  • The call log keeps up to 1,000 calls in memory and saves the latest 500 for the browser session; calls older than 24 hours are dropped when the extension restarts. Calls to every org you used are counted together.
  • The forecast counts calls answered from the cache too, so it can overstate how fast the limit is being used.
  • Top API Consumers needs Event Monitoring. If the query for the log files fails for any reason, the panel shows Requires Event Monitoring license (Shield or add-on), so that message does not prove a license is missing.
  • The reads of /limits and the event log files are API calls too; they appear in the call log under the source api-dashboard.