---
title: "Rate limits"
description: "Per-partner request limits for read, search and write endpoints, and how to handle 429 responses."
url: "https://portal.konghotels.cloud/guides/rate-limits"
image: "https://portal.konghotels.cloud/_og/d/c_Ocean.takumi,title_Rate+limits,description_~UGVyLXBhcnRuZXIgcmVxdWVzdCBsaW1pdHMgZm9yIHJlYWQsIHNlYXJjaCBhbmQgd3JpdGUgZW5kcG9pbnRzLCBhbmQgaG93IHRvIGhhbmRsZSA0MjkgcmVzcG9uc2VzLg,props_eyJ0aGVtZSI6eyJtb2RlIjoibGlnaHQiLCJjb2xvcnMiOnsicHJpbWFyeSI6IiMwRTJBMUYifX19,p_Ii9ndWlkZXMvcmF0ZS1saW1pdHMi,s_-Yi1V_guMGiPqP6j.png"
---

# Rate limits

Limits apply per partner, per minute, in three buckets. Every response tells you where you stand.

## [Buckets](#buckets)

Limits apply per partner (or per client IP for anonymous requests) per minute:

| Bucket | Default | Endpoints                                                                   |
| :----- | :------ | :-------------------------------------------------------------------------- |
| read   | 300/min | Content, reservations and feeds: every GET except the ones below            |
| search | 120/min | /availability, /properties/{code}/availability, /properties/{code}/calendar |
| write  | 60/min  | Every POST, PATCH and DELETE                                                |

Contracted quotas enforced at Kong Gateway are separate from these limits.

## [Headers](#headers)

Every response carries the limit and what's left of it for that bucket:

```http
X-RateLimit-Limit: 300
X-RateLimit-Remaining: 298
```

## [When you hit a limit](#when-you-hit-a-limit)

You get `429` with problem type `rate-limited` and a `Retry-After` header in seconds. Wait that long before retrying.

Search less, sync more

Searches have the tightest limit. Instead of re-searching to keep prices fresh, use the [change feed or webhooks](https://portal.konghotels.cloud/guides/staying-in-sync) and only refresh rooms whose rates or availability changed.