TidePay

Authentication

How to authenticate with the Tidepay API.

Every request to the Tidepay API is authenticated with an X-API-Key header. Unlike APIs with separate sandbox/production domains, Tidepay uses a single base URL for both environments — the key you send determines which one a request runs against, not the URL.

Create an API key

Get your API keys from the Tidepay dashboard: Settings → API keys → Generate keys. Both a live key (tp_live_...) and a test key (tp_test_...) are shown there.

Send the key

Include it as a header on every request:

curl "https://api.tidepay.cc/v1/offers" \
  -H "X-API-Key: tp_test_xxx"

A tp_test_... key runs entirely in sandbox: no real blockchain transaction is ever submitted, no real funds move. A tp_live_... key runs in production against real chains and real funds. Both point at the exact same https://api.tidepay.cc/v1 base URL — see Test mode for the full behavioral differences.

Important

Never share your API key with anyone. This credential grants access to the Tidepay API, and any action performed with it is attributed to your account. Tidepay shows the full key once, at creation — it can't be recovered if lost.

Next

  • Errors — how authentication failures are reported.
  • Test mode — full behavioral differences between test and live keys.

API Overview

How the Tidepay API is structured and what you need before calling it.

Core concepts

How Offers, Subscriptions, Customers, Payments, and Settlement Wallets fit together.

On this page

Create an API keySend the keyNext