HYBRID-CHAINAPI
PRODUCTIONv1Get access

HYBRID-CHAIN PLATFORM API

API Reference

The primary interface for account-scoped wallet, payment, trading, tokenization, data, and white-label operations across Hybrid-Chain.

RESTJSONBEARER AUTHSANDBOX + PRODUCTION

ENVIRONMENT

Base URL

All documented v1 requests are made against the production API host. Access and endpoint scopes depend on the credentials issued for your environment.

PRODUCTION
https://api.hybrid-chain.com/api/v1

CORE FUNCTIONALITY

Authentication

Authentication uses a user-specific seed and random key to transform sensitive credential material before login. A successful login returns the bearer token used by protected endpoints.

  1. 1Request the account seed.
  2. 2Hash the password with the seed.
  3. 3Hash the result with the random key.
  4. 4Log in and retain the bearer token.
SECURITY NOTE

Use the unique account identifier—email or international MSISDN—to associate the seed and session with the correct profile. Never expose credentials or bearer tokens in browser code.

GET/auth/seedFull spec ↗

Get the seed and one-time random key used to transform sensitive login material.

QUERYTYPEREQUIRED
emailstringOptional*
msisdnstringOptional*
curl 'https://api.hybrid-chain.com/api/v1/auth/seed?email=user@example.com'
POST/auth/loginFull spec ↗

Submit the unique identifier, randomized password hash, and one-time random key to establish a bearer session.

{
  "email": "user@example.com",
  "password": "<randomized_sha256>",
  "randomkey": "<one_time_random_key>"
}
POST/auth/registrationFull spec ↗

Register a private or corporate account and associate it with an optional white-label context.

PAYMENTS

Create a payment request

Create an invoice-style request for a specific amount and settlement currency. The response includes the payment identifier, payment URL, and QR data required for checkout.

AUTHORIZATION

Send the bearer token through the Authorization header for protected payment requests.

POST/pay/new_payment_requestFull spec ↗
cURLJSON bodyResponse
curl --request POST \
  --url https://api.hybrid-chain.com/api/v1/pay/new_payment_request \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
    "currency": "USD",
    "amount": 10,
    "description": "Order 1048"
  }'
200 · OK
{
  "payment_hash": "<payment_id>",
  "payment_url": "https://hybrid-chain.com/pay/<payment_id>",
  "qr_code_base64": { "meta_data": {}, "qrdata": {} }
}

AUTOMATION STUDIO

Verify every callback.

Hybrid-Chain sends a stable event envelope and signs the exact request body. Keep the endpoint secret in a secrets manager, reject stale timestamps, and deduplicate the event ID before applying business logic.

SIGNATURE INPUT

Compute HMAC-SHA256 over <timestamp>.<raw_request_body>. Compare it in constant time with the v1 value in Hybrid-Event-Signature.

POSTYour HTTPS endpointOpen Studio ↗

Return a 2xx response within eight seconds. Redirects are not followed; failed attempts use the published backoff schedule.

Hybrid-Event-Id: evt_01J…
Hybrid-Event-Type: trade.order.filled
Hybrid-Event-Timestamp: 1784073600
Hybrid-Event-Signature: v1=<hmac_sha256>
EVENT ENVELOPE
{
  "id": "evt_01J…",
  "type": "trade.order.filled",
  "created": "2026-07-14T22:00:00Z",
  "livemode": true,
  "api_version": "2026-07-14",
  "data": { "order_uuid": "ord_01J…" },
  "metadata": {}
}

DIRECTORY

Endpoint families

The published API is organized by business domain so teams can adopt only the capabilities required by their product.

01Authentication+
02User profile data+
03Vault & wallet+
04Trading & tokens+
05Payments & merchant+
06Storage & data+
07Automation & callbacks+
08Peripheral services+

START BUILDING

Request an integration environment.

Tell us what you are building and which endpoint families you need. We’ll scope the right sandbox and access model.

Request API access ↗