---
title: "API rate limit errors on bulk imports"
url: "https://demo.myforumcat.com/q/7/api-rate-limit-errors-on-bulk-imports"
forum: "Demo"
question_number: 7
category: "General"
tags: ["API", "Billing", "Webhooks"]
status: "solved"
solved: true
votes: 1
replies: 7
views: 282
asked_at: "2026-05-05T12:34:36.898Z"
updated_at: "2026-09-18T23:15:24.517Z"
---

# API rate limit errors on bulk imports

Asked by Margaret Doyle on 2026-05-05 · 1 vote

We are hitting 429 responses when importing more than 500 records in a single batch. Is there a documented rate limit we should design around?

## 7 replies

### Reply 1 (marked as the solution)

meow (Owner) · 2026-05-05 · 7 votes

The documented limit is 100 requests per minute per API key, and bulk imports count each record as its own request today. For anything over a few hundred records, batch them into chunks of 50 with a short delay between chunks, or reach out and we can raise your limit temporarily for a one-time migration.

### Reply 2

Jane Cooper · 2026-05-06 · 2 votes · In reply to Reply 1

Chunking into 50s fixed it for us too, thanks for the tip.

### Reply 3

Marcus Lee · 2026-05-07 · 1 vote

We ended up just queuing the import overnight when traffic is low, works fine as a stopgap.

### Reply 4

Jane Cooper · 2026-05-07 · 1 vote · In reply to Reply 1

One more thing, does the raised limit apply permanently or just for the one migration?

### Reply 5

meow (Owner) · 2026-05-08 · 3 votes · In reply to Reply 4

Just for the one-time migration window we agree on, your limit reverts to the standard 100 per minute afterward unless you ask us to keep it raised.

### Reply 6

Kai Tanaka · 2026-05-08 · 1 vote

Chunking helped us too, though we ended up going a bit smaller, batches of 25, to stay well under the limit with headroom.

### Reply 7

Laura Simmons · 2026-05-09 · 1 vote · In reply to Reply 6

Good tip, will try a smaller batch size if we hit this again.