Skip to main content

Base URL

The API runs in two independent environments. Append /api/v1 to the host for your environment: Use the server dropdown at the top of any endpoint page to switch the interactive examples between them. See Environments for keys, clusters, and dashboards.

Authentication

All API endpoints require an API key. Pass it via the x-api-key header or as a Bearer token.
API keys are prefixed to indicate mode: The Solana cluster (mainnet/devnet) depends on the environment the API is deployed against.

Request format

Use JSON request bodies for POST requests and standard path/query parameters for GET and DELETE requests.

Idempotency

All POST mutations require an Idempotency-Key header (8–64 characters, [a-zA-Z0-9._-]). Use a random UUID per request. Reusing a key with a different body returns MH_071.

Error codes

All errors include a structured MH_XXX code for programmatic handling.

Authentication

Validation

Transfer lifecycle

Webhooks

Recovery

Reward claims

Internal

Rate limits

Rate limits are enforced per API key, per endpoint. When exceeded, the API returns MH_004 with a Retry-After header.

Pricing

Pricing tiers are determined by the USD equivalent of the transfer at quote time. For native SOL, the backend resolves USD value from CoinGecko spot pricing. Fees are split between you (the integrator) and the platform.

Estimate fees

Check costs before creating a transfer.

Create transfer

Create a transfer and receive funding transactions.

Webhooks

Receive real-time transfer lifecycle events.

Usage

View usage and fee summaries for your integration.