ceven

Postman

Automates the creation and management of API collections, environments, and mock servers to keep your documentation in sync with your code.

Try Postman in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Postman integration

    • Describe the outcome and Ceven picks the right Postman calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Postman data, across all 126 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Postman access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Postman, when, and on whose behalf.
    • The agent pauses and asks when Postman is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Postman.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Postman action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Postman, and when to use it.

Create collection
Use this when you need to start a new group of requests in a specific workspace for a new project or API version.
Create request
Add a new API call with a specific method and URL to an existing collection.
Create environment
Use this to set up a new set of variables for different deployment stages like development or production.
Create mock server
Provision a server that simulates API responses based on your saved examples to unblock frontend teams.
Create monitor
Set up a scheduled run of a collection using cron expressions to track API uptime and performance.
Create API
Initialize a new API definition in a workspace with a name and summary.
Create API schema
Upload an OpenAPI or GraphQL schema to an existing API to define the contract.
Create workspace
Create a new team or personal workspace to isolate project resources.
Create pull request
Propose changes from a forked collection to be merged back into the parent collection.
Create webhook
Set up a webhook endpoint that triggers a specific collection run when called.
Create folder
Organize requests within a collection by grouping them into a new folder.
Create response
Save a specific response example to a request to power mock servers and documentation.
Delete collection
Permanently remove a collection that is no longer needed from the workspace.
Delete environment
Remove an environment and its associated variables from the workspace.
Create a Collection
Tool to create a new Postman collection in a specific workspace or the default workspace. Use when you need to create a collection with workspace specification. For complete collection format details, refer to the Postman Collection Format
Create a Collection Comment
Tool to create a comment on an API's collection. Use when you need to add a comment to a specific collection within an API. To create a reply on an existing comment, include the thread_id in the request.
Create Collection from Schema
Tool to create a collection from a schema and link it to an API with specified relations. Note: This endpoint is deprecated in Postman v10 and higher. Use when you need to generate a collection from an API schema and establish relations lik
Create a Folder
Tool to create a folder in a Postman collection. Use when you need to organize requests by creating a new folder within a collection. For complete details, see the Postman Collection Format documentation.
Create a Folder Comment
Tool to create a comment on a folder. Use when you need to add a comment to a specific folder in a collection.
Create a Fork
Tool to create a fork from an existing collection into a workspace. Use when you need to fork a collection to create an independent copy in a specific workspace.
Create Environment Fork
Tool to create a fork from an existing environment into a workspace. Use when you need to fork an environment to a specified workspace.
Create a Mock Server
Tool to create a new mock server in a Postman collection. Use when you need to create a mock server to simulate API endpoints for testing or development. Returns the created mock server's details including the mockUrl which can be used to m
Create a Monitor
Tool to create a new monitor in a specific workspace to run a collection on a schedule. Use when you need to set up automated collection runs at specified intervals using cron expressions within a workspace.
Create an API
Tool to create a new API in Postman. Use when you need to create an API with a name, summary, and description in your Postman workspace.
Create an Environment
Tool to create a new environment in a Postman workspace. Use when you need to create a new environment with variables for different settings (development, production, testing, etc.). Returns the created environment's ID, name, and UID upon
Create a Pull Request
Tool to create a pull request for a forked collection into its parent collection. Use when you need to propose changes from a forked collection to be merged into the parent collection. The forked collection must exist before creating a pull
Create Request in Collection
Tool to create a new request in a Postman collection. Use when you need to add a request to an existing collection with specified method, URL, headers, and body.
Create a Request Comment
Tool to create a comment on a request. Use when you need to add a comment to a specific request within a collection or reply to an existing comment thread.
Create a Response
Tool to create a request response in a Postman collection. Use when you need to add a saved response example to a specific request in a collection.
Create a Response Comment
Tool to create a comment on a response. Use when you need to add a comment to a specific response within a collection or reply to an existing comment thread.

30 actions · scroll to see them all

Frequently asked questions

Ceven uses the Postman API key for authentication. You generate a secret key from your Postman account settings and provide it to Ceven. This key is stored in an encrypted vault and is never exposed to the model or other users. Every request the agent makes to the Postman API includes this key in the header to verify your identity and permissions. If you suspect the key has been compromised, you can revoke it instantly from the Postman dashboard, which will stop all Ceven agents from making changes until a new key is provided. This ensures you maintain full control over who can modify your collections and environments.
Yes, as long as the API key provided has the necessary permissions for those workspaces. Ceven can create, edit, and delete resources across any workspace where the authenticated user has administrator or editor rights. If you are using a team workspace, the agent respects the existing role based access control set up within Postman. This means if your account cannot delete a collection in a specific team folder, the Ceven agent will also receive a forbidden error from the Postman API. This preserves your internal governance and prevents accidental deletion of critical team assets by the AI agent.
The Postman API has strict rate limits that vary based on your plan level. For example, free tier accounts have much lower limits on the number of requests per second compared to enterprise accounts. Ceven includes a built in retry mechanism with exponential backoff to handle rate limit errors. If the agent hits a 429 Too Many Requests response, it will pause and wait before attempting the action again. However, for very large migrations involving thousands of requests, you may notice a slower pace as the agent ensures it does not trigger a permanent block from the Postman API gateway.
Yes, Ceven can provision mock servers and link them to specific collections. The agent can also create the specific response examples required for the mock server to return meaningful data. For instance, you can tell the agent to create a mock server that returns a 200 OK for valid users and a 401 Unauthorized for invalid tokens. The agent will create the corresponding examples in the collection and then spin up the mock server. This is particularly useful for parallel development where the frontend team needs a stable API contract before the backend logic is fully implemented.
Ceven can use the Postman API to create a new API definition and upload a schema file. It supports the most common formats including OpenAPI 3.0 and GraphQL. Once the schema is uploaded, the agent can trigger the creation of a collection based on that schema. This allows you to maintain a single source of truth in a YAML file and have the agent ensure that the Postman collections used by your QA team are always perfectly aligned with the technical specification, removing the need for manual imports.
The agent can create new environments and set key value pairs for variables. This is useful for managing different base URLs or API keys across development, staging, and production. When you ask the agent to set up a new environment, it can pull the required values from your secret manager or a configuration file and push them into Postman. It can also update existing variables in real time, ensuring that your automated tests always point to the correct version of your infrastructure without manual intervention.
Ceven can create and configure monitors to run collections on a schedule. While the actual execution of the monitor happens on Postman servers, the agent can be used to set up the monitor and then pull the results of the runs via the API. You can build a workflow where Ceven checks the monitor status every hour and sends a summary of any failed tests to a specific channel. This turns Postman into a proactive alerting system rather than just a reactive testing tool.
Yes, the agent can create a fork of an existing collection into a different workspace. This is a powerful feature for managing version control within Postman. You can have the agent fork a master collection into a feature branch workspace, allow developers to make changes, and then use the agent to create a pull request back into the main collection. This mirrors the git workflow and ensures that changes to your API tests are reviewed and approved before they become part of the official test suite.

Alternatives to Postman

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Insomnia logoInsomniaHoppscotch logoHoppscotchPaw logoPaw

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Postman and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free