Launch27 · Rate Limits

Launch27 Rate Limits

Launch27 documents a token-bucket rate limiter applied per client IP address, with read requests and write requests limited separately. The current limits are echoed back in response headers on every call, rather than only published as static numbers in the docs - the documented example values are a sustained rate of roughly 2 requests/second for both reads and writes, with burst allowances of 30 (read) and 10 (write) requests.

Launch27 Rate Limits is the machine-readable rate-limit profile for Launch27 on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests and failed_attempts.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Field Service Management, Cleaning Services, Booking, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Field Service ManagementCleaning ServicesBookingRate LimitingQuotas

Limits

Read Requests client_ip
requests
30 burst, ~2/sec sustained (documented example: x-rate-limit-read-limit=30, ttl=500ms)
Applies to GET endpoints; returned live in x-rate-limit-read-* response headers.
Write Requests client_ip
requests
10 burst, ~2/sec sustained (documented example: x-rate-limit-write-limit=10, ttl=500ms)
Applies to POST/PUT/DELETE endpoints; returned live in x-rate-limit-write-* response headers.
Login Lockout account
failed_attempts
5 invalid attempts within 1 minute
Triggers a 403 Forbidden account lockout for 5 minutes. Already-logged-in users are unaffected until logout.

Policies

Token Bucket
Limiter is described as a token bucket (https://en.wikipedia.org/wiki/Token_bucket); actual sustained throughput depends on recent request activity, not just the burst number.
Per-IP Scope
Documented limits are applied per client IP address, not per account or API token.
Header-Reported Limits
Every response carries the current effective limit and TTL in x-rate-limit-read-limit / x-rate-limit-read-ttl / x-rate-limit-write-limit / x-rate-limit-write-ttl headers, so clients can read actual limits live rather than relying solely on documentation.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/launch27-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.