> For the complete documentation index, see [llms.txt](https://biztech.gitbook.io/webapi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://biztech.gitbook.io/webapi/api/api-rate-limit.md).

# API Rate Limit

### Parameter Description

<table data-header-hidden><thead><tr><th width="150" align="center"></th><th width="593.3333333333333"></th></tr></thead><tbody><tr><td align="center"><strong>설명</strong> </td><td><ul><li>Rate Limit란 특정한 시간 내에 호출할 수 있는 API 요청 횟수를 의미합니다.<br></li><li>클라이언트의 API 요청 횟수가 제한 값을 초과하면 HTTP 429 코드를 반환하며 요청이 실패합니다.<br></li><li>클라이언트에서 API Rate Limit를 고려해 적절하게 처리하지 않으면 <br>의도하지 않은 오류가 발생할 수 있습니다. <br>특히, 재시도하는 로직이 있는 경우 재시도 간격을 충분히 늘려 제한 값에 <br>도달하지 않도록 주의해야 합니다.<br></li></ul><p>  * API 요청 횟수는 모든 API 요청 횟수를 포함 <br>    (토큰 발급, 메시지 발송, 리포트 요청 등)</p></td></tr></tbody></table>

### **Response**

**Headers**

```
HTTP/1.1 429 Too Many Requests
Content-type: application/json
RateLimit-Limit: 1000
RateLimit-Remaining: 0
RateLimit-Reset: 0.299
```

<figure><img src="/files/AIlK0PwByT5es1XLmPCY" alt=""><figcaption></figcaption></figure>

**Body**

```json5
{
"code": 5002,
"description": "too many requests",
"refkey": " test1234"
}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://biztech.gitbook.io/webapi/api/api-rate-limit.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.