> For the complete documentation index, see [llms.txt](https://support.iafcertsearch.org/api-developer-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.iafcertsearch.org/api-developer-guide/api-ko/api-integration/responses.md).

# 응답

### Content-Type Header

모든 응답은 JSON 형식으로 반환됩니다. 이를 위해 `Content-Type` 헤더를 보냅니다.

### 상태 코드

아래는 현재 지원하는 다양한 자원에 대한 상태 코드에 대한 설명을 담고 있는 테이블입니다.

| 응답 코드 | 설명           |
| ----- | ------------ |
| 200   | OK           |
| 201   | 리소스 생성됨      |
| 202   | 접수된          |
| 400   | 잘못된 요청       |
| 401   | 인증되지 않음      |
| 404   | 리소스 찾을 수 없음  |
| 406   | 허용되지 않음      |
| 422   | 처리할 수 없는 엔티티 |
| 429   | 요청이 너무 많음    |
| 500   | 내부 서버 오류     |

### 페이지네이션

페이지네이션 쿼리로 요청을 하는 경우, 응답에 메타 데이터가 포함되어 이전, 현재, 첫 번째 및 마지막 페이지를 쉽게 탐색할 수 있습니다.

```json
{
    "data": [
        // 응답 데이터 
    ],
    "meta": {
        "total_pages": 100,
        "total_rows": 2000,
        "order": "DESC",
        "order_by": "resource_field",
        "limit": 20,
        "offset": 0,
        "next_key": ""
    }
}
```


---

# 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, and the optional `goal` query parameter:

```
GET https://support.iafcertsearch.org/api-developer-guide/api-ko/api-integration/responses.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.