Hbridge Docs
API reference

Hbridge API

Provision crypto deposit addresses for your users, detect deposits, and pay out your collected balance, net of the Hbridge fee. Everything you need to integrate lives here: start with the quickstart, learn the concepts, then reach for the API reference.

Quickstart Introduction

Static wallets

One persistent address per user

Get started
Introduction

What the Hbridge API does and the conventions every endpoint follows.

Get started
Quickstart

Go from zero to your first deposit and payout in a handful of API calls.

Concepts
Core concepts

The model behind users, deposits, balances, payouts, and webhooks.

API reference
Users & addresses

Register end users and provision a persistent deposit address per chain.

API reference
Deposits & balances

Read detected on-chain deposits and your collectable balance.

API reference
Payouts

Pay your collected net balance out to your whitelisted address.

API reference
Webhooks & events

Receive signed, at-least-once event notifications and replay them.

Reference
Errors & pagination

Status codes, cursor pagination, idempotency, and rate limits.

Dynamic wallets

A new address per payment

Dynamic wallets
Overview

Address-per-payment checkout: how dynamic wallets differ from the static per-user model.

Dynamic wallets
Payment requests

Create a per-payment address and amount, then track it to completion.

Dynamic wallets
Integration walkthrough

Wire up a hosted checkout end to end, from payment request to confirmation.

Reference
Errors & pagination

Status codes, cursor pagination, idempotency, and rate limits.