Developer guide

API rate limits

Understand AutoPostcode API rate limits. How limits are applied, how to handle 429 responses with backoff, and how to cache lookups to stay within quota.

No card required · Royal Mail PAF-verified data

Trusted UK address intelligence

31M+
UK addresses
1.8M
Postcodes
99.9%
Uptime
PAF-verified address lookup
Fast REST API & no-code plugins
GDPR-friendly, UK-hosted

Rate limits keep the API fast and fair for everyone. Build your integration to respect them gracefully.

Staying within quota

  • Debounce postcode inputs so you only call on meaningful changes
  • Cache repeat lookups for the same postcode
  • Honour the retry interval on a 429 response with exponential backoff
  • Queue or batch non-urgent verification jobs

Need more?

Higher volumes are available on larger plans. For pattern details, see error handling.

Next steps

Review authentication & keys and the REST API reference.

Frequently asked questions

What are the API rate limits?

Limits depend on your plan and protect service quality. When you exceed them, the API returns a 429 response with headers indicating when to retry.

How should I handle a 429?

Back off and retry after the indicated interval, queue non-urgent requests, and cache repeat postcode lookups to reduce volume.

Can I increase my limits?

Yes — upgrade your plan or contact us for higher-volume needs.

Ready to get started?

Add Royal Mail PAF-verified UK address lookup to your site in minutes — start free, no card required.