Getpostman Postman API
64
AI ReadinessAI-Aware (B)64/100
Community OpenAPI document · agent-readyDeveloper ToolsTesting QaapiKey57 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Manage Postman collections, environments, mocks, monitors, and API schemas across a workspace through an account-scoped X-API-Key.
Use for: I need to create a new Postman collection from a JSON definition, List all environments in my Postman workspace, Set up a mock server for the 'staging' collection, Schedule a monitor that runs my smoke-test collection every hour
Not supported: Does not handle source-control hosting, deployment pipelines, or runtime traffic capture - use for managing Postman collections, mocks, monitors, and API schemas only.
The Postman API is the programmatic surface to a Postman workspace, exposing collections, environments, mocks, monitors, APIs, schemas, and webhooks behind a single account-scoped key. It covers 57 endpoints that let teams script collection authoring, version their API definitions, manage mock servers and scheduled monitors, and retrieve schema relations to keep contracts and tests in sync. It is the canonical control plane for orchestrating CI-time API testing, mock-driven development, and API governance across a Postman workspace.
Install Jentic One Beta
Connect the Postman API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Postman API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgetpostman.com%2Fgetpostman" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgetpostman.com%2Fgetpostman" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Postman API.
Create, fetch, update, and fork Postman collections under a workspace
Manage environment variable sets that drive collection runs
Spin up and tear down mock servers backed by a collection or schema
Schedule monitors that run a collection and report results back
Register an API in Postman, version it, and attach contract test, integration test, and documentation relations
Upload and update OpenAPI or RAML schemas attached to an API version
Use Cases
Patterns agents use Postman API for, with concrete tasks.
★ CI-driven contract testing
Engineering teams keep their OpenAPI source of truth in Postman and run contract tests on every pull request. The API lets a CI job upload the latest schema to the API version, link the contract-test collection, and trigger a monitor run, then read results back to gate the merge.
Upload openapi.json to API version v2 of API id abc123 and trigger the linked contract-test monitor
Mock-first frontend development
Frontend teams build against a Postman mock server while the backend is still landing. The API creates the mock from a collection, returns the mock URL, and lets the team rotate or update the mock as the contract evolves without touching the frontend codebase.
Create a mock named 'payments-mock-staging' bound to collection xyz789 and return the mock URL
Workspace governance audit
Platform teams audit a workspace by listing every collection, environment, monitor, and registered API to flag stale assets. The API exposes each resource type with stable identifiers, so the audit job can compare current state to a previous snapshot and surface drift such as orphaned mocks or unused environments.
List every collection, environment, and monitor in workspace ws123 and produce a CSV of items not modified in the last 90 days
AI agent test orchestration
An AI agent connected through Jentic accepts a request like 'run the payments smoke tests against staging', resolves it to a Postman collection plus environment, and triggers a monitor run. Jentic injects the X-API-Key so the agent never holds the workspace credential directly.
Find the collection named 'payments-smoke', bind environment 'staging', and create a one-shot monitor run
Key Endpoints
57 endpoints — the postman api is the programmatic surface to a postman workspace, exposing collections, environments, mocks, monitors, apis, schemas, and webhooks behind a single account-scoped key.
METHOD
PATH
DESCRIPTION
GET
/collections
List all collections in the workspace
POST
/collections
Create a new collection
POST
/mocks
Create a mock server
POST
/monitors
Schedule a collection monitor
POST
/apis
Register a new API
POST
/apis/{apiId}/versions/{apiVersionId}/schemas
Attach a schema to an API version
GET
/environments
List environments
GET
/collections
List all collections in the workspace
POST
/collections
Create a new collection
POST
/mocks
Create a mock server
POST
/monitors
Schedule a collection monitor
POST
/apis
Register a new API
POST
/apis/{apiId}/versions/{apiVersionId}/schemas
Attach a schema to an API version
GET
/environments
List environments
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
P
Postman API
- AI-Aware (B)64/100
93
Foundational Compliance72
Developer Experience & Jentic Compatibility37
AI-Readiness & Agent Experience93
Agent Usability100
Security65
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
93
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
97%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
75%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
72
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: A-Signals: 4
57%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
32%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
37
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
13%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
35%
Summary Coverage
Coverage of summaries across operations/tags/info.
93
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
93%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
100
Security
Trust, risk posture, and security compliance.
Grade: A+Signals: 1
100%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
65
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: BSignals: 1
65%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Postman by hand means setting its API-key request header and shaping payloads for collections, mocks, monitors, environments, and API schemas across many endpoints yourself. Through Jentic you install once, import the Postman API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Postman exposes collections, mocks, monitors, and environments largely as top-level resources, so you limit the agent to the operations it needs, such as listing collections or creating a monitor. Because you pick the operation set, writes like creating a collection are not reachable unless you add them.
Credential isolation
Your Postman API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a Postman monitor' or 'list collections', and Jentic returns the matching Postman operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Postman API through Jentic.
What authentication does the Postman API use?
Postman uses an account-scoped API key sent as the X-API-Key request header. The same key is also accepted as an apikey query parameter, with the header taking precedence when both are present. Through Jentic the key is vaulted and injected per request.
Can I create a collection through the Postman API?
Yes. POST /collections accepts a Postman collection JSON document and returns the new collection's identifier. Subsequent updates use PUT /collections/{collectionId}, and a fork operation is available via POST /collections/fork/{collectionId}.
What are the rate limits for the Postman API?
The Postman API enforces 60 requests per minute per API key. Every response includes X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers; if you exceed the quota you get a 429 response and should back off until the reset epoch.
How do I run a collection on a schedule through Jentic?
Search Jentic for 'create postman monitor', load the POST /monitors schema, then execute with the collection identifier and an interval. Jentic handles the X-API-Key injection and returns the monitor identifier you can poll later.
Can I attach an OpenAPI schema to a Postman API version?
Yes. POST /apis/{apiId}/versions/{apiVersionId}/schemas uploads a schema document, and PUT on the same path with a schema id replaces it. The sync endpoint at /apis/{apiId}/versions/{apiVersionId}/{entityType}/{entityId}/syncWithSchema regenerates linked entities such as collections from the new schema.
Is the Postman API free?
Access is included with Postman accounts, with usage caps that scale up on paid plans. Heavy automation, large workspaces, and high-frequency monitors typically require a paid tier - check the Postman pricing page for the current per-plan API call allowances.
Can I limit what my agent is allowed to do with the Postman API?
Yes. Because Jentic One is self-hosted, you decide which Postman operations your agent can reach, and Postman exposes collections, mocks, monitors, and environments as top-level resources you can select individually. You might allow only read operations like listing collections or environments while withholding writes such as creating a collection or scheduling a monitor. Any operation you do not add to the agent's set stays out of reach, and your stored API key is injected at execution time rather than exposed to the agent.
GET STARTED