Some of the best practices that you can follow to use APIs effectively

1. Fetch data based on your configured polling frequency. For example, if you want to fetch the log reports for a monitor with a polling frequency of 5 minutes, use /reports/log_reports/(\d+) at an interval of 5 minutes only to view any changes.
   
2. If you wish to get the status of more than a single monitor, use /current_status to fetch data for your entire account, /current_status/group/(\d+) for a monitor group, or /current_status/type/(\S+) for a monitor type, instead of /current_status/(\d+) for a single monitor.
   
3. Call the API /monitors (for an entire account) or /monitors/(\d+) (for a single monitor) only when you have made any configuration changes to your monitors. In case there are no changes made, it is recommended to cache the data at your end. 
   
4. For the availability/performance reports, use /reports/availability_summary/group/(\d+) or /reports/performance/group/(\d+) to fetch the reports for an entire monitor group, instead of making an API call for every monitor /reports/availability_summary/(\d+) or /reports/performance/(\d+).
   
   Also, you can use the light-weight basic availability APIs for a leaner reporting experience, simpler and faster data fetching.
   
5. For fetching the performance reports of monitor groups, it is recommended to call the API on a hourly basis, as the data archiving is done only once in 60 minutes.
   

Follow our community post for instant updates on this topic.

API calls for a Business Unit account is applied at the account level in Site24x7. Learn more.

Related article