Nuvemshop / Tiendanube · Rate Limits

Nuvemshop Rate Limits

The Nuvemshop / Tiendanube Admin API is rate limited per store using a leaky bucket algorithm. Each store gets a bucket that holds a default of 40 requests and drains (leaks) at 2 requests per second. Stores on higher-tier plans (Next / Evolution) get the limit multiplied by 10 (a 400-request bucket draining at 20 requests/second). When the bucket is full, additional requests are rejected with HTTP 429. Every response carries rate-limit headers so clients can pace themselves.

Nuvemshop Rate Limits is the machine-readable rate-limit profile for Nuvemshop / Tiendanube on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests and requests_per_second.

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

Tagged areas include E-commerce, Latin America, Rate Limiting, Quotas, and Throttling.

4 Limits Throttle: 429
E-commerceLatin AmericaRate LimitingQuotasThrottlingLeaky Bucket

Limits

Default Bucket Size store
requests
40
Maximum number of requests the per-store bucket holds by default.
Default Leak Rate store
requests_per_second
2
The bucket drains at 2 requests per second, allowing sustained ~2 rps.
Higher-Tier Bucket Size store
requests
400
For stores on higher plan tiers (Next / Evolution), the limit is multiplied by 10.
Higher-Tier Leak Rate store
requests_per_second
20
Higher-tier stores drain at 20 requests per second.

Policies

Leaky Bucket
Each store has a bucket that fills with incoming requests and drains at a fixed rate; overflow returns 429.
Plan-Based Scaling
Higher commercial plan tiers receive a 10x larger bucket and leak rate.
Backoff Strategy
Clients should read x-rate-limit-remaining / x-rate-limit-reset and back off (exponential backoff with jitter) before the bucket overflows.

Sources