> For the complete documentation index, see [llms.txt](https://docs.1q.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1q.gg/documentation/reference/erros-e-diagnostico.md).

# Erros e diagnóstico

Definitions of terms you'll encounter in the docs and dashboard.

Erros da Games API usam o envelope:

```json
{"code":"INVALID_SIGNATURE","message":"Operator request signature is invalid.","request_id":null,"retryable":false}
```

| Código                         | Interpretação                      | Ação                                        |
| ------------------------------ | ---------------------------------- | ------------------------------------------- |
| INVALID\_API\_IDENTITY         | Chave não reconhecida              | Conferir credencial e aprovação             |
| INVALID\_SIGNATURE             | Assinatura errada                  | Conferir canonicalização e secret           |
| IP\_NOT\_ALLOWED               | Origem não autorizada              | Conferir IP real de saída                   |
| REQUEST\_REPLAYED\_OR\_EXPIRED | Nonce repetido ou relógio inválido | Renovar nonce/timestamp                     |
| IDEMPOTENCY\_CONFLICT          | Chave usada com payload diferente  | Corrigir identidade da operação             |
| IDEMPOTENCY\_IN\_PROGRESS      | Primeira execução em processamento | Repetir com mesma chave/payload após espera |

O cabeçalho `X-Request-Id` correlaciona a solicitação. Colete método, caminho, request\_id, código, horário UTC, provedor e jogo. Não registre tokens, segredos, cookies ou assinatura completa.

## Diagnosticando erros HTTP 500

Verifique primeiro o corpo estruturado da resposta, `request_id`, `retryable`, status de `launchable`, disponibilidade do provedor, configuração do Projeto e logs correspondentes. Não converta indiscriminadamente erro 500 em sucesso nem tente debitá-lo novamente.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.1q.gg/documentation/reference/erros-e-diagnostico.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.