> 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/partner-integration/authentication.md).

# Authentication

Dutchman Bridge has two credentials. As a partner integrating the API you only need the first.

## API key — the Partner API

Every route under `/api/v1/partner/v1/...` is authenticated with your API key in the `x-api-key` header:

```http
x-api-key: db_live_5f8c2a7e91d34b0c8a6e1f9d2b7c4e3a
```

```bash
curl "https://app.dutchmanbridge.com/api/v1/partner/v1/customers/$CUSTOMER_ID/balance" \
  -H "x-api-key: $API_KEY"
```

The key is issued from the partner console (*Dashboard → API key*) and identifies your business. Every customer you register belongs to it, and customer-scoped routes take the customer id in the path — there is no per-customer token.

* Keep it on your servers. Never ship it in a browser, mobile app, or public repository.
* Rotate it from the same console screen if it leaks; the old key stops working immediately.
* A missing or unknown key is a `401`. A `customerId` that is not one of yours is a `403` — the same response whether the id is unknown or belongs to another partner.
* A valid key whose business has not yet passed KYB is a `403` with the message `Your partner account is not yet approved…`. The key proves who you are; approval is what lets you act.

The [Partner quickstart](/partner-integration/partner-quickstart.md) walks through the first calls.

## The console

Signing in to the console (company details, KYB, key management) uses your email and password, not the API key, and an API key is not accepted on the console's own routes. You do not need them for an integration.

## Webhook signatures

Deliveries from Dutchman Bridge to your endpoint are authenticated the other way round: an HMAC-SHA256 signature in the `X-Dutchman-Signature` header, computed with the secret returned by `PUT /partner/v1/webhook`. Verification is covered in [Webhooks](/partner-integration/partner-webhooks.md#verifying-the-signature).


---

# 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/partner-integration/authentication.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.