Sanaf AI
Start free
Developer Tools

Postman, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Postman account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Developer Tools
  • Connects with a key
  • 98 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Postman is

Postman is an API platform for building, testing, and managing APIs with powerful collaboration features.

You paste in a key from your own Postman account. It is kept encrypted, and you can withdraw it from inside Postman whenever you like.

How a run works

One message in, the work done in Postman.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Postman. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Postman account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

98 tools it already has

What it can do in Postman

These are the ready-made tools your AI employee already has in Postman. It is not limited to them, but it never has to be taught these.

  • Create a CollectionTool 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 collec
  • Create a Collection CommentTool 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 th
  • Create a FolderTool 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 Collecti
  • Create a Folder CommentTool to create a comment on a folder. Use when you need to add a comment to a specific folder in a collection.
  • Create a ForkTool 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 a Mock ServerTool 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 s
  • Create a MonitorTool 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 expr
  • Create a Pull RequestTool 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 collect
  • Create a Request CommentTool 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 ResponseTool 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 CommentTool 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.
  • Create a SpecTool to create an API specification in Postman's Spec Hub. Use when you need to create single or multi-file specifications in a workspace. Supports various spec types including Ope
  • Create a WebhookTool to create a webhook that triggers a collection with a custom payload. Use when you need to set up a webhook endpoint that can trigger a Postman collection run. The webhook URL
  • Create a WorkspaceTool to create a new workspace in Postman. Use when you need to create a workspace with a specified name, type (personal, team, private, or public), and optional description. Retur
  • Create an APITool 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 EnvironmentTool 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.
  • Create API SchemaTool to create a schema for an API in Postman. Use when you need to add a schema definition (such as OpenAPI, GraphQL, or Protocol Buffers) to an existing API. The schema can consi
  • Create API Version RelationsTool to create new relations for an API version. Use when you need to link collections or mock servers to an API version as contract tests, test suites, documentation, or mocks.
  • Create CollectionTool to create a new Postman collection with specified name and configuration. Use when you need to create a new collection in Postman workspace. Returns the created collection's I
  • Create Collection from SchemaTool 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
  • Create EnvironmentTool to create a new Postman environment with specified name and variables. Use when you need to create a new environment in Postman workspace. Returns the created environment's ID
  • Create Environment ForkTool to create a fork from an existing environment into a workspace. Use when you need to fork an environment to a specified workspace.
  • Create Mock ServerTool to create a new mock server for a Postman collection. Use when you need to set up a mock server that simulates API responses based on saved examples in a collection.
  • Create Mock Server ResponseTool to create a server response on a Postman mock server. Use when you need to simulate 5xx server-level responses (500, 503, etc.) for testing error conditions.
  • Create MonitorTool to create a new monitor to run a collection on a schedule. Use when you need to set up automated collection runs at specified intervals using cron expressions.
  • Create or Update a Schema FileTool to create or update an API schema file in Postman. Use when you need to add a new schema file or modify an existing one within an API schema. Requires API ID, schema ID, file
  • Create Request in CollectionTool 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 Spec FileTool to create a new file in an API specification. Use when you need to add a new file (such as schema definitions, path configurations, or components) to an existing spec.
  • Create WebhookTool to create a new webhook for a Postman collection. Use when you need to create a webhook that triggers a collection when called. Returns the created webhook's ID and name upon
  • Delete a CollectionTool to permanently delete a collection from Postman. Use when you need to remove a collection that is no longer needed.
  • Delete a collection's commentTool to delete a comment from an API's collection. Use when you need to remove a specific comment from a collection. On success, returns HTTP 204 No Content.
  • Delete a FolderTool to delete a folder in a Postman collection. Use when you need to remove a folder and all its contents from a collection. The folder ID should not contain spaces to avoid 404 e
  • Delete a Folder's CommentTool to delete a comment from a folder. Use when you need to remove a specific comment from a folder. Returns HTTP 204 No Content on successful deletion.
  • Delete a Request's CommentTool to delete a comment from a request. Use when you need to remove a specific comment from a request. On success, this returns an HTTP 204 No Content response.
  • Delete a ResponseTool to delete a response in a Postman collection. Use when you need to remove a saved response from a collection.
  • Delete a Response's CommentTool to delete a comment from a response. Use when you need to remove a specific comment from a collection response. On successful deletion, this returns HTTP 204 No Content.
  • Delete a Schema FileTool to delete a file in an API schema. Use when you need to remove a specific file from a schema. On success, returns HTTP 204 No Content response.
  • Delete a SpecTool to delete an API specification from Postman. Use when you need to permanently remove a specification. On success, returns HTTP 204 No Content response.
  • Delete a WorkspaceTool to delete a Postman workspace permanently. Use when you need to remove a workspace and all its contents. Deletion is permanent and cannot be undone.
  • Delete an APITool to delete an API from Postman. Use when you need to permanently remove an API. On success, returns HTTP 204 No Content response.
  • Delete an API's CommentTool to delete a comment from an API. Use when you need to remove a comment from a specific API. On success, this returns an HTTP 204 No Content response indicating the comment was
  • Delete an environmentTool to delete an environment permanently in Postman. Use when you need to remove an environment that is no longer needed.
  • Delete Mock Server ResponseTool to delete a mock server's server response. Use when you need to remove a specific response from a Postman mock server.
  • Delete MonitorTool to delete a monitor by its ID. Use when you need to permanently remove a monitor from Postman. The monitor ID must be provided to identify which monitor to delete.
  • Delete Spec FileTool to delete a file from an API specification. Use when you need to remove a specific file from a multi-file specification.
  • Duplicate a CollectionTool to create a duplicate of a collection in another workspace. Use when you need to copy an existing collection to a different workspace. Returns an asynchronous task that can be
  • Fork CollectionTool to create a fork of a collection in a specified workspace. Use when you need to fork an existing collection to a workspace.
  • Generate Collection from SpecTool to generate a Postman collection from an OpenAPI 2.0, 3.0, or 3.1 specification. Use when you need to create a collection from an existing API spec. The operation is asynchron
  • Generate Spec from CollectionTool to generate an API specification from a Postman collection. Use when you need to create an OpenAPI 3.0 specification from an existing collection. The operation is asynchronous
  • Get All API ReleasesTool to get all releases for a specific API version in Postman. Use when you need to list releases for an API version. Note: This endpoint is deprecated in Postman v10 and higher.
  • Get All API SpecificationsTool to get all API specifications in a workspace. Use when you need to list or retrieve API specs from a specific Postman workspace. Returns an array of spec objects with their ID
  • Get All API VersionsTool to get all published versions of a specific API in Postman. Use when you need to list or retrieve version information for an API. Returns an array of version objects with thei
  • Get All APIsTool to get all APIs accessible to the authenticated user with optional workspace filtering. Use when you need to list or retrieve APIs from Postman. Returns an array of API object
  • Get All APIs in WorkspaceTool to get all APIs in a specific Postman workspace. Use when you need to list or retrieve APIs from a workspace. Returns an array of API objects with their details.
  • Get All CollectionsTool to get all collections accessible to the authenticated user with optional workspace filtering. Use when you need to list or retrieve collections from Postman. Returns an array
  • Get All EnvironmentsTool to get all environments accessible to the authenticated user with optional workspace filtering. Use when you need to list or retrieve environments from Postman. Returns an arr
  • Get All Forked CollectionsTool to retrieve all forked collections for the authenticated user. Use when you need to list or access all collections that the user has forked.
  • Get All GroupsTool to get all user groups in a Postman team. Use when you need to list all groups and their details including member counts and timestamps. Returns an array of group objects with
  • Get All Linked RelationsTool to retrieve all linked relations for a specific API version in Postman. Use when you need to discover what collections, documentation, mocks, or monitors are linked to an API
  • Get All Mock ServersTool to get all active mock servers accessible to the authenticated user. Use when you need to list or retrieve mock servers from Postman. By default, returns only mock servers you
  • Get All MonitorsTool to get all monitors accessible to the authenticated user with optional workspace filtering. Use when you need to list or retrieve monitors from Postman. Returns an array of mo
  • Get All Team UsersTool to get information about all users on the Postman team. Use when you need to list all team members and their details including roles and join dates. Returns an array of user o
  • Get All Test RelationsTool to retrieve all test relations for a specific API version. Use when you need to get test relations associated with an API version. Note: This endpoint is deprecated in Postman
  • Get All Workspace RolesTool to get information about all roles in a workspace based on the team's plan. Use when you need to retrieve the IDs of all users with different roles (Editor, Admin, Viewer) in
  • Get All WorkspacesTool to get all workspaces accessible to the authenticated user with optional type filtering. Use when you need to list or retrieve workspaces from Postman. Returns an array of wor
  • Get an EnvironmentTool to retrieve detailed information about a specific environment in Postman. Use when you need to fetch environment details including name, ID, owner, and all environment variabl
  • Get API CommentsTool to retrieve all comments left by users in an API. Use when you need to fetch all comments associated with a specific API.
  • Get API InformationTool to retrieve information about a specific API in Postman. Use when you need to fetch API details including name, description, versions, and schemas.
  • Get API SchemaTool to retrieve information about an API schema from Postman. Use when you need to fetch schema details for a specific API. Optionally specify a version ID to get a schema publish
  • Get API SpecificationTool to retrieve information about an API specification in Postman. Use when you need to fetch spec details including name, type, and timestamps.
  • Get API VersionTool to get information about a specific API version in Postman. Use when you need to retrieve details about a particular version of an API. Returns version details including ID, n
  • Get Async Collection Update StatusTool to get the status of an asynchronous collection update task. Use when you need to check whether a previously initiated async collection update is still processing, has complet
  • Get Authenticated UserTool to get information about the authenticated user. Use when you need to retrieve details about the current authenticated user, including their user ID, username, and email addre
  • Get Billing Account DetailsTool to retrieve Postman billing account details for the authenticated team. Use when you need to access account information such as account ID, team ID, account state, billing slo
  • Get Collection Access KeysTool to retrieve all personal and team collection access keys for the authenticated user. Use when you need to list or manage collection access keys. Returns an array of access key
  • Get Collection CommentsTool to retrieve all comments left by users in an API's collection. Use when you need to fetch all comments associated with a specific collection within an API.
  • Get Collection Pull RequestsTool to get information about a collection's pull requests including source and destination IDs, status, and URLs. Use when you need to retrieve pull request details for a specific
  • Get Collection RolesTool to get information about all roles in a collection. Use when you need to retrieve the IDs of all users, teams, and groups with access to view or edit a collection.
  • Get Collection's ForksTool to get all forks of a specific collection. Use when you need to retrieve information about who has forked a collection, including fork IDs, users, and creation dates.
  • Get Contract Test RelationsTool to retrieve contract test relations for a specific API version. Use when you need to check contract test associations. Note: This endpoint is deprecated and may return limited
  • Get documentation relationsTool to get documentation relations for a specific API version. This endpoint is deprecated in Postman v10 and higher.
  • Get Duplication Task StatusTool to get the status of a collection duplication task. Use when you need to check whether a previously initiated collection duplication is still processing or has completed. The
  • Get Environment ForksTool to retrieve all forked environments for a specific environment. Use when you need to list all environments that have been forked from a particular environment.
  • Get Folder CommentsTool to retrieve all comments left by users in a folder. Use when you need to fetch all comments associated with a specific folder within a collection.
  • Get Folder InformationTool to retrieve information about a folder in a Postman collection. Use when you need to fetch details about a specific folder including its name, description, owner, and timestam
  • Get Monitor InformationTool to retrieve information about a specific monitor in Postman. Use when you need to fetch monitor details including schedule, collection, environment, and run status.
  • Get Request CommentsTool to retrieve all comments left by users in a request. Use when you need to fetch all comments associated with a specific request within a collection.
  • Get Request InformationTool to retrieve information about a specific request in a Postman collection. Use when you need to fetch details about a request including its method, URL, headers, body, authenti
  • Get Response CommentsTool to retrieve all comments left by users in a response. Use when you need to fetch all comments associated with a specific response within a collection.
  • Get Response InformationTool to retrieve information about a saved response in a Postman collection. Use when you need to fetch details about a specific response including status, headers, body, and metad
  • Get Spec DefinitionTool to get the complete contents of an API specification's definition. Use when you need to retrieve the full OpenAPI/Swagger specification content for a spec. Returns the raw def
  • Get Spec File ContentsTool to get the contents of an API specification's file. Use when you need to retrieve the actual content and metadata of a specific file within a spec.
  • Get Spec's Generated CollectionsTool to retrieve all collections generated from an API specification in Postman. Use when you need to fetch collections that have been auto-generated from a spec. Returns metadata
  • Get Specification FilesTool to retrieve all files in an API specification from Postman. Use when you need to list or view specification files for a specific spec ID. Returns file metadata including IDs,
  • Get Team UserTool to get information about a user on the Postman team. Use when you need to retrieve details about a specific team member including their ID, name, email, roles, and join date.
  • Get Workspace Activity FeedTool to get a workspace's activity feed showing who added or removed collections, environments, or elements, and users joining or leaving. Use when you need to track workspace chan
  • Get Workspace DetailsTool to get detailed information about a specific workspace by its ID. Use when you need to retrieve the complete structure of a workspace including all collections, environments,
  • Get Workspace RolesTool to get the roles of users, user groups, and partners in a workspace. Use when you need to retrieve role assignments and understand who has what level of access to a specific w
Access, and who is in charge of it

You stay the boss of your Postman account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Postman account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Postman is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Postman and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about Postman

Can an AI employee really work inside Postman?
Yes. It signs in to your own Postman account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Postman?
No. Nothing moves and nothing is replaced. Your records stay in Postman, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Postman account?
You paste in a key from your own Postman account. It is kept encrypted, and you can withdraw it from inside Postman whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Postman?
It has 98 ready-made tools in Postman today, among them Create a Collection, Create a Collection Comment and Create a Folder. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Postman and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Postman and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Postman?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Postman is written down with what it did and when.