How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Postman Server Responses API

Operations for managing mock server responses and examples.

Postman Server Responses API is one of 51 APIs that Postman publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Server Responses. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 4 operations across 2 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.getpostman.com.

4 operations 2 paths 2 schemas 1 DELETE1 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.getpostman.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Postman Server Responses API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-api-key (apiKeyAuth). By default, every request must be authenticated.

  • apiKeyAuth — Postman API key for authentication.

Paths & Operations 4

Across 2 paths, the API surfaces 4 operations — 1 DELETE, 1 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Server Responses 4

Operations for managing mock server responses and examples.

GET
/mocks/{mockId}/serverResponses
Postman Get mock server responses
getMockServerResponses 1 param → 200401404429
POST
/mocks/{mockId}/serverResponses
Postman Create a server response
createServerResponse 1 param body → 200400401404429
PUT
/mocks/{mockId}/serverResponses/{serverResponseId}
Postman Update a server response
updateServerResponse 2 params body → 200401404429
DELETE
/mocks/{mockId}/serverResponses/{serverResponseId}
Postman Delete a server response
deleteServerResponse 2 params → 200401404429

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are ServerResponse (8 properties), ServerResponseInput (5 properties). Each schema is shown below with its type and property counts.

ServerResponse
object
A custom server response configured on a mock server.
8 properties
ServerResponseInput
object
5 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

postman-server-responses-api-openapi.yml Raw ↑

Other APIs Postman publishes across the network.

Postman Collections API
Postman Workspaces API
Postman Environments API
Postman Monitors API
Postman Webhooks API
Postman Tags API
Postman Billing API
Postman SCIM API
Postman MCP Server
Postman Flows
Postman Mocks API
Where this information came from

This is an independent, third-party profile of Postman Server Responses API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.