> 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/core-concepts/fluxo-de-integracao.md).

# Fluxo de integração

Understand workspaces, projects, and how permissions work across the platform.

```mermaid
flowchart TD
 A[Backend cadastra jogador] --> B[Consulta catálogo HMAC]
 B --> C{launchable?}
 C -->|Não| D[Exibir indisponibilidade]
 C -->|Sim| E[POST /api/v1/launches]
 E --> F{Aceito?}
 F -->|Sim| G[Abrir launch_url]
 F -->|Erro| H[Verificar código e retryable]
 G --> I[1Q encaminha callbacks financeiros]
 I --> J[Carteira confirma operação idempotente]
```

O backend do cassino autentica toda chamada à Games API. O navegador somente recebe a URL temporária de lançamento que seu backend decidir expor ao jogador.

{% hint style="info" %}
O `user_balance` enviado no lançamento **não transfere autoridade de saldo** à 1Q. O callback do operador permanece obrigatório para movimentações reais.
{% endhint %}

### Responsabilidades

| Seu cassino                     | 1Q                                             |
| ------------------------------- | ---------------------------------------------- |
| Identificar jogadores e sessões | Validar credencial e política de acesso        |
| Manter saldo e ledger           | Iniciar jogo e encaminhar eventos do provedor  |
| Assinar requisições             | Retornar URL, sessão e IDs                     |
| Verificar e executar callback   | Registrar e reconciliar tentativas financeiras |


---

# 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/core-concepts/fluxo-de-integracao.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.