> ## Documentation Index
> Fetch the complete documentation index at: https://docs.etherfuse.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> The Etherfuse REST API: base URLs, auth, and conventions.

The Etherfuse API is a REST API. It accepts and returns JSON and uses standard HTTP verbs and status codes. Every endpoint page includes a **"Try it"** playground and code samples.

## What is in the reference

* **Payment accounts, quotes and orders** (`/organization/{organizationId}/*`): register the bank accounts and wallets money moves between, price a transfer, create the order and track it. `organizationId` is your own organization or one of your direct customer organizations. [`GET /orders`](https://docs.etherfuse.com/v2/api-reference/orders/list-orders) lists the orders of your organization and all its customer organizations. Start with [Register payment account](https://docs.etherfuse.com/v2/api-reference/payment-accounts/register-payment-account.md).
* **Webhook subscriptions** (`/webhook_subscription*`): receive `orderUpdated`, `paymentAccountUpdated`, `kycUpdated` and `kybUpdated` events. One subscription covers your organization and every customer organization.
* **Organizations, members, KYC and KYB**: read your organization and set your default partner fee (`/me`), create and list customer organizations (`/organization`, `/organizations`), manage a business's members, and verify customers. Start with [Create customer organization](https://docs.etherfuse.com/v2/api-reference/organizations/create-organization.md).
* **Assets, statements and lookup**: supported assets, wallet balances, monthly partner statements, and public reference data such as exchange rates and stablebonds. The `/lookup/*` endpoints need no API key.

## Base URLs

| Environment | Base URL |
| - | - |
| **Sandbox** | `https://api.sand.etherfuse.com` |
| **Production** | `https://api.etherfuse.com` |

Build and test against the sandbox first. See [Initial Setup](https://docs.etherfuse.com/v2/initial-setup.md). The endpoints are the same in both environments; only the base URL and API key differ.

## Authentication

Send your API key in the `Authorization` header, with **no `Bearer` prefix**. See [Authentication](https://docs.etherfuse.com/v2/authentication.md) for the sandbox and production key rules.

```bash theme={null}
curl https://api.sand.etherfuse.com/organization/<organization_id>/payment_accounts \
  -H "Authorization: <your_api_key>"
```

## Conventions

> [card] [Errors](https://docs.etherfuse.com/v2/errors.md)
>
> RFC 9457 problem details with a stable `type` for every error.

> [card] [Pagination](https://docs.etherfuse.com/v2/pagination.md)
>
> `pageSize` and `pageNumber` query parameters, and one page envelope.

> [card] [Idempotency](https://docs.etherfuse.com/v2/idempotency.md)
>
> Creating an order twice from the same quote returns the same order.

> [card] [Webhooks](https://docs.etherfuse.com/v2/webhooks.md)
>
> Signed events that carry the full order or payment account.

## Use the spec directly

[Download `openapi-v2.json`](https://docs.etherfuse.com/openapi-v2.json) to import into Postman or Insomnia, or to generate a client. To use natural language instead, connect the [MCP server](https://docs.etherfuse.com/v2/mcp-overview.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.