> For the complete documentation index, see [llms.txt](https://docs.dutchmanbridge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dutchmanbridge.com/get-started/readme.md).

# Get started

From an empty account to your first API call. Then follow the [quickstart](/get-started/quickstart.md) to take a customer from registration to moving money.

## Get access

1. **Sign up as a business** at [dutchmanbridge.com](https://dutchmanbridge.com). The console is where you manage your account; your customers never see it.
2. **Complete KYB.** Upload your company documents from the console. Compliance reviews them and tells you the outcome by webhook once you have one registered (`partner.approved`, `partner.rejected`, or `partner.resubmission_requested` with a reason) and in the console. Approval is a condition of calling the API at all: until compliance approves your business, the console does not reveal your API key and every `/partner/v1` request returns `403` with `"Your partner account is not yet approved…"`. Build against the OpenAPI spec and the SDK's types in the meantime.
3. **Issue an API key** from *Dashboard → API key*. Rotating it from the same screen invalidates the previous key immediately.

The key identifies your whole business, not one customer. Keep it on your servers: **never embed it in a browser, mobile app, or public repository.** If it leaks, rotate it.

## Base URL and authentication

|                |                                                                                     |
| -------------- | ----------------------------------------------------------------------------------- |
| Base URL       | `https://app.dutchmanbridge.com/api/v1`                                             |
| Partner routes | `/partner/v1/...` under that base                                                   |
| Auth header    | `x-api-key: <your key>` on every call                                               |
| Content type   | `application/json` (except the KYC document upload, which is `multipart/form-data`) |

Responses, errors, retries and pagination are covered in the [developer platform](https://docs.dutchmanbridge.com/developer-platform). If you write TypeScript, the [SDK](https://docs.dutchmanbridge.com/developer-platform/sdk) wraps every route.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dutchmanbridge.com/get-started/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.