Tiendanube Rate Limits
Tiendanube (Nuvemshop) enforces rate limits per app+store combination using a leaky-bucket algorithm. Each app has a bucket per store that holds a fixed number of request tokens and refills (leaks) at a steady rate. Every API call consumes one token; when the bucket is empty, requests are rejected with HTTP 429 until the bucket refills. The current fill state is surfaced on every response through rate-limit headers so clients can pace themselves. Exact bucket size and leak rate are set by the platform and may differ by app and plan; specific numeric values are not reconciled in this artifact.
Tiendanube Rate Limits is the machine-readable rate-limit profile for Tiendanube on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring requests and requests_per_second.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include E-commerce, Retail, Latin America, Storefront, and Rate Limiting.
Limits
Policies
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/tiendanube-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.