Adding a pause to your mock API is an easy way to check loading indicators, catch timeout issues, or explore performance edge-cases. Mockoon lets you set those pauses—per route and globally—in just a few clicks.
Need a mock server first?
Check out my previous Club post “Have you tried Mockoon to capture and mock real API responses?” for instructions.
Your task
- Open your existing Mockoon server
- Add a delay to one specific route.
- Select the route.
- In the Response panel, set Response delay (ms) to something noticeable, e.g.
2000
.
- Add a global delay for all other routes.
- Go to Environment → Settings.
- Set Latency to a different value, e.g.
1000
.
-
Start the server and exercise your application or API client.
Refresh a few times and watch how calls with the route-specific delay compare to everything else. -
Share your experience and thoughts in the thread:
- Which delays did you set, and why?
- **How did your application behave with those delays?
- Where could latency simulation be useful in your own testing?
Post your thoughts or questions below. Someone else is probably experimenting with the same settings.