Linnworks API rate limits: what triggers them and how to stop hitting them

Short answer: Linnworks rate-limits per account, not per app. Everything you have connected shares one budget — so the culprit is often a different tool than the one showing the error.

What a 429 means

Too many requests in a window. Well-built integrations back off and retry with increasing delays, so a single 429 usually self-heals within seconds and you never notice.

What causes sustained bursts

Full catalogue syncs, bulk price pushes, several integrations polling on the same schedule, and AI tools firing many parallel queries at once. Run big syncs outside trading hours where you can.

Practical fixes

Stagger scheduled jobs so they do not all fire on the hour. Prefer targeted queries over full syncs. If you use AI over Linnworks, ask narrower sequential questions rather than "summarise everything across orders, stock and POs" — see good question patterns.

If it is persistent

Audit what is connected — old integrations nobody uses still consume budget. If your genuine usage exceeds the limit, that is a conversation with Linnworks about your tier.

Questions, or want a tool we don't have yet? Email hello@grafto.co.uk — a real person replies.