Gelato Collection Creator Limits & API Constraints
Understand Gelato's API rate limits and constraints to optimize your Collection Creator workflow.
Gelato enforces rate limits to ensure stable API performance. The limits vary by endpoint type and your account tier.
~100 Requests Per Minute
General rate limit for most API endpoints. Baseline threshold for consistent performance.
Higher Limits for Some Endpoints
Certain endpoints (like price lookups) may have higher individual limits depending on account tier.
Daily Caps Based on Plan
Daily request limits vary by your subscription tier and account type.
Typical: 2-3 API Calls Per Product
Creating a single Gelato product requires fewer API calls than Printify, thanks to Gelato's streamlined architecture:
- • Template Fetch: ~1 call to retrieve template and product details
- • Product Creation: ~1-2 calls to create the product and set up variants
Lower API footprint than Printify:
Gelato: 2-3 calls/product
Printify: 3-4 calls/product
This means you can safely create more products within rate limits.
Maximum 10 Products Per Collection (Recommended)
Based on Gelato's ~100 requests/minute rate limit and 2-3 API calls per product:
100 API calls/min ÷ 2.5 avg calls/product = 40 products/min safely
Recommended per collection: 10 products
Actual throughput: 20-30 API calls (well under 100/min limit)
Safety margin: Uses only 20-30% of available requests
✓ Gelato is more forgiving than Printify: You can safely exceed 10 products per collection if needed, but 10 is a conservative recommendation that works well across both Printify and Gelato.
Your plan determines how many collections you can create per action:
1 Collection Per Action
1 collection × 10 templates = 10 products maximum
2-5 Collections Per Action
Multiple collections × 10 templates each = up to 50 products
5 Collections Per Action
5 collections × 10 templates = up to 50 products per batch
Starter Plan
1 collection × 10 templates = 10 products
Uses 20-30 API calls (well under 100/min)
Advanced Plan
3 collections × 10 templates = 30 products total
Uses 60-90 API calls (very safe, leaves plenty of headroom)
Pro Plan
5 collections × 10 templates = 50 products total
Uses 100-150 API calls (slightly aggressive, may hit rate limit)
Recommendation: Use 5-8 templates per collection or spread across separate batches
If your job hits Gelato's rate limit, the Collection Creator will handle it gracefully:
- Job Pauses Automatically — Your job will pause and you'll get a notification.
- Wait for Rate Limit Reset — Gelato's per-minute limits reset after a short delay (~1 minute typically).
- Resume or Retry — You can manually resume, or enable "Auto Resume" to continue automatically when the limit resets.
- Progress is Saved — All completed products are preserved. The job continues from where it paused.
| Metric | Gelato | Printify |
|---|---|---|
| Rate Limit Window | Per minute (~100 req/min) | Per 30 minutes (~200 req/30min) |
| API Calls Per Product | 2-3 calls | 3-4 calls |
| Safe Products Per Collection | 10 products | 10 products |
| Throughput | Higher per minute | Higher per 30 min window |
| Difficulty | More forgiving for smaller batches | Stricter rate limit system |
Key insight: Gelato's per-minute limits are actually more lenient than Printify's per-30-minute window, especially for quick, focused batches. Both providers are safe at 10 products per collection.
- Start with 5-10 products per collection — this keeps you well under rate limits with good headroom
- Gelato is faster than Printify — you can often create multiple collections without hitting limits
- If you want to be ultra-conservative, spread batches over a few minutes to let per-minute counters reset
- Monitor your API usage in the Collection Creator UI to understand your typical consumption
- Enable "Auto Resume" if your job pauses — it will continue automatically when the rate limit resets