Jakub Stefaniak

Here is a test. Without opening any tools, can you answer these three questions about your Salesforce org? Which connected app made the most API calls last week? Is any integration still running on an API version Salesforce plans to retire? Did anything unusual happen with your API traffic over the weekend? If you answered “I’d need to check” to all three — welcome to the majority. Most admins know their org’s API usage as a single number on System Overview.

In my sister article, An Admin’s Guide to Better Salesforce API Usage Monitoring, we covered the foundations of API monitoring – understanding your limits, setting up notifications, reading event logs, and building governance practices. That knowledge helps you answer “how much API capacity are we using?” It’s an important question, but not the only one that matters.

Salesforce API monitoring can feel like an afterthought – until something goes wrong. This article is a practical guide for admins who want to understand their org’s API usage, set up sensible alerts, and be ready to answer questions when traffic looks unusual. We will cover limits, native tools, governance practices, and the building blocks of deeper monitoring. Let us start with a scenario that might sound familiar. It is Monday, 08:12.