> 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/top-up-api-request.md).
# Top-Up API Request
This message provides details of a successful purchase from Codashop to the partner. As a result, the customer's game account should be successfully topped up with the item specified in the call.
Codashop anticipates a response within 5 seconds. The procedure should be idempotent, meaning that responses to two identical calls should be consistent and avoid triggering multiple top-ups.
It is important to note that the ID, txnId, and orderId utilized in top-up requests may differ from those used in the validate request for the corresponding purchase. Top-ups should be fulfilled based solely on the SKU.
Order Complete Page for Successful Purchase
---
# 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://docs.coda.co/codashop-and-distribution/integration-guides/top-up-api-request.md?ask=&goal=
```
`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.