Delays on the front- or back-end make it difficult for dependent teams to complete their work efficiently. Postman's mock servers can alleviate those delays in the development process.
Before sending an actual request, front-end developers can create a mock server to simulate each endpoint and its corresponding response in a Postman Collection. Developers can view potential responses, without spinning up a back end.
Creating a mock example during the earliest phase of API development fosters clear communication among team members and aligns their expectations.
As a result, all teams in the development process can work in parallel; and dependent teams experience fewer delays.
Postman lets you create two types of mock servers: private and public.
Private mock servers require users to add a Postman API key in the request header
x-api-key:<your postman API key>.
If you create a private mock server, users can share the underlying collection with the team or specific team members, and provide permissions to edit or view. Your team members can use their Postman API keys to consume the mock. Team members can use the mock if they have permissions to access the underlying collection.
Mock servers are public by default. Public mock servers are accessible to anyone. When you share a public mock server, users don’t need to add a Postman API key.
For more information about mock servers, see: