Overview
While ButterCMS doesn’t provide dedicated bulk endpoints, you can perform efficient bulk operations by orchestrating multiple Write API calls. This guide covers patterns and best practices for bulk content operations.Key Considerations
- Request Pacing: Add small delays between requests to keep bulk operations stable and reduce monthly usage spikes.
- Error Handling: Implement retry logic for transient failures.
- Progress Tracking: Track successful and failed operations for large imports.
- Async Nature: Write operations return
202 Accepted—content typically appears within seconds but processing time may vary.
Bulk Create Pattern
Sequential Creation with Request Pacing
Parallel Creation with Concurrency Control
For faster bulk operations, use controlled concurrency:Bulk Update Pattern
Update Multiple Items by ID
Bulk Status Update
Bulk Delete Pattern
Content Migration Example
WordPress to ButterCMS Migration
Handling 429 Responses
Progress Tracking and Logging
Best Practices
Request Pacing
Add 200-500ms delay between requests to keep bulk operations stable and reduce monthly API usage spikes.
Idempotency
Check if content exists before creating to avoid duplicates during retries.
Error Logging
Log failed operations for manual review and retry.
Batch Verification
After bulk operations, verify content via Read API.
Recommended Limits
These are recommended values to keep bulk operations stable. Free/Trial accounts can be blocked when monthly API call limits are exceeded.
Next Steps
Pages - Write
Create and update pages
Collections - Write
Create collection items
Blog Posts - Write
Create blog posts
Rate Limits
API rate limiting