# Hybrid-Chain API Reference

### Introduction / Abstract

The Hybrid-Chain API is the primary interface to interact with the Hybrid-Chain infrastructure—an advanced, multi-layer blockchain platform that enables secure, composable, and high-performance digital asset operations across a wide range of supported blockchains. This API reference serves as the definitive guide for integrators, developers, fintech teams, and enterprises seeking to build, automate, or extend their own services using the Hybrid-Chain’s powerful backend.

At the heart of Hybrid-Chain lies a layered architecture that integrates:

* Layer-0: A trust and validation layer that uses quantum-resilient cryptography and independently operated indexers to verify the authenticity of cross-chain transactions.
* Layer-2: A high-performance abstraction layer that enables fast settlement, low-cost computation, and scalable smart transaction routing between assets, protocols, and user accounts.

### What the API Enables

The Platform API exposes the full capability of Hybrid-Chain’s core components. Through authenticated endpoints, developers can:

* Create and manage Hybrid-Vaults (multi-chain, self-custody wallets) with granular permission controls.
* Initiate, track, and verify deposits and withdrawals on all supported Layer-1 chains, such as Bitcoin, Ethereum, Solana, Litecoin, and TRON.
* Configure and execute Secure Send transfers (email-to-wallet routing), margin interactions, or vault-to-vault operations in milliseconds.
* Tokenize real-world assets, equities, claims, NFTs, or financial derivatives via the built-in tokenization engine.
* Launch and manage ICO/NFT campaigns, automate smart delivery post-payment, and integrate with hybrid invoice mechanisms.
* Build high-throughput trading platforms, perpetuals exchanges, FX desks, or remittance platforms using powerful real-time endpoints.
* Fully white-label the platform, including user-facing flows, with APIs to register users, assign vaults, manage 2FA, and trigger custom workflows.

{% hint style="info" %}
All requests are cryptographically secured through RSA-signed headers and can be augmented with entropy-derived encryption keys to prevent MITM or replay attacks. Access is gated through a secure API key infrastructure with environment-specific scopes (sandbox or production).
{% endhint %}

### API Design Philosophy

The Hybrid-Chain API is designed to be:

* Composable: Endpoints can be chained or modularly implemented based on business logic.
* Deterministic: Response formats and behaviors are consistent across all environments.
* Audit-Ready: Every state change is ledgered, traceable, and cryptographically verifiable.
* Secure-by-Design: No shared custody, no key leakage, and no mutable state transitions without authorized signatures.
* Business-Oriented: Grouped by business-case domains (Wallet Operations, Tokenization, User Mgmt, Finance, etc.) to reduce integration time and enhance clarity.

### Getting Access

To build on Hybrid-Chain:

* White-Label Operators can apply for full production deployment and partner credentials via <contact@hybrid-chain.com>. This includes access to a dedicated sandbox, dynamic branding options, invoice/payment customization, and API scopes tailored to their vertical.
* Independent Developers can use the publicly available API keys to interact with the sandbox environment, build automation around testnet wallets, and evaluate the infrastructure for their own applications.

\
Once authenticated, partners can use the API to onboard users, monitor liquidity, execute payouts, validate deposits via the ledger, and build sophisticated cross-chain apps without ever handling private keys or relying on custodial intermediaries.

### Documentation & Next Steps

The API Reference is organized by collection and function:

* Vault & Wallet Management
* Payments & Transactions
* Deposit & Withdrawal Handling
* Tokenization & NFT Launch
* Trading & Settlement
* User & Identity Control
* Event Logs & Audit History

\
Each section provides a full specification, including request schema, sample calls, expected responses, and real-world usage tips. The API is continuously evolving, and new capabilities are added regularly to support business-case expansions like Web3 gaming, FX settlement, carbon tokenization, and regulated financial services.

{% hint style="info" %}
Important: the Hybrid-Chain terms and conditions always apply.

They're available here: [https://hybrid-chain.com/terms-privacy-policy](https://hybrid-chain.com/terms-privacy-policy/)
{% endhint %}

### Jump right in

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Authentication</strong></td><td>Register Users, Manage Access and functionalities, Secure accounts with Master Passwords and Multi-Factor Authentication.</td><td></td><td></td><td><a href="/pages/p2KcObGMaJpU16OlnSok">/pages/p2KcObGMaJpU16OlnSok</a></td></tr><tr><td><strong>User Profiles &#x26; Data</strong></td><td>Handle User's profile data, features, settings, personal preferences and general information about the user's account.</td><td></td><td></td><td><a href="/pages/9Gyt5mAWUGfc4HDQk0iE">/pages/9Gyt5mAWUGfc4HDQk0iE</a></td></tr><tr><td>Vault / Wallet Functions</td><td>Manage Self-Custodial Wallets, connectivity to external wallets and various different blockchains for transactions and more.</td><td></td><td></td><td><a href="/pages/OmAJutZAdEsCRLayhMyx">/pages/OmAJutZAdEsCRLayhMyx</a></td></tr></tbody></table>


---

# 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://dev.hybrid-chain.com/api-docs/readme.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.
