Postman API

Name: Postman API
Brand: Postman API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsTesting QaapiKey57 EndpointsREST

For Agents

Manage Postman collections, environments, mocks, monitors, and API schemas across a workspace through an account-scoped X-Api-Key.

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.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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

GET STARTED

Start building with Postman API

Explore with Jentic

View OpenAPI Document

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.

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

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

POST

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Postman X-Api-Key values are stored encrypted in the Jentic vault. Agents receive a scoped credential reference and the raw key never enters the prompt or logs.

Intent-based discovery

Agents search by intent such as 'create postman monitor' and Jentic returns the matching Postman operation along with its input schema.

Time to first call

Direct Postman integration: 2-3 days to wire collection management, monitor scheduling, and rate-limit handling. Through Jentic: under an hour to search, load, and execute.

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.

Postman API

Connect the Postman API to your agent

Capabilities

Start building with Postman API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs