To do so, from Setup, enter API Usage Notifications in the Quick Find box, then select API Usage Notifications.
You can also set up notifications for when your org exceeds a number of API calls that you designate.
Inside this zip file you can find the ant-salesforce.jar file and some sample configuration files. Total limits are also subject to minimums and maximums based on the org edition, but we won’t get into that here. Click the Migration Tool link to download a zip file. Total limits vary by org edition and license type, including any add-on licenses you purchase. Total limits cap the number of calls made within a rolling 24-hour period.
For example, trial orgs and production orgs have a different limit on concurrent requests. Concurrent limits cap the number of long-running calls that are running at one time. Timeout limits restrict the length of time a single call is allowed to run. There are three types of API limits: timeout limits, concurrent request limits, and total request allocations. Nonetheless, it’s a good idea to get familiar with them. They don’t get in the way of your everyday work. These limits exist to prevent rogue scripts from smashing our servers into driftwood. Similarly, Salesforce limits the number of API calls per org to ensure the health of the instance. If the captain lets the sailors drink coconut milk all day long, nothing gets done.