specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: BrowserStack
providerId: browserstack
created: '2026-05-04'
modified: '2026-09-04'
generated: '2026-09-04'
method: searched
source: >-
  BrowserStack product API reference pages, fetched 2026-09-04. Every limit below is quoted
  from the provider's own documentation.
note: >-
  This file REPLACES a 2026-05-04 bulk-sweep scaffold that carried invented free/professional/
  enterprise tiers, invented X-RateLimit-* headers and an invented monthly quota. BrowserStack
  does not tier its API rate limits by plan and does not document any RateLimit-* or
  Retry-After response header — the only runtime signal it documents is the 429 status code.
  That absence is itself the finding: an agent hitting a BrowserStack limit learns nothing
  from the response about when it may retry, and must fall back to the fixed windows stated
  in the docs.
description: >-
  Published rate limits for the BrowserStack API surface, per product API. Limits are stated
  per user, per IP address, or per group depending on the product; there is no plan-tiered
  rate limiting in the published documentation.
headers:
  limit: null
  remaining: null
  reset: null
  retryAfter: null
  policy: null
  note: >-
    No rate-limit response headers are documented on any BrowserStack product API reference
    page. Checked: Automate, App Automate, Test Management and User Management introductions.
responseCodes:
  throttled: 429
limit_count: 6
limits:
  - name: Automate API — per user
    api: BrowserStack Automate API
    scope: per-user
    metric: requests
    limit: 1600
    timeFrame: 5 minutes
    source: https://www.browserstack.com/docs/automate/api-reference/selenium/introduction
    quote: 1600 API requests per 5 minutes per user.
  - name: Automate API — per IP address
    api: BrowserStack Automate API
    scope: per-ip
    metric: requests_per_second
    limit: 160
    timeFrame: second
    source: https://www.browserstack.com/docs/automate/api-reference/selenium/introduction
    quote: 160 API requests per second per IP address.
  - name: App Automate API — per user
    api: BrowserStack App Automate API
    scope: per-user
    metric: requests_per_second
    limit: 90
    timeFrame: second
    source: https://www.browserstack.com/docs/app-automate/api-reference/introduction
    quote: APIs - 90 requests/second per user.
  - name: App Automate — app and test-suite uploads
    api: BrowserStack App Automate API
    scope: per-user
    metric: requests
    limit: 5
    timeFrame: minute
    source: https://www.browserstack.com/docs/app-automate/api-reference/introduction
    quote: App/Test suite Uploads - 5 requests/per minute per user.
    note: Upload endpoints are limited far more tightly than read endpoints — 5/minute against
      90/second.
  - name: Test Management API — per group
    api: BrowserStack Test Management API
    scope: per-group
    metric: requests
    limit: 300
    timeFrame: minute
    source: https://www.browserstack.com/docs/test-management/api-reference/rate-limit-for-api-calls
    quote: All of the API requests have a rate limit of 300 requests per minute. Rate limits
      apply to each group.
    recovery: >-
      The docs state the window is shared across the whole group and recovers pro rata — a
      second user in the same group who calls 33 seconds after the first user was throttled
      must wait the remaining 27 seconds. There is no header carrying that remaining time.
  - name: User Management API — per group, with burst
    api: BrowserStack User Management API
    scope: per-group
    metric: requests
    limit: 15
    burst: 5
    timeFrame: minute
    source: https://www.browserstack.com/docs/enterprise/api-reference/introduction
    quote: You can make up to 5 requests in an initial burst, followed by 15 requests per
      minute. This is equivalent to one request every 4 seconds.
policies:
  - name: Exhaustion response
    description: All documented limits return HTTP 429 Too Many Requests on exhaustion.
  - name: Recovery
    description: >-
      Test Management documents a fixed 60-second wait after a 429. No other product API
      documents a recovery interval, and none returns Retry-After.
  - name: Undocumented surfaces
    description: >-
      The Accessibility Testing, Percy, Test Reporting and Analytics, Screenshots, App Live,
      Local Testing, Automate TurboScale and Low Code Automation API references do not publish
      rate limits. Their limits are unknown, not absent.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com
  - name: BrowserStack
    email: support@browserstack.com
    url: https://www.browserstack.com