Tamara · Rate Limits

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, in the API Commons Rate Limits shape.

It captures 3 rate-limit definitions, measuring requests.

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 Fintech, BNPL, Payments, Rate Limiting, and Throttling.

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

Limits

Default Merchant API merchant
requests
not publicly documented
Tamara's docs do not publish a numeric per-second/per-minute quota; traffic is bounded by retail purchase volume.
Sandbox merchant
requests
sandbox shared environment
Sandbox at api-sandbox.tamara.co is shared infrastructure intended for integration testing, not load testing.
Channel Partner API channel_partner
requests
not publicly documented
Numeric quotas for partner-api.tamara.co are negotiated as part of the channel partner agreement.

Policies

Idempotency
Re-issuing a `POST /orders/{order_id}/authorise` after a non-2xx response is unsafe — Tamara instructs merchants to verify order status via Get Order Details before retrying, and to not retry on Expired or Declined.
Webhook Retries
Tamara webhooks expect a 2xx response from the merchant endpoint quickly; non-2xx will be retried.
Backoff
Clients should implement exponential backoff with jitter on 429 and 5xx responses.

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