Documentation

This documentation is the public technical reference for integrating with the platform's user-facing services. It is designed for product teams, backend developers, automation engineers, and partners who need stable API behavior, clear request and response contracts, and predictable integration flows.

Each guide focuses on a production-facing API surface and shows how to authenticate, submit requests, read status updates, and handle results in a way that is suitable for real customer applications.

What You Can Build

Use these APIs to power workflows such as:

• Privacy-focused transfer experiences with dedicated order tracking.
• Crypto swap flows with clear order creation and status handling.
• TRON energy rental experiences backed by wallet balance and order history.
• AML wallet screening workflows with customer authentication, credit purchases, wallet funding, reports, and historical lookup.

Start Here

If you are integrating for the first time, this is the recommended order:

1. Choose the product surface that matches your use case.
2. Review its authentication requirements and request schema.
3. Implement order or action creation with idempotency where supported.
4. Store your identifiers and use the history or detail endpoints for tracking.
5. Add error handling for validation, rate limits, and business-rule failures.

API References

Private Send API

Open the Private Send API guide

Create and track privacy-oriented transfer orders, validate destination addresses, and guide users through payment and execution status from request to completion.

Swap API

Open the Swap API guide

Build exchange flows for quoting, creating, and monitoring swap orders across supported currencies and networks.

Rent TRON Energy API

Open the Rent TRON Energy API guide

Integrate customer authentication, wallet funding, balance tracking, TRON energy order placement, live status lookup, and wallet history for energy-rental use cases.

Wallet AML Check API

Open the Wallet AML Check API guide

Integrate wallet screening with customer login, internal wallet funding, AML credit catalog and purchases, check execution, report downloads, and screening history.

Integration Notes

• All examples and contracts in these guides are intended for public-site integrations.
• Use the documented endpoint paths and payloads exactly as described in each guide.
• Keep your client logic idempotent for retriable create operations.
• Persist the identifiers returned by the API so that status, history, and downloads remain easy to retrieve later.

Need a Specific Flow

Choose the guide that matches the customer journey you are building, then implement that API end to end before expanding into adjacent features. This keeps authentication, wallet handling, and status tracking aligned with the documented production flow.