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: Microsoft Edge
providerId: microsoft-edge
created: '2026-05-04'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-05'
reconciled: false
tags:
  - Browser
  - Chromium
  - Developer Tools
  - Edge
  - Extensions
  - Microsoft
  - Rate Limiting
description: Microsoft Edge's developer-facing APIs (Add-ons publishing API, DevTools Protocol HTTP API,
  Extensions API, Web Platform APIs) do not publish explicit numeric rate limits. The Add-ons publishing
  API uses Microsoft Partner Center which applies fair-use throttling. The DevTools Protocol HTTP API
  is a localhost-only debugger and is bounded by host CPU. Treat all limits as fair-use unless documented
  per-service.
sources:
  - https://learn.microsoft.com/en-us/microsoft-edge/extensions-chromium/publish/api/using-addons-api
  - https://learn.microsoft.com/en-us/microsoft-edge/devtools-protocol-chromium/
notes: No public per-second or per-minute rate-limit numbers are published for the Edge developer API
  surface. Values below are placeholders; treat as fair-use until Microsoft documents specific quotas.
responseCodes:
  throttled: 429
  serviceUnavailable: 503
limits:
  - name: Edge Add-ons publishing API
    scope: partner-center-account
    metric: varies
    limit: see Microsoft Partner Center fair-use policy
  - name: Edge DevTools Protocol HTTP API
    scope: local-process
    metric: varies
    limit: bounded by local host CPU (localhost-only debugger)
  - name: Edge Extensions / Web Platform APIs
    scope: client
    metric: varies
    limit: client-side; no server quota
policies:
  - name: Backoff Strategy
    description: For the Add-ons publishing API, retry on 429 / 503 using exponential backoff and the
      Retry-After header when present.
  - name: Fair Use
    description: Microsoft Partner Center applies fair-use throttling on the Add-ons publishing API; no
      per-second numbers are published.
  - name: Local Debugger
    description: The DevTools Protocol HTTP API is intended for local debugging and is not a server-side
      quota-managed API.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com