Environment
Environment variables store reusable values you can reference in requests across Replay, Automate, and Workflows.
Creating and Editing Variables
- Open Environment from the left navigation.
- Click Add variable.
- Enter a name (letters, numbers, and underscores; no spaces).
- Enter the value.
- Toggle Secret if the value is sensitive (API keys, tokens, passwords). Secret values are masked in the UI and excluded from AI context.
- Click Save.
To edit an existing variable, click its row and update the name or value.
Using Variables in Requests
Reference a variable anywhere in a request using double-brace syntax:
{{VARIABLE_NAME}}Examples:
- Base URL field:
/api/v1/users - Authorization header:
Bearer - Request body:
{"tenant": ""}
Ogma substitutes the variable value at send time. If a variable is not found, the literal string is sent instead.
Variable Scope
Variables are project-level. Each project has its own variable set. Switching projects changes which variables are available. There is no global variable scope shared across projects.
AI Assistant Access
The AI assistant can read non-secret variable names and values to provide context when you ask it to analyze a request or draft a test plan. Secret variables are never included in AI context.
Common Uses
| Variable | Example value |
|---|---|
BASE_URL | https://api.example.com |
AUTH_TOKEN | eyJhbGci... (mark as secret) |
TARGET_HOST | app.example.com |
API_KEY | sk-... (mark as secret) |
USER_ID | 12345 |