> ## Documentation Index
> Fetch the complete documentation index at: https://docs.linguolink.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Environment Overrides

> Use environment-specific values for different deployment targets.

Each project defines its own set of environments (these are free-form labels you
choose, e.g. `development`, `staging`, `production` — they are not a fixed list).
An override lets a translation key resolve to a different value for a specific
environment, while falling back to the base value everywhere else.

Common use cases:

* Environment-specific URLs
* Region-specific compliance text
* Internal-only labels in staging

## Exporting with Overrides

Pass the `environment` query parameter to the export endpoint to apply that
environment's overrides on top of the base values:

```bash theme={null}
curl -H "Authorization: Bearer YOUR_API_KEY" \
  "https://linguolink.dev/api/v1/pull?project_id=YOUR_PROJECT_ID&language=en&environment=production&format=json" \
  -o ./locales/en.json
```

Keys without an override for the requested environment fall back to their base
value, so the export is always complete.