> 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-pt/api-integration/errors.md).

# Erros

Às vezes, sua chamada de API gerará um erro. Aqui você encontrará informações adicionais sobre o que esperar se você não formatar corretamente sua solicitação, ou se não conseguirmos processar sua solicitação corretamente.

### Códigos de Resposta

Código de Status Descrição

* 400 Solicitação inválida
* 401 Requer autenticação
* 404 Não encontrado
* 406 Cabeçalho Accept ausente. Por exemplo: `Accept: application/json`
* 429 Muitas solicitações/Limite de taxa excedido
* 500 Erro interno do servidor

### Solicitações Mal-sucedidas

As diretrizes gerais de formatação são exibidas quando o código de status correspondente é retornado.

```http
GET https://api.iafcertsearch.com/api/client/v1/resource HTTP/1.1
```

```http
HTTP/1.1 404 Solicitação inválida
Content-Type: application/json

{
    "errors": [
      {"code": "not_found", "message": "mensagem de erro explicada"},
    ]
}
```


---

# 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-pt/api-integration/errors.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.