Skip to main content
The Rhino.fi API lets your platform accept tokens on any supported chain and settle them on the chain and in the token you choose. It works from any language that can make HTTPS requests. Every request and response body is JSON.
Building in JavaScript or TypeScript? The Rhino.fi SDK wraps these endpoints and handles authentication for you. This section is for teams integrating over REST directly, or teams who want to understand what the SDK does.

Choose your integration

There are two ways to accept and settle funds with Rhino.fi, and clients often use both. Some rely on Smart Deposit Addresses, some on bridge transfers, and others combine the two. Both run on the same settlement infrastructure, are covered by your subscription and report progress through the same status endpoints and webhooks. Using both is common: Smart Deposit Addresses for deposits coming in, and bridge transfers for withdrawals going out or to move funds between your own wallets.

Before you start

You need:
  1. A Rhino.fi project and API key. Create both in the Rhino.fi Console. Read Authentication before choosing a key type.
  2. A server-side environment for secret keys and webhook handling.
  3. Destination addresses on each chain you will settle to. These can be your own addresses or your end customers’ addresses.
  4. For bridge transfers sent by you: a signer on each source chain, such as a wallet, a custody provider or an MPC service. You don’t need one if your end customers sign and send from their own wallets.

Test your integration

We recommend testing on mainnet with small amounts, in a project you keep separate from production. Testnets have limited liquidity routes, so they don’t show how transfers and swaps behave in production. Rhino.fi handles small transactions the same way as large ones, so a small mainnet test runs the real flow end to end.
  1. Create a separate test project in the Rhino.fi Console, with its own API keys and webhook URL. This keeps test traffic, history and webhooks apart from production.
  2. Send small transactions on every chain and token pair you plan to offer, within the deposit limits for each route.
  3. Test the edge cases, such as a deposit below the minimum, an unsupported token or an expired quote. Check that your system handles the resulting statuses and webhooks.
  4. Move to your production project when everything works. Your account manager can help you plan the switch.

Base URLs

All endpoints are served over HTTPS from https://api.rhino.fi. Each service has its own path prefix.

How this section is organized

Read the guides in order. Each page ends with a link to the next one.
1

Authentication

Choose the right key type, exchange it for a JWT and keep the token fresh. Read the guide.
2

Core concepts

Learn the identifiers, amounts, errors, pagination and limits that every endpoint shares. Read the guide.
4

Track transactions

Receive webhooks, query status and reconcile history. Read the guide.
5

Go live

Work through the security and operations checks before production. Read the checklist.

Next steps

Authentication

Set up your API key and get your first JWT.