> For the complete documentation index, see [llms.txt](https://docs.ddosify.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ddosify.com/ddosify/performance-testing/environment-variables.md). # Environment Variables {% embed url="" %} Ddosify Environment Variables Feature {% endembed %} Similar to Postman, the Ddosify Platform offers an Environment Variables feature that allows you to store constants in variables for convenient use within your test scenarios. #### Environment Variable Creation 1. Navigate to the Environments listing page within the Ddosify App, and find the 'New' button situated at the top-left corner of the page.

2. Assign a unique name to the new environment, which will be used to link the environment to a test. Next, create your name-value pairs. The values can be of various types, such as Number, String, or Array.

#### Attach Environment into Tests 1. In the Ddosify App, go to the Test Suite and choose the Environment you previously created using the dropdown menu in the top-right corner of the Test Suite.

2. Utilize the `{{environmentVariableName}}` format to insert test data into one of the following locations: URL, headers, query parameters, or authentication.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ddosify.com/ddosify/performance-testing/environment-variables.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.