> For the complete documentation index, see [llms.txt](https://docs.oxapay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oxapay.com/legacy/api-reference.md). # API Reference The API Reference provides detailed information on the various endpoints and functionalities available in the OxaPay API. This section serves as a comprehensive guide to help you integrate the OxaPay Crypto Payment Gateway seamlessly into your application or website. By referring to the API Reference, you can gain a comprehensive understanding of the OxaPay API and leverage its capabilities to create a seamless payment experience for your users. Whether you need to initiate payments, retrieve payment details, or manage transactions, the API Reference provides the necessary documentation to facilitate successful integration. Now, let's dive into the API Reference section, where you'll find detailed information on each endpoint, their request and response formats, and example code snippets to assist you in integrating the OxaPay Crypto Payment Gateway seamlessly. --- # 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.oxapay.com/legacy/api-reference.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.