How to Guide Salesforce API Usage Reporting at Scale

1. Manual, Salesforce-native ways to build API usage reports

If you are just starting, you can get surprisingly far using what Salesforce already gives you. The tradeoff: lots of clicks and almost no automation.

Method 1: System Overview (last 24 hours)

1. Log in to Salesforce as an admin.
2. In Lightning, click the gear icon → Setup.
3. In the Quick Find box, type System Overview.
4. Open System Overview and look for API Usage; Salesforce shows your calls in the last 24 hours and a percentage of your Daily API Request Limit.
5. Screenshot or copy the numbers into a spreadsheet to trend them day by day.

Reference: Salesforce docs on limits: https://developer.salesforce.com/docs/atlas.en-us.salesforce_app_limits_cheatsheet.meta/salesforce_app_limits_cheatsheet/salesforce_app_limits_platform_api.htm

Pros: Zero configuration, great for quick health checks.
Cons: No history beyond 24 hours unless you manually copy the data out.

Method 2: Company Information (24-hour and 30-day view)

1. From Setup, search for Company Information.
2. Under Organization Detail, find API Requests, Last 24 Hours. This shows usage vs. your documented Daily API Request Limit.
3. Scroll to Usage-based Entitlements and find API Request Limit per Month to see a 30‑day aggregate.
4. Manually export these numbers weekly into Excel or Google Sheets to visualize trends.

Reference: https://help.salesforce.com/s/articleView?id=sf.company_information.htm&type=5

Pros: Combines daily and monthly perspective; good for forecasting.
Cons: Still manual; no breakdown by app or user.

Method 3: Classic report “API Usage in the Last 7 Days”

1. Temporarily switch to Salesforce Classic (click your avatar → Switch to Salesforce Classic).
2. Go to Reports → Administrative Reports.
3. Open API Usage in the Last 7 Days.
4. Filter by date, user, or profile to see which integration users are consuming the most calls.
5. Export the report to CSV and analyze in a BI or spreadsheet tool.

Guide: https://help.salesforce.com/s/articleView?id=000337767&type=1

Pros: Near real-time 7‑day view; decent attribution to users.
Cons: Classic-only; user-based, not app-based; still not automated.

Method 4: REST API Limits resource for programmatic checks
If you have a technical teammate or a small script:

1. Create a Connected App and get OAuth credentials.
2. Use the REST Limits endpoint:
   GET https://<your-domain>.my.salesforce.com/services/data/vXX.0/limits
3. Inspect the DailyApiRequests object for Max and Remaining.
4. Log the values every hour into a database or even a Google Sheet via script.

Docs: https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_limits.htm

Pros: Accurate, machine-readable metrics; a foundation for automation.
Cons: Requires scripting; still no deep breakdown by app.

Method 5: Event Log Files for detailed per-request data

1. Ensure Event Monitoring is enabled (Enterprise+; some events are free, others are add-ons).
2. Open Event Log File Browser in Setup or via: https://help.salesforce.com/s/articleView?id=sf.real_time_em_elf_browser.htm&type=5
3. Filter for API Total Usage logs.
4. Download CSV files for the desired date range.
5. Analyze columns like CLIENT_ID, API_TYPE, and URI to see which integrations and endpoints are most expensive.

Docs: https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_eventlogfile_apitotalusage.htm

Pros: Deep forensic visibility; you can slice by app, user, IP.
Cons: Heavy CSV wrangling; not friendly for non-technical users.

2. No-code automation methods

Once you know where to find the data, the next step is to stop doing it manually. Without writing code, you can lean on automation platforms.

No-code Method 1: Scheduled CSV processing with a data tool
Scenario: You download API Total Usage logs weekly and want a clean dashboard.

1. Store your downloaded CSVs in a shared folder (Google Drive, OneDrive, Dropbox).
2. Use a no-code ETL/automation tool (e.g., Zapier, Make, or Power Automate) to watch that folder.
3. When a new CSV appears, the flow parses rows and loads them into a central table (Airtable, Notion database, or a Salesforce custom object like API_Usage__c).
4. Build a simple chart view grouped by date and integration user.
5. Schedule a weekly email from the tool summarizing key stats: total calls, top 5 users, week-over-week change.

Pros: Point-and-click setup; business users can own the dashboard.
Cons: Still depends on you downloading the CSVs unless you also script that piece.

No-code Method 2: REST Limits endpoint via automation
You can wrap the REST /limits call inside a no-code integration.

1. In your tool (e.g., Make), create a scheduled scenario that runs every hour.
2. Add an HTTP module configured to call the Salesforce Limits REST resource using an OAuth connection.
3. Parse the JSON response, focusing on DailyApiRequests.Max and DailyApiRequests.Remaining.
4. Write those values into a Google Sheet or Airtable.
5. Add a conditional step: if Remaining / Max < 0.2, send a Slack or email alert.

Docs for the Limits resource: https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_limits.htm

Pros: Fully automated alerting; no dev needed.
Cons: Limited to high-level metrics; still no detailed attribution.

No-code Method 3: Native Salesforce notifications
Salesforce can email you when API usage crosses a threshold.

1. In Setup, search for API Usage Notifications.
2. Create rules such as:
   • 50% of limit in 24 hours (daily digest).
   • 80% in the last 4 hours.
   • 90% in the last hour.
3. Point notifications to an ops shared inbox or Slack email gateway.

Docs: https://help.salesforce.com/s/articleView?id=sf.monitor_rate_limit.htm&type=5

Pros: Built-in, fast to configure.
Cons: Alerts tell you that you have a problem, not why.

3. Scaling with an AI agent (Simular) doing the work

Manual and no-code methods still depend on you wiring pieces together. A Simular AI computer agent can behave like a power user who sits at the keyboard and runs the entire reporting workflow end to end.

AI Agent Method 1: Autonomous weekly API forensic report

Story: Every Friday at 6pm, your Simular agent wakes up on a Mac, logs into Salesforce, pulls logs, analyzes them, and drops a narrative into Slack.

Concrete steps the agent can perform:

1. Open Salesforce in the browser, navigate to System Overview and Company Information, and capture key limit stats.
2. Launch the Event Log File Browser, filter API Total Usage, and download the latest CSV.
3. Open the CSV locally, filter/sort by CLIENT_ID and USER_ID to find the top 10 integrations by volume.
4. Paste summarized metrics into a Google Sheet, updating trend charts.
5. Draft a human-readable summary: “HubSpot and custom middleware drove 72% of calls; weekend traffic spiked 40% due to campaign X; projection says we’ll hit 95% of our daily limit by Thursday if nothing changes.”
6. Post the sheet and summary to your sales ops Slack channel.

Pros: Truly hands-off; combines data gathering, analysis, and storytelling.
Cons: Requires clear onboarding instructions and initial monitoring to ensure it behaves exactly as you expect.

Learn more about the agent’s capabilities: https://www.simular.ai/simular-pro

AI Agent Method 2: Real-time guardrail during big launches

Before a high-volume integration goes live, you can instruct a Simular agent to act as your “API limit sentry.”

1. Configure the agent to run every 15–30 minutes.
2. It calls the Salesforce REST Limits endpoint in a browser or API client, logs Max vs Remaining into a sheet, and calculates burn rate.
3. When remaining calls drop below a threshold, the agent:
   • Sends a structured email to your engineering and RevOps lists.
   • Posts a message in Slack with suggested actions (pause a specific integration, throttle a sync, or temporarily buy additional calls).

Pros: You get proactive, context-rich alerts instead of raw numbers.
Cons: Needs careful testing so it doesn’t over-alert or miss edge cases.

AI Agent Method 3: Continuous governance workbook

Over time, governance matters more than one-off reports. A Simular agent can maintain a living workbook of every integration and its typical Salesforce API footprint.

1. On a weekly cadence, the agent downloads API Total Usage logs.
2. It groups usage by integration users, maps them to documented apps (from a simple “Integration Catalog” sheet you maintain), and updates a central “API Governance” spreadsheet.
3. It highlights anomalies: new client IDs, apps using deprecated API versions, or sudden spikes compared to the 4-week baseline.
4. The agent then drafts a short action list for the week: “Review AppExchange package X (API v51) – still active; consider upgrade before v51 retirement.”

Pros: Turns raw logs into an ongoing asset for security, compliance, and capacity planning.
Cons: Requires an upfront investment in defining your integration catalog and acceptance criteria.

You can see how Simular agents handle long, multi-step workflows across desktop, browser, and cloud apps here: https://www.simular.ai/simular-pro