> For the complete documentation index, see [llms.txt](https://docs.coda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coda.co/codashop-and-distribution/integration-guides.md).

# Integration Guides

The following section provides a detailed overview of the process and the APIs employed by Coda for the verification and [validation](https://docs.coda.co/codashop-and-distribution/integration-guides/validation-api-request/validation-api-request-example-and-responses.md) of game account information, retrieving server lists, and processing top-up or recharge requests for top-up products that will be sold on Codashop and Coda's Distribution network.\
\
You can use the sidebar on the left side of your screen to quickly dive into various feature request guides:

<table data-card-size="large" data-view="cards"><thead><tr><th align="center"></th><th align="center"></th><th data-hidden></th><th data-hidden></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td align="center"><mark style="color:purple;"><strong>Validation API Request</strong></mark></td><td align="center">Order details for Partners to validate</td><td></td><td></td><td><a href="https://docs.coda.co/codashop-and-distribution/integration-guides/validation-api-request.md">Validation API Request</a></td></tr><tr><td align="center"><mark style="color:purple;"><strong>Top-Up API Request</strong></mark></td><td align="center">Details of a successful purchase from Codashop to Partners</td><td></td><td></td><td><a href="https://docs.coda.co/codashop-and-distribution/integration-guides/top-up-api-request.md">Top-Up API Request</a></td></tr><tr><td align="center"><mark style="color:purple;"><strong>Fetch Server List Request (Optional)</strong></mark></td><td align="center">Allows Coda to fetch server lists information</td><td></td><td></td><td><a href="https://docs.coda.co/codashop-and-distribution/integration-guides/fetch-server-list-request-optional.md">Fetch Server List Request (Optional)</a></td></tr><tr><td align="center"><mark style="color:purple;"><strong>UserSync API Request</strong></mark></td><td align="center">Sync In-game user data to verify profiles and offer personalized SKUs</td><td></td><td></td><td><a href="https://docs.coda.co/codashop-and-distribution/integration-guides/usersync-api-request.md">UserSync API Request</a></td></tr></tbody></table>


---

# 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.coda.co/codashop-and-distribution/integration-guides.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.
