Learn how to manage different environments for your mock APIs, allowing you to test across development, staging, and production.
Environments management is coming soon!We're building a comprehensive way to manage different endpoint configurations for different stages of your application lifecycle.
For now, you can achieve similar results by creating separate projects for each environment or using dynamic response templates that check for environment headers.
Environments allow you to define sets of variables and configurations that can be applied to your mock endpoints. Instead of changing individual endpoints, you switch the active environment.
They make your mock APIs more flexible and realistic. You can simulate production constraints, test different data sets, or point your frontend to different backend services instantly.
Define key-value pairs (e.g., API_KEY, BASE_URL) that differ between environments and inject them into your response templates.
Switch between Development, Staging, and Production instantly via the dashboard or using a simple header in your requests.
Override specific endpoint behaviors, status codes, or delays at the environment level without modifying the base endpoint.
Environment variables will be accessible in your response templates using the double curly brace syntax:
During request processing, the system will replace these placeholders with the values defined in the currently active environment.