process.env, os.environ, os.Getenv, System.getenv. There is no separate configuration API to learn.
What’s in the environment
Declaring variables
Define non-sensitive configuration under[env_vars] in func.toml:
- All values are strings. Parse numbers and booleans in your code.
- Changes take effect on the next
telnyx-edge ship— there is no live update. - Names share the
envnamespace with bindings. If an[env_vars]entry has the same name as a declared binding — or is namedSECRETSwhile a[[secrets]]block is declared —shipwarns that one shadows the other onenvand still proceeds; rename one. (A binding namedSECRETS, or a duplicate[[secrets]]handle, is a hard error.)
[env_vars] values are plaintext in func.toml and end up in version control. Put credentials in secrets instead.
Reading variables
- TypeScript / JavaScript
- Python
- Go
- Quarkus (Java)
Environment variables vs secrets
Next Steps
- Secrets — the server-side counterpart for sensitive values, including the typed
env.SECRETSsurface for TypeScript - Bindings — typed, pre-authenticated handles instead of raw variables
- Configuration — the full manifest reference: every
func.tomlandtelnyx.tomlkey