> 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/developer-platform/retrying-safely.md).

# Retrying safely

Every call that moves money takes an optional `reference` in the body — your own request id. Send the same value again and you get the original record back; nothing moves twice.

| Endpoint                        | Creates          |
| ------------------------------- | ---------------- |
| `POST .../withdraw`             | a withdrawal     |
| `POST .../send`                 | a crypto send    |
| `POST .../funding/charge`       | a funding charge |
| `POST .../global-send/initiate` | a global send    |

```json
{ "amount": 50000, "reference": "req_01HZY4K8N2" }
```

Letters, digits, dot, underscore and hyphen; 120 characters max. It is scoped to the endpoint, so the same value on a withdrawal and on a send are two different records — and it is yours to choose, so make it unique per intended operation (a request id, not a customer id).

**A timeout is not a failure.** If a request times out or returns 5xx, retry it with the same `reference` rather than assuming nothing happened — that is the only way to find out which. Without one, a retry is a second withdrawal.

Buy and sell are covered by their quote instead: a `quoteId` executes exactly once, including when two requests arrive together. A second execute is a 400, and an execute that fails (insufficient balance, say) leaves the quote usable until it expires.


---

# 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/developer-platform/retrying-safely.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.