# Page Not Found

The URL `documentacao/faq/erros-e-problemas/codigos-de-erros-da-meta` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Códigos de Erros](https://docs.flw.chat/guide/documentacao/faq/conexao-whatsapp/erros-e-problemas/codigos-de-erros-da-meta.md)
- [Erros comuns](https://docs.flw.chat/guide/documentacao/faq/conexao-whatsapp/erros-e-problemas.md)
- [Revisão de banimento](https://docs.flw.chat/guide/documentacao/faq/conexao-whatsapp/erros-e-problemas/solicitar-revisao-de-banimento.md)
- [Mensagens não chegam](https://docs.flw.chat/guide/documentacao/faq/instagram-messenger/mensagens-do-instagram-nao-chegam.md)
- [Tipos de perfis de usuários](https://docs.flw.chat/guide/documentacao/ajustes/usuarios/tipos-de-perfis-de-usuarios.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://docs.flw.chat/guide/documentacao/faq/conexao-whatsapp/erros-e-problemas/codigos-de-erros-da-meta.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.

### Option 2 — Browse the documentation index

Full index: https://docs.flw.chat/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://docs.flw.chat/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/guide/documentacao/faq/conexao-whatsapp/erros-e-problemas/codigos-de-erros-da-meta.md`).

You may also use `Accept: text/markdown` header for content negotiation.