Environment Format
Environment files use dotenv format and live under <collection>/.environments/.
One .env file per environment.
File Format
Section titled “File Format”_color=successbase_url=https://api.example.comapi_key=sk-placeholder# disabled_key=this_is_disabledKEY=value: Active variable, available for$KEYsubstitution# KEY=value: Disabled variable. Prefix with#to exclude from substitution_color=<name>: Sets sidebar badge color for this environment
Badge Colors
Section titled “Badge Colors”| Color | Badge |
|---|---|
primary |
Cyan |
secondary |
Blue |
accent |
Purple |
error |
Red |
warning |
Yellow |
success |
Green |
info |
Light blue |
Convention
Section titled “Convention”| Environment | Recommended _color |
|---|---|
| Production | success (green) |
| Staging | warning (yellow) |
| Development | info (blue) |
Variable Substitution
Section titled “Variable Substitution”All $VARNAME references in request files are resolved against the active
environment. Variables are applied to:
urlheadersvaluesparamsvaluesbodyform_datavaluesfile_pathauthfields (token, user, pass, key, value)
Unresolved variables cause noodle to throw an error at send time.
Best Practices
Section titled “Best Practices”- Always keep the same set of variable names across all environments. Different values, same keys.
- Comment out (
#) variables that don’t apply to an environment — don’t delete the line. - Use placeholder values (e.g.,
sk-placeholder) in dev/staging. Keep real secrets out of version control. - Put
_coloron the first line for visual clarity.
