Skip to main content
Table of Contents

Usage Reports

Access Usage Reports using REST API to analyze how your team members are using BrowserStack

Usage Reports provide valuable insights into your BrowserStack utilization. They help you with the necessary information to make efficient decisions regarding the allocation and usage of parallel resources and user licenses among teams and individuals.

You can access usage reports on BrowserStack UI from Test Insights console:


Alternatively, if you prefer to automate the retrieval and consumption of Usage Reports, you can utilize the REST API endpoints. These endpoints offer the capability to retrieve the following reports related to your organization’s BrowserStack usage:

Note the owner has access to invoke any of these API for any member in their organization account on BrowserStack. However, if teams are created, then team admins can invoke these endpoints only for their respective team members.

What you need to do

Usage reports APIs use a shared job queue (for both User and Team reports) in order to generate the desired reports. To retrieve a report, you can follow these three simple steps:

  1. Begin by creating a job using one of the create-job endpoints. Upon job creation, you will receive a job_id in response (You can use this job_id to monitor its status, retrieve the generated report, or cancel the job).
  2. Once created, the jobs will be automatically enqueued and processed for report generation. You can check the status of a job using one of the get-job-status endpoints.
  3. Once a job moves to completed state, you can use the ‘get report’ end points to retrieve the generated reports.

Frequently asked questions

Q. Is there a time frame limit for which I can fetch Usage reports?

Q. Is there a restriction on the frequency of fetching Usage reports within a day?

Yes, there is. To prevent unintended misuse, the Usage Reports APIs have rate limits as outlined below:

Q. My queue is at capacity. How can I empty it to handle additional reports?

You can delete jobs that havev been scheduled to reduce the number of concurrent/ enquued jobs. To delete an existing job, simply pass the job_id to the corresponding delete-job endpoints.

We're sorry to hear that. Please share your feedback so we can do better

Contact our Support team for immediate help while we work on improving our docs.

We're continuously improving our docs. We'd love to know what you liked

Thank you for your valuable feedback