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

# Servers

### API servers

| Environment | Base URL                                                          |
| ----------- | ----------------------------------------------------------------- |
| Sandbox     | [https://sandbox-api.fonbnk.com](https://sandbox-api.fonbnk.com/) |
| Production  | [https://api.fonbnk.com](https://api.fonbnk.com/)                 |

Sandbox and production are separate systems with separate credentials, separate users, and separate orders. Nothing crosses between them, so start in sandbox and move the same code to production by changing this base URL and your API keys.

Sandbox never moves real money. Its offers are simulated, and its quotes expose the extra `depositSandboxForcedFlow` and `payoutSandboxForcedFlow` fields so you can force an outcome on demand — a deposit success, invalid, underpayment or overpayment, and a payout success or failure. Which of those a given leg offers varies, so read the field's own `options` array. See [Create quote](/server-to-server/api-endpoints/create-quote.md) for how the fields arrive.

{% hint style="warning" %}
Sandbox contract addresses, bank names and carrier lists are fixtures. Never hard-code anything you read from a sandbox response — always take them from [Get available currencies](/server-to-server/api-endpoints/get-available-currencies.md) and from the quote.
{% endhint %}


---

# 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.fonbnk.com/server-to-server/servers.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.