Brushfire · Rate Limits

Brushfire Rate Limits

The Brushfire API enforces rate limiting and returns HTTP 429 Too Many Requests when a caller exceeds the allowed number of requests. The developer portal instructs callers to read the X-Rate-Limit-Limit, X-Rate-Limit-Remaining, and X-Rate-Limit-Reset response headers (and the response body) before retrying. The specific numeric request quota per App Key is not published; the mechanism and headers are documented but the exact ceiling is disclosed only through the live headers on your own account.

Brushfire Rate Limits is the machine-readable rate-limit profile for Brushfire on the APIs.io network, in the API Commons Rate Limits shape.

It captures 1 rate-limit definition, measuring requests.

Limit state is signalled in the X-Rate-Limit-Limit, X-Rate-Limit-Remaining, and X-Rate-Limit-Reset response headers, and an exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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

Tagged areas include Event Ticketing, Registration, Rate Limiting, and Quotas.

1 Limits Exhausted: HTTP 429 X-Rate-Limit-LimitX-Rate-Limit-RemainingX-Rate-Limit-Reset
Method: generated, dated 2026-07-05.
Written by API Evangelist on 2026-07-05 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Event TicketingRegistrationRate LimitingQuotas

Limits

API Requests appKey
requests
not published (surfaced via X-Rate-Limit-* headers)
Exceeding the allowance returns 429 Too Many Requests. Read X-Rate-Limit-Limit, X-Rate-Limit-Remaining, and X-Rate-Limit-Reset to observe the live ceiling and reset window for your App Key.

Policies

Versioning
Requests must specify an API version via the api-version request header (for example, 2025-07-22); a missing version returns 412 Precondition Failed.
Backoff Strategy
On a 429 response, stop issuing requests until X-Rate-Limit-Reset, and apply exponential backoff with jitter rather than retrying immediately.
Authentication
Every request must include the App Key in the Authorization header; unauthenticated requests are rejected before rate-limit accounting applies.

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/brushfire-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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