---
title: "Environments"
description: "Production and staging base URLs, keys, test data and going live."
url: https://developer.tendralhealth.com/docs/environments
---

# Environments

Tendral runs two environments. Build against staging, then switch the base URL and key to go live.

## Base URLs

| Environment | API base URL | Docs |
| --- | --- | --- |
| Production | `https://api.tendralhealth.com/v1` | https://developer.tendralhealth.com |
| Staging | `https://api.staging.tendralhealth.com/v1` | https://developer.staging.tendralhealth.com |

## Keys

Keys look the same in both environments (`tk_live_…`), but each environment has its own keys: a staging key is refused by production and the other way round. Ask for a staging key when you start building.

## Telling them apart in a response

Every resource and list carries `livemode`. It is `true` only on production. Check it before you act on data, so a staging response can never be mistaken for real activity.

## Test data

Staging holds test data only. Send it nothing real:

- Use addresses at `example.com`.
- Use made-up NPIs, never a real clinician's.
- Treat anything staging returns as disposable; it can be reset without notice.

## Going live

1. Get a production key.
2. Change the base URL to `https://api.tendralhealth.com/v1`.
3. Check that responses carry `"livemode": true`.