Puzzle · Rate Limits

Puzzle Rate Limits

Puzzle does not publish specific API rate-limit numbers in its public documentation. The API is a partner-gated, RESTful JSON interface issued through the Partner Program, and Puzzle advertises 99.9% API availability. Concrete request-per-minute, per-hour, or per-day limits are set per partner agreement during the technical review and are not documented publicly. Values below are placeholders describing the expected shape of Puzzle's throttling, not confirmed figures.

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

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

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 Accounting, Fintech, Rate Limiting, Quotas, and Throttling.

3 Limits Exhausted: HTTP 429
Method: generated, dated 2026-07-01.
Written by API Evangelist on 2026-07-01 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
AccountingFintechRate LimitingQuotasThrottling

Limits

Requests Per Minute (RPM) partner
requests
see partner agreement
Not published; set per partner during technical review.
Concurrent Requests partner
concurrent
see partner agreement
Not published; large-scale portfolio partners are provisioned for high volume.
Sync Frequency company
syncs
see partner agreement
Upstream connection sync cadence is managed by Puzzle, not exposed as a client-side limit.

Policies

Availability SLA
Puzzle advertises 99.9% API availability for the partner API.
Partner Provisioning
Limits are negotiated per partner rather than published as fixed public tiers.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on HTTP 429.

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/puzzle-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.