Tamara Rate Limits
Tamara does not publish a per-merchant request-per-minute/quota table in its public documentation. The merchant integration is structured around customer-driven checkout events and merchant-driven order operations (authorise/capture/cancel/refund), so most traffic is naturally bounded by retail volume.
Tamara Rate Limits is the machine-readable rate-limit profile for Tamara on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring requests.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Fintech, BNPL, Payments, Rate Limiting, and Throttling.
Limits
Policies
Sources
- https://docs.tamara.co/
- https://docs.tamara.co/reference/tamara-api-reference-documentation
- https://docs.tamara.co/docs/online-go-live-testing-checklist
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/tamara-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.