---
title: "Environments and API keys"
description: "The base URLs of the Nodu sandbox and of production, what differs between the two environments, and how you get and keep API keys."
url: "/guides/get-started/environments-and-api-keys/"
index: "/llms.txt"
---

# Environments and API keys

Nodu has two environments: the sandbox, for building and testing your integration, and production. Each environment has its own base URL and its own API keys. [Authentication](/guides/api-basics/authentication/index.md) explains how to send a key.

## The two environments

| Environment | Base URL | What it is for |
|---|---|---|
| Sandbox | `https://api.sandbox.nodu.fi` | Building and testing. No real money moves. |
| Production | `https://api.nodu.fi` | Real customers and real money. |

The paths are the same in both environments. Every path starts with `/v1`. For example, [List customers](/api/tag/customers/get-v1-customers.md) in the sandbox is a `GET` request to `https://api.sandbox.nodu.fi/v1/customers`.

Each environment keeps its own data. A customer, an external account or a transfer that you create in the sandbox does not exist in production.

## What differs in the sandbox

The sandbox uses the same requests, the same statuses and the same webhook events as production. In the sandbox, you can simulate the following three steps:

| In production | In the sandbox |
|---|---|
| Nodu reviews the customer's information and documents, unless it relies on your own checks under a respondent agreement. | A marker in the customer's address or a test document decides the outcome: see [Test onboarding in the sandbox](/guides/sandbox/test-onboarding/index.md). |
| The customer sends a payment to fund a transfer. | You simulate the payment: see [Simulate funding in the sandbox](/guides/sandbox/simulate-funding/index.md). |
| The customer proves that they control a crypto wallet, when Nodu asks for it. | Nodu asks for the proof whatever the amount of the transfer. You simulate the proof, or give it with testnet coins: see [Simulate crypto wallet verification in the sandbox](/guides/sandbox/simulate-wallet-verification/index.md). |

The simulation operations work in the sandbox only. In production, Nodu refuses them with the status `403` and the code `forbidden`.

## API keys

Every request carries an API key.

- **A key belongs to one environment.** A sandbox key does not work in production. A production key does not work in the sandbox. Nodu answers such a request with `401 Unauthorized`.
- **The start of a key names its environment.** A sandbox key starts with `test_`. A production key starts with `live_`.
- **A key gives full access to the API in its environment.** Anyone who holds the key can read your customers' data. They can also create transfers. [Authentication](/guides/api-basics/authentication/index.md#keep-api-keys-safe) says how to keep keys safe.
- **A key can have a list of allowed IP addresses.** Nodu then refuses a request from another address with `403 Forbidden`.

## Get a key

Nodu gives you your API keys during the integration, through the support channel agreed with Nodu.

- You receive one key for the sandbox first. You receive a production key when you go live: see [Go live](/guides/get-started/go-live/index.md).
- Store each key in a secret manager or in protected server configuration as soon as you receive it.
- If you lose a key, or a key may have been exposed, ask Nodu for a new key through the same channel.

## Next steps

- [Authentication](/guides/api-basics/authentication/index.md): how to send the key and interpret a `401` or `403` response.
- [Quickstart: your first sandbox transfer](/guides/get-started/quickstart/index.md): use a sandbox key from the first request to a completed test transfer.
- [Go live](/guides/get-started/go-live/index.md): what to check before you use a production key.
