Microsoft Edge · Rate Limits
Microsoft Edge Rate Limits
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.
3 Limits
Throttle: 429
BrowserChromiumDeveloper ToolsEdgeExtensionsMicrosoftRate Limiting
Limits
Edge Add-ons publishing API partner-center-account
see Microsoft Partner Center fair-use policy
Edge DevTools Protocol HTTP API local-process
bounded by local host CPU (localhost-only debugger)
Edge Extensions / Web Platform APIs client
client-side; no server quota
Policies
Backoff Strategy
For the Add-ons publishing API, retry on 429 / 503 using exponential backoff and the Retry-After header when present.
Fair Use
Microsoft Partner Center applies fair-use throttling on the Add-ons publishing API; no per-second numbers are published.
Local Debugger
The DevTools Protocol HTTP API is intended for local debugging and is not a server-side quota-managed API.