socket.help

Rate-limit simulator

Test retry and backoff behavior against quotas.

Expires after 1 hour

Checking this session…

Import / export configuration
Request conditions & response templates

Templates accept {{path.id}}, {{query.name}} and {{body.name}} inside JSON strings or plain text. Missing values become empty strings. No code runs. Test credentials are stored in the configuration; use fake tokens only.

Up to 20 routes, 80 KiB total configuration, and 120 requests per minute. Paths support parameters such as /users/:id. Matching routes are checked in order.

Open an existing mock API
Guide & examples

About Rate-limit simulator

Create an endpoint with a shared, configurable requests-per-minute quota for testing retry and backoff.

When to use it

Create an endpoint with a shared, configurable requests-per-minute quota for testing retry and backoff.

Rate-limit simulator example
Two allowed requests → HTTP 429 with Retry-After

How to use it

  1. Configure the endpoint and choose private or public access.
  2. Create it and send requests from your client.
  3. Inspect test output, update or delete the resource when finished.

Limits & privacy

Uses an expiring mock resource, private by default, with separate management and access credentials. Public access is optional. Standard resource quotas, ownership, renewal and deletion apply. Private access tokens are sent in headers, never in share URLs. Each route allows 1–120 requests per minute. A fixed window starts with its first counted request. Private access is checked before the configured quota is consumed. The general 120/minute mock limit also applies.

Use this tool from the API reference or connect through the SDK, CLI, SSH, or MCP. Hosted calls share your plan allowances.