Mock Server Settings
Mock server behavior is configured on two levels: per-server settings for the mock server inside a project, and organization-wide defaults that every new mock server inherits. This guide covers both.
Per-server settings
In the Mock Server workspace, click Mock Server Settings at the bottom of the left panel. A settings sheet opens with all configuration for this server; changes are saved as you make them. Editing requires the mock-server:manage permission (Admins and Owners by default) — with only mock-server:read, the values are visible but read-only.
Server Settings
| Setting | What it does |
|---|---|
| Server Name | A display name for the server. |
| Status | Toggle the server Active/Inactive. An inactive server stops answering requests without losing configuration. |
| Mock URL | The server's public base URL (https://<id>.routebasemock.dev), read-only with a copy button. |
Proxy Configuration
| Setting | What it does |
|---|---|
| Proxy Mode | When enabled, requests that no mock rule matches are forwarded to a real backend instead of failing. Requires a Starter plan or higher — on the Free plan the toggle is disabled with an upgrade hint. |
| Proxy Target URL | The backend that unmatched requests are forwarded to, e.g. https://api.example.com. Shown once Proxy Mode is on. |
CORS Configuration
| Setting | What it does |
|---|---|
| CORS Enabled | Allow cross-origin requests to the mock server, so browser apps can call the mock URL from your dev environment. |
| Allowed Origins | The list of origins permitted to call the server (e.g. https://example.com). Add origins one at a time; remove one by clicking the × on its chip. Shown once CORS is enabled. |
Smart Mock Settings
These settings control generated data. Each one carries a badge showing whether it currently follows the Org Default or holds a Custom value; once you change a setting, a Reset to org default link appears to fall back to the inherited value.
| Setting | Options | What it does |
|---|---|---|
| Data Locale | English, German, French, Spanish | Language of generated names, cities, and other locale-sensitive data. |
| Time Format | ISO 8601, Unix Timestamp, RFC 2822 | Format of generated dates and times. |
| Timezone | UTC plus common IANA zones (Europe/Berlin, Europe/London, Europe/Paris, America/New York, America/Chicago, America/Denver, America/Los Angeles, Asia/Tokyo, Asia/Shanghai, Australia/Sydney) | Timezone for generated dates and times. |
| Default Mock Type | Smart Mock First, Response Example First | Which response source takes priority when an endpoint has both a Smart Mock body and a documented response example. |
| Built-in Matching | On/Off | Enable or disable the built-in field-name matching rules for Smart Mock data generation. |
Security
| Setting | What it does |
|---|---|
| Require Access Token | When enabled, every mock request must carry the server's access token — via an Authorization: Bearer <token> header or a ?token=<token> query parameter. |
| Access Token | Shown once the requirement is on, with copy and Regenerate buttons. Regenerating revokes the old token immediately. |
Danger Zone
Delete Mock Server permanently deletes the server, all its rules, and its request logs. The action cannot be undone and asks for confirmation.
Organization-wide defaults
Under Settings → Mock Server (in the Automation & Integrations group), organization admins configure the baseline that every new mock server starts from. Individual servers can still override each value — the per-server Org Default / Custom badges show where a server has diverged. Changing these settings requires the org:manage-governance permission (Admins and Owners by default).
The page shows the organization's Mock Usage (requests this month against the plan limit, with upgrade warnings from 80% onward) followed by three cards:
Default Settings
The same five values as the per-server Smart Mock Settings — Data Locale, Time Format, Timezone, Default Mock Type, and Built-in Matching — set as organization-wide defaults. Unlike the per-server sheet, this card uses an explicit Save Changes button, with Reset to discard unsaved edits.
Built-in Matching Rules
Override the shipped Smart Mock matching rules for all projects in the organization: toggle individual rules on or off, or use Enable All / Disable All. The card shows how many rules are currently overridden. Projects can still adjust built-in rules locally in their mock server's Smart data tab.
Custom Matching Rules
Organization-wide custom matching rules that apply to all projects, created with the same fields as project-level custom rules (condition type and pattern, data type, faker type, category, remark, sort order, case sensitivity). Use Add Rule to create one; existing rules can be edited, toggled, or deleted.
How defaults, org rules, and project rules interact
- A new mock server starts with all five Smart Mock settings inherited from the organization defaults.
- Changing a setting on the server makes it Custom; Reset to org default re-attaches it, so later changes to the org default flow through again.
- For data generation, project-level matching rules in the Smart data tab sit alongside org-wide rules and built-in rules; matching rules are applied when mock bodies are generated, so after changing rules use Regenerate affected rules (project) or regenerate individual rules to see the effect in existing mocks.
Related
- Mock Server — rules, response bodies, and the mock workflow
- Test Data — fixtures served by fixture-backed response modes
- Roles & Permissions — how mock-server and governance permissions map to roles
- Billing — plan limits, including monthly mock requests