marketplace-rate-limiting

Implement rate-limit resilience for VTEX marketplace API calls with exponential backoff and Retry-After handling.

Updated Mar 27, 2026

Search Tags:#rate limiting #circuit breaker #exponential backoff #retry strategy #vtex #request queue #429 handling

Ready to run

npx skills add https://github.com/exilonX/ap2 --skill marketplace-rate-limiting-exilonx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: marketplace-rate-limiting
Source: https://github.com/exilonX/ap2/tree/main/.agents/skills/marketplace-rate-limiting
Command: npx skills add https://github.com/exilonX/ap2 --skill marketplace-rate-limiting-exilonx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents VTEX API integrations from failing or slowing down when the marketplace throttles requests, especially during bursts that cause 429 responses.

Core Features & Use Cases

Exponential Backoff with Jitter for 429: Replaces immediate retries with randomized exponential delays to avoid retry storms and burst-credit drain.
Retry-After Respect & Header-Aware Delays: Ensures the retry wait uses the server-provided Retry-After value (and the maximum of it vs calculated backoff).
Resilience Patterns for High Availability: Adds circuit breakers, request queues, and proactive monitoring of X-RateLimit-Remaining and X-RateLimit-Reset to throttle before the platform blocks you.

Quick Start

Use the marketplace-rate-limiting skill to add rate-limit-aware retry and backpressure to your VTEX calls so 429 responses trigger exponential backoff with jitter while honoring the Retry-After header.

Frequently Asked Questions about marketplace-rate-limiting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I handle VTEX API 429 throttling errors during catalog sync?▼

Handle VTEX API 429 throttling errors by implementing exponential backoff with jitter and respecting the Retry-After header. This prevents retry storms during burst traffic catalog syncs, ensuring requests queue safely without draining burst credits.

What is exponential backoff with jitter for rate limiting?▼

Exponential backoff with jitter for rate limiting replaces immediate retries with randomized exponential delays. This mechanism avoids retry storms and burst-credit drain when a marketplace API throttles requests and returns 429 responses.

How do I use Retry-After and X-RateLimit headers for VTEX request queues?▼

Use Retry-After and X-RateLimit headers for VTEX request queues by enforcing wait times based on the maximum of the server-provided value versus calculated backoff. Monitor X-RateLimit-Remaining and X-RateLimit-Reset to proactively throttle traffic.

Can I add a circuit breaker to prevent VTEX marketplace API downtime?▼

Yes, you can add a circuit breaker to prevent VTEX marketplace API downtime. Circuit breakers, combined with request queues and header-aware delays, provide high availability resilience patterns during burst traffic and throttling.

Does this rate limiting approach work for order processing and fulfillment operations?▼

Yes, this rate limiting approach works for order processing and fulfillment operations. The retry behavior and backpressure mechanisms apply to any VTEX marketplace API calls reacting to 429 responses, including price, inventory, and fulfillment updates.

Why are my immediate VTEX API retries causing retry storms under throttling?▼

Immediate VTEX API retries cause retry storms under throttling because they rapidly drain burst credits and trigger further 429 responses. Applying randomized exponential backoff with jitter avoids tight retry loops and stabilizes request throughput.