Runtime settings
Configure Mock API Runtime Settings
Configure local port, record generation, authentication, pagination, search, sorting, latency, and injected failures for a synchronized Mock API Studio project.
Set the local server and data defaults
Choose a default port, record count, and deterministic seed. Individual resources can override relevant collection settings.
Match collection query behavior
Configure parameter names, default and maximum page sizes, search, sorting, and direction values to resemble the planned API.
Simulate authentication
Choose bearer-token, API-key, or Basic authentication and configure the unauthorized response expected by the frontend.
Exercise slow and failing states
Add fixed latency and a seeded probability of HTTP 503 responses. Runtime controls can adjust these settings while the local process is running.
PUT /_mock/config
content-type: application/json
{ "latency": 800, "errorRate": 0.2 }Restart after cloud changes
Save dashboard changes and restart the CLI to synchronize them. Local CRUD state persists while the configuration remains compatible.
Related questions
Can failures return a different status for every route?
Not currently. Global probabilistic failure injection returns HTTP 503; other statuses arise from validation, authentication, missing data, and relationship rules.
Keep exploring
Last updated September 17, 2026. Product behavior described here is verified against the current Mock API Studio runtime.