# API Reference

The API Reference is your comprehensive guide for integrating the Tylt Crypto Payment Gateway into your application or website with ease. It details every aspect of the available API functionalities, offering clear and concise information for developers, merchants, and businesses alike.

Whether you’re accepting or making crypto payments, reviewing transaction histories, or exploring supporting functionalities like supported currencies and networks, this documentation provides the essential tools for a seamless integration.

#### What You’ll Find in the API Reference:

1. **Accept Crypto Payments**: This section guides you through the process of accepting cryptocurrency payments, including detailed transaction history for pay-ins.
2. **Make Crypto Payments**: Learn how to initiate payouts, including viewing transaction history for payouts.
3. **Supporting APIs**: This section covers additional API functionalities, such as listing supported currencies, networks, and fiat.

Each section provides:

* **Endpoint Descriptions**: A breakdown of each API endpoint.
* **Request & Response Formats**: Clear examples of request and response structures, including status codes.
* **Code Snippets**: Implementations in popular programming languages like Node.js, Python, and more.
* **Error Handling**: Insights into common errors and best practices for managing them.

With this API Reference, you’ll have everything you need to seamlessly integrate Tylt's crypto payment solutions into your platform.


---

# Agent Instructions: 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:

```
GET https://docs.tylt.money/tylt-cpg-crypto-asset-gateway/api-reference.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
