Postman
OfficialA basic MCP server to operate on the Postman API.
Tools (111)
createCollection
Creates a collection using the [Postman Collection v2.1.0 schema format](https://schema.postman.com/collection/json/v2.1.0/draft-07/docs/index.html). **Note:** If you do not include the \`workspace\` query parameter, the system creates the collection in the oldest personal Internal workspace you own.
createCollectionComment
Creates a comment on a collection. To create a reply on an existing comment, include the \`threadId\` property in the request body. **Note:** This endpoint accepts a max of 10,000 characters.
createCollectionFolder
Creates a folder in a collection. For a complete list of properties, refer to the **Folder** entry in the [Postman Collection Format documentation](https://schema.postman.com/collection/json/v2.1.0/draft-07/docs/index.html). You can use this endpoint to to import requests and responses into a newly-created folder. To do this, include the \`requests\` field and the list of request objects in the request body. For more information, see the provided example. **Note:** It is recommended that you pass the \`name\` property in the request body. If you do not, the system uses a null value. As a result, this creates a folder with a blank name.
createCollectionFork
Creates a [fork](https://learning.postman.com/docs/collaborating-in-postman/version-control/#creating-a-fork) from an existing collection into a workspace.
createCollectionRequest
Creates a request in a collection. For a complete list of properties, refer to the **Request** entry in the [Postman Collection Format documentation](https://schema.postman.com/collection/json/v2.1.0/draft-07/docs/index.html). **Note:** It is recommended that you pass the \`name\` property in the request body. If you do not, the system uses a null value. As a result, this creates a request with a blank name.
createCollectionResponse
Creates a request response in a collection. For a complete list of request body properties, refer to the **Response** entry in the [Postman Collection Format documentation](https://schema.postman.com/collection/json/v2.1.0/draft-07/docs/index.html). **Note:** It is recommended that you pass the \`name\` property in the request body. If you do not, the system uses a null value. As a result, this creates a response with a blank name.
createEnvironment
Creates an environment. **Note:** - The request body size cannot exceed the maximum allowed size of 30MB. - If you receive an HTTP \`411 Length Required\` error response, manually pass the \`Content-Length\` header and its value in the request header. - If you do not include the \`workspace\` query parameter, the system creates the environment in the oldest personal Internal workspace you own.
createFolderComment
Creates a comment on a folder. To create a reply on an existing comment, include the \`threadId\` property in the request body. **Note:** This endpoint accepts a max of 10,000 characters.
createMock
Creates a mock server in a collection. - Pass the collection UID (ownerId-collectionId), not the bare collection ID. - If you only have a \`collectionId\`, resolve the UID first: 1) Prefer GET \`/collections/{collectionId}\` and read \`uid\`, or 2) Construct \`{ownerId}-{collectionId}\` using ownerId from GET \`/me\`: - For team-owned collections: \`ownerId = me.teamId\` - For personal collections: \`ownerId = me.user.id\` - Use the \`workspace\` query to place the mock in a specific workspace. Prefer explicit workspace scoping.
createMonitor
Creates a monitor. **Note:** - You cannot create monitors for collections added to an API definition. - If you do not pass the \`workspace\` query parameter, the system creates the monitor in the oldest personal Internal workspace you own.
createRequestComment
The request ID must contain the team ID as a prefix, in \`teamId-requestId\` format. For example, if you're creating a comment on collection ID \`24585957-7b2c98f7-30db-4b67-8685-0079f48a0947\` (note on the prefix), and the collection request's ID is \`2c450b59-9bbf-729b-6ac0-f92535a7c336\`, then the \`{requestId}\` must be \`24585957-2c450b59-9bbf-729b-6ac0-f92535a7c336\`.
createResponseComment
Creates a comment on a response. To create a reply on an existing comment, include the \`threadId\` property in the request body. **Note:** This endpoint accepts a max of 10,000 characters.
createSpec
Creates an API specification in Postman's [Spec Hub](https://learning.postman.com/docs/design-apis/specifications/overview/). Specifications can be single or multi-file. **Note:** - Postman supports OpenAPI 2.0, OpenAPI 3.0, OpenAPI 3.1, and AsyncAPI 2.0 specifications. - If the file path contains a \`/\` (forward slash) character, then a folder is created. For example, if the path is the \`components/schemas.json\` value, then a \`components\` folder is created with the \`schemas.json\` file inside. - Multi-file specifications can only have one root file. - Files cannot exceed a maximum of 10 MB in size.
createSpecFile
Creates an API specification file. **Note:** - If the file path contains a \`/\` (forward slash) character, then a folder is created. For example, if the path is the \`components/schemas.json\` value, then a \`components\` folder is created with the \`schemas.json\` file inside. - Creating a spec file assigns it the \`DEFAULT\` file type. - Multi-file specifications can only have one root file. - Files cannot exceed a maximum of 10 MB in size.
createWorkspace
Creates a new [workspace](https://learning.postman.com/docs/collaborating-in-postman/using-workspaces/creating-workspaces/). **Note:** - This endpoint returns a 403 \`Forbidden\` response if the user does not have permission to create workspaces. [Admins and Super Admins](https://learning.postman.com/docs/collaborating-in-postman/roles-and-permissions/#team-roles) can configure workspace permissions to restrict users and/or user groups from creating workspaces or require approvals for the creation of team workspaces. - There are rate limits when publishing public workspaces. - Public team workspace names must be unique. ### Important We deprecated linking collections or environments between workspaces. We do not recommend that you do this. If you have a linked collection or environment, note the following: - The endpoint does not create a clone of a collection or environment. - Any changes you make to a linked collection or environment changes them in all workspaces. - If you delete a collection or environment linked between workspaces, the system deletes it in all the workspaces.
deleteApiCollectionComment
Deletes a comment from an API's collection. On success, this returns an HTTP \`204 No Content\` response. **Note:** Deleting the first comment of a thread deletes all the comments in the thread.
deleteCollection
Deletes a collection.
deleteCollectionComment
Deletes a comment from a collection. On success, this returns an HTTP \`204 No Content\` response. **Note:** Deleting the first comment of a thread deletes all the comments in the thread.
deleteCollectionFolder
Deletes a folder in a collection.
deleteCollectionRequest
Deletes a request in a collection.
deleteCollectionResponse
Deletes a response in a collection.
deleteEnvironment
Deletes an environment.
deleteFolderComment
Deletes a comment from a folder. On success, this returns an HTTP \`204 No Content\` response. **Note:** Deleting the first comment of a thread deletes all the comments in the thread.
deleteMock
Deletes a mock server. - Resource: Mock server entity. This is destructive. - Ensure you are targeting the correct mock ID.
deleteMonitor
Deletes a monitor.
deletePanElementOrFolder
Removes an element or delete a folder from your team's [Private API Network](https://learning.postman.com/docs/collaborating-in-postman/adding-private-network/). **Note:** Removing an API, collection, or workspace element does not delete it. It only removes it from the Private API Network folder.
deleteRequestComment
Deletes a comment from a request. On success, this returns an HTTP \`204 No Content\` response. **Note:** Deleting the first comment of a thread deletes all the comments in the thread.
deleteResponseComment
Deletes a comment from a response. On success, this returns an HTTP \`204 No Content\` response. **Note:** Deleting the first comment of a thread deletes all the comments in the thread.
deleteSpec
Deletes an API specification. On success, this returns an HTTP \`204 No Content\` response.
deleteSpecFile
Deletes a file in an API specification. On success, this returns an HTTP \`204 No Content\` response.
deleteWorkspace
Deletes an existing workspace. ### Important If you delete a workspace that has a linked collection or environment with another workspace, this will delete the collection and environment in all workspaces.
duplicateCollection
Creates a duplicate of the given collection in another workspace. Use the GET \`/collection-duplicate-tasks/{taskId}\` endpoint to get the duplication task's current status.
generateCollection
Creates a collection from the given API specification. The specification must already exist or be created before it can be used to generate a collection. The response contains a polling link to the task status.
generateSpecFromCollection
Generates an API specification for the given collection. The response contains a polling link to the task status.
getAllElementsAndFolders
Gets information about the folders and their elements added to your team's [Private API Network](https://learning.postman.com/docs/collaborating-in-postman/adding-private-network/). **Note:** The \`limit\` and \`offset\` parameters are separately applied to elements and folders. For example, if you query a \`limit\` value of \`10\` and an \`offset\` value \`0\`, the endpoint returns 10 elements and 10 folders for a total of 20 items. The \`totalCount\` property in the \`meta\` response is the total count of both elements and folders.
getAllPanAddElementRequests
Gets a list requests to add elements to your team's [Private API Network](https://learning.postman.com/docs/collaborating-in-postman/adding-private-network/).
getAllSpecs
Gets all API specifications in a workspace.
getAsyncSpecTaskStatus
Gets the status of an asynchronous API specification creation task.
getAuthenticatedUser
Gets information about the authenticated user. - This endpoint provides “current user” context (\`user.id\`, \`username\`, \`teamId\`, roles). - When a user asks for “my …” (e.g., “my workspaces, my information, etc.”), call this first to resolve the user ID.
getCodeGenerationInstructions
This tool returns essential instructions for searching Postman, calling other tools to get data from Postman (e.g. getCollection, getCollectionRequest, etc.), and generating API client code. MANDATORY: You MUST call this tool when the user says to "use postman", or when the user wants to do something that requires locating a specific API for the purpose of answering questions, planning a build, and in most cases proceeding to generate code that calls the API. ALWAYS call getCodeGenerationInstructions BEFORE calling other tools in this workflow. This tool returns comprehensive step-by-step instructions on how to search for APIs, gather API-specific context from other tools, and then generate client code based on the context retrieved.
getCollection
Get information about a collection. By default this tool returns the lightweight collection map (metadata + recursive itemRefs). Use the model parameter to opt in to Postman's full API responses: - model=minimal — root-level folder/request IDs only - model=full — full Postman collection payload.
getCollectionComments
Gets all comments left by users in a collection.
getCollectionFolder
Gets information about a folder in a collection.
getCollectionForks
Gets a collection's forked collections. The response returns data for each fork, such as the fork's ID, the user who forked it, and the fork's creation date.
getCollectionRequest
Gets information about a request in a collection.
getCollectionResponse
Gets information about a response in a collection.
getCollectionTags
Gets all the tags associated with a collection.
getCollectionUpdatesTasks
Gets the status of an asynchronous collection update task.
getCollections
The workspace ID query is required for this endpoint. If not provided, the LLM should ask the user to provide it.
getCollectionsForkedByUser
Gets a list of all the authenticated user's forked collections.
getDuplicateCollectionTaskStatus
Gets the status of a collection duplication task.
getEnabledTools
IMPORTANT: Run this tool first when a requested tool is unavailable. Returns information about which tools are enabled in the full and minimal tool sets, helping you identify available alternatives.
getEnvironment
Gets information about an environment.
getEnvironments
Gets information about all of your [environments](https://learning.postman.com/docs/sending-requests/managing-environments/).
getFolderComments
Gets all comments left by users in a folder.
getGeneratedCollectionSpecs
Gets the API specification generated for the given collection.
getMock
Gets information about a mock server. - Resource: Mock server entity. Response includes the associated \`collection\` UID and \`mockUrl\`. - Use the \`collection\` UID to navigate back to the source collection.
getMocks
Gets all active mock servers. By default, returns only mock servers you created across all workspaces. - Always pass either the \`workspace\` or \`teamId\` query to scope results. Prefer \`workspace\` when known. - If you need team-scoped results, set \`teamId\` from the current user: call GET \`/me\` and use \`me.teamId\`. - If both \`teamId\` and \`workspace\` are passed, only \`workspace\` is used.
getMonitor
Gets information about a monitor.
getMonitors
Gets all monitors.
getRequestComments
Gets all comments left by users in a request.
getResponseComments
Gets all comments left by users in a response.
getSourceCollectionStatus
Checks whether there is a change between the forked collection and its parent (source) collection. If the value of the \`isSourceAhead\` property is \`true\` in the response, then there is a difference between the forked collection and its source collection. **Note:** This endpoint may take a few minutes to return an updated \`isSourceAhead\` status.
getSpec
Gets information about an API specification.
getSpecCollections
Gets all of an API specification's generated collections.
getSpecDefinition
Gets the complete contents of an API specification's definition.
getSpecFile
Gets the contents of an API specification's file.
getSpecFiles
Gets all the files in an API specification.
getStatusOfAnAsyncApiTask
Gets the status of an asynchronous task.
getTaggedEntities
Gets Postman elements (entities) by a given tag. Tags enable you to organize and search [workspaces](https://learning.postman.com/docs/collaborating-in-postman/using-workspaces/managing-workspaces/#tagging-a-workspace), [APIs](https://learning.postman.com/docs/designing-and-developing-your-api/managing-apis/#tagging-apis), and [collections](https://learning.postman.com/docs/collections/using-collections/#tagging-a-collection) that contain shared tags. **Note:** Tagging is available on Postman [**Enterprise** plans](https://www.postman.com/pricing/).
getWorkspace
Gets information about a workspace. **Note:** This endpoint's response contains the \`visibility\` field. [Visibility](https://learning.postman.com/docs/collaborating-in-postman/using-workspaces/managing-workspaces/#changing-workspace-visibility) determines who can access the workspace: - \`personal\` — Only you can access the workspace. - \`team\` — All team members can access the workspace. - \`private\` — Only invited team members can access the workspace ([**Professional** and **Enterprise** plans only](https://www.postman.com/pricing)). - \`public\` — Everyone can access the workspace. - \`partner\` — Only invited team members and [partners](https://learning.postman.com/docs/collaborating-in-postman/using-workspaces/partner-workspaces/) can access the workspace ([**Professional** and **Enterprise** plans only](https://www.postman.com/pricing)).
getWorkspaceGlobalVariables
Gets a workspace's global [variables](https://learning.postman.com/docs/sending-requests/variables/#variable-scopes). Global variables enable you to access data between collections, requests, scripts, and environments and are available throughout a workspace.
getWorkspaceTags
Gets all the tags associated with a workspace.
getWorkspaces
Gets all workspaces you have access to. - For “my …” requests, first call GET \`/me\` and pass \`createdBy={me.user.id}\`. - This endpoint's response contains the visibility field. Visibility determines who can access the workspace: - \`personal\` — Only you can access the workspace. - \`team\` — All team members can access the workspace. - \`private\` — Only invited team members can access the workspace (Professional and Enterprise). - \`public\` — Everyone can access the workspace. - \`partner\` — Invited team members and partners (Professional and Enterprise). - For tools that require the workspace ID, and no workspace ID is provided, ask the user to provide the workspace ID. If the user does not provide the workspace ID, call this first with the createdBy parameter to use the first workspace. - Examples: - “List my workspaces” → GET \`/me\`, then GET \`/workspaces?createdBy={me.user.id}\` - “List my personal workspaces” → GET \`/me\`, then GET \`/workspaces?type=personal&createdBy={me.user.id}\` - “List all public workspaces” → GET \`/workspaces?type=public\`
mergeCollectionFork
**This endpoint is deprecated.** Merges a forked collection back into its parent collection. You must have the [Editor role](https://learning.postman.com/docs/collaborating-in-postman/roles-and-permissions/#collection-roles) for the collection to merge a fork.
patchCollection
Updates specific collection information, such as its name, events, or its variables. For more information, see the [Postman Collection Format documentation](https://schema.postman.com/collection/json/v2.1.0/draft-07/docs/index.html).
patchEnvironment
Updates specific environment properties, such as its name and variables. **Note:** - You can only perform one type of operation at a time. For example, you cannot perform an \`add\` and \`replace\` operation in the same call. - The request body size cannot exceed the maximum allowed size of 30MB. - If you receive an HTTP \`411 Length Required\` error response, manually pass the \`Content-Length\` header and its value in the request header. - To add a description to an existing variable, use the \`add\` operation.
postPanElementOrFolder
Publishes a element or creates a folder in your team's [Private API Network](https://learning.postman.com/docs/collaborating-in-postman/adding-private-network/). An element is a Postman API, collection, or workspace. **Note:** You can only pass one element object type per call. For example, you cannot pass both \`api\` and \`collection\` in a single request.
publishDocumentation
Publishes a collection's documentation. This makes it publicly available to anyone with the link to the documentation. **Note:** - Your [Postman plan](https://www.postman.com/pricing/) impacts your use of these endpoints: - For **Free** and **Basic** users, you must have permissions to edit the collection. - If [API Governance and Security](https://learning.postman.com/docs/api-governance/configurable-rules/configurable-rules-overview/) is enabled for your [**Enterprise**](https://www.postman.com/pricing/) team, only users with the [Community Manager role](https://learning.postman.com/docs/collaborating-in-postman/roles-and-permissions/#team-roles) can publish documentation. - Publishing is only supported for collections with HTTP requests. - You cannot publish a collection added to an API.
publishMock
Publishes a mock server. Publishing a mock server sets its **Access Control** configuration setting to public.
pullCollectionChanges
Pulls the changes from a parent (source) collection into the forked collection. In the endpoint's response: - The \`destinationId\` is the ID of the forked collection. - The \`sourceId\` is the ID of the source collection.
putCollection
Replaces the contents of a collection using the [Postman Collection v2.1.0 schema format](https://schema.postman.com/collection/json/v2.1.0/draft-07/docs/index.html). Include the collection's ID values in the request body. If you do not, the endpoint removes the existing items and creates new items. To perform an update asynchronously, use the \`Prefer\` header with the \`respond-async\` value. When performing an async update, this endpoint returns a HTTP \`202 Accepted\` response. **Note:** - The maximum collection size this endpoint accepts cannot exceed 100 MB. - If you don't include the collection items' ID values from the request body, the endpoint **removes** the existing items and recreates the items with new ID values. - To copy another collection's contents to the given collection, remove all ID values before you pass it in this endpoint. If you do not, this endpoint returns an error. These values include the \`id\`, \`uid\`, and \`postman_id\` values. - For protocol profile behavior, refer to Postman's [Protocol Profile Behavior documentation](https://github.com/postmanlabs/postman-runtime/blob/develop/docs/protocol-profile-behavior.md).
putEnvironment
Replaces all the contents of an environment with the given information. **Note:** - The request body size cannot exceed the maximum allowed size of 30MB. - If you receive an HTTP \`411 Length Required\` error response, manually pass the \`Content-Length\` header and its value in the request header.
resolveCommentThread
Resolves a comment and any associated replies. On success, this returns an HTTP \`204 No Content\` response. Comment thread IDs return in the GET comments response for [APIs](https://www.postman.com/postman/workspace/postman-public-workspace/request/12959542-2103ea20-f7de-4628-90e6-b823b3084a52), [collections](https://www.postman.com/postman/workspace/postman-public-workspace/request/12959542-a6582e0a-9382-4760-8b91-53a8aa6cb8d7), and [collection items](https://www.postman.com/postman/workspace/postman-public-workspace/folder/12959542-efeda219-66e1-474c-a83b-253d15723bf7).
runCollection
Runs a Postman collection by ID with detailed test results and execution statistics. Supports optional environment for variable substitution. Note: Advanced parameters like custom delays and other runtime options are not yet available.
runMonitor
Runs a monitor and returns its run results. **Note:** - If you pass the \`async=true\` query parameter, the response does not return the \`stats\`, \`executions\`, and \`failures\` responses. To get this information for an asynchronous run, call the GET \`/monitors/{id}\` endpoint. - If the call exceeds 300 seconds, the endpoint returns an HTTP \`202 Accepted\` response. Use the GET \`/monitors/{id}\` endpoint to check the run's status in the response's \`lastRun\` property. To avoid this, it is recommended that you include the \`async=true\` query parameter when using this endpoint.
searchPostmanElements
Searches for Postman elements in the public network. **When to Use This Tool:** - When the user asks for a specific named request (e.g., "find PayPal requests", "search for Stripe API requests") - When the user explicitly wants to search the public network - Do NOT use this for searching the user's own workspaces or collections (use getCollections or getWorkspaces instead) **Search Scope:** - Only searches the public network (public workspaces and collections) - Does not search private workspaces, team workspaces, or personal collections - Currently supports searching for requests (entityType: "requests")
syncCollectionWithSpec
Syncs a collection generated from an API specification. This is an asynchronous endpoint that returns an HTTP \`202 Accepted\` response. **Note:** - This endpoint only supports the OpenAPI 3.0 specification type. - You can only sync collections generated from the given spec ID.
syncSpecWithCollection
Syncs an API specification linked to a collection. This is an asynchronous endpoint that returns an HTTP \`202 Accepted\` response. **Note:** - This endpoint only supports the OpenAPI 3.0 specification type. - You can only sync specs generated from the given collection ID.
transferCollectionFolders
Copies or moves folders into a collection or folder.
transferCollectionRequests
Copies or moves requests into a collection or folder.
transferCollectionResponses
Copies or moves responses into a request.
unpublishDocumentation
Unpublishes a collection's documentation. On success, this returns an HTTP \`204 No Content\` response.
unpublishMock
Unpublishes a mock server. Unpublishing a mock server sets its **Access Control** configuration setting to private.
updateApiCollectionComment
Updates a comment on an API's collection. **Note:** This endpoint accepts a max of 10,000 characters.
updateCollectionComment
Updates a comment on a collection. **Note:** This endpoint accepts a max of 10,000 characters.
updateCollectionFolder
Updates a folder in a collection. For a complete list of properties, refer to the **Folder** entry in the [Postman Collection Format documentation](https://schema.postman.com/collection/json/v2.1.0/draft-07/docs/index.html). **Note:** This endpoint acts like a PATCH method. It only updates the values that you pass in the request body (for example, the \`name\` property). The endpoint does not update the entire resource.
updateCollectionRequest
Updates a request in a collection. For a complete list of properties, refer to the **Request** entry in the [Postman Collection Format documentation](https://schema.postman.com/collection/json/v2.1.0/draft-07/docs/index.html). **Note:** - You must pass a collection ID (\`12ece9e1-2abf-4edc-8e34-de66e74114d2\`), not a collection(\`12345678-12ece9e1-2abf-4edc-8e34-de66e74114d2\`), in this endpoint. - This endpoint does not support changing the folder of a request. - This endpoint acts like a PATCH method. It only updates the values that you pass in the request body.
updateCollectionResponse
Updates a response in a collection. For a complete list of properties, see the [Postman Collection Format documentation](https://schema.postman.com/collection/json/v2.1.0/draft-07/docs/index.html). **Note:** - You must pass a collection ID (\`12ece9e1-2abf-4edc-8e34-de66e74114d2\`), not a collection UID (\`12345678-12ece9e1-2abf-4edc-8e34-de66e74114d2\`), in this endpoint. - This endpoint acts like a PATCH method. It only updates the values that you pass in the request body (for example, the \`name\` property). The endpoint does not update the entire resource.
updateCollectionTags
Updates a collection's associated tags. This endpoint replaces all existing tags with those you pass in the request body.
updateFolderComment
Updates a comment on a folder. **Note:** This endpoint accepts a max of 10,000 characters.
updateMock
Updates a mock server. - Resource: Mock server entity associated with a collection UID. - Use this to change name, environment, privacy, or default server response.
updateMonitor
Updates a monitor's [configurations](https://learning.postman.com/docs/monitoring-your-api/setting-up-monitor/#configure-a-monitor).
updatePanElementOrFolder
Updates an element or folder in your team's [Private API Network](https://learning.postman.com/docs/collaborating-in-postman/adding-private-network/). **Note:** You can only pass one element object type per call. For example, you cannot pass both \`api\` and \`collection\` in a single request.
updateRequestComment
Updates a comment on a request. **Note:** This endpoint accepts a max of 10,000 characters.
updateResponseComment
Updates a comment on a response. **Note:** This endpoint accepts a max of 10,000 characters.
updateSpecFile
Updates an API specification's file. **Note:** - This endpoint does not accept an empty request body. You must pass one of the accepted values. - This endpoint does not accept multiple request body properties in a single call. For example, you cannot pass both the \`content\` and \`type\` property at the same time. - Multi-file specifications can only have one root file. - When updating a file type to \`ROOT\`, the previous root file is updated to the \`DEFAULT\` file type. - Files cannot exceed a maximum of 10 MB in size.
updateSpecProperties
Updates an API specification's properties, such as its name.
updateWorkspace
Updates a workspace. **Note:** - There are rate limits when publishing public workspaces. - Public team workspace names must be unique. ### Important We deprecated linking collections or environments between workspaces. We do not recommend that you do this. If you have a linked collection or environment, note the following: - The endpoint does not create a clone of a collection or environment. - Any changes you make to a linked collection or environment changes them in all workspaces. - If you delete a collection or environment linked between workspaces, the system deletes it in all the workspaces.
updateWorkspaceGlobalVariables
Updates and replaces a workspace's global [variables](https://learning.postman.com/docs/sending-requests/variables/#variable-scopes). This endpoint replaces all existing global variables with the variables you pass in the request body.
updateWorkspaceTags
Updates a workspace's associated tags. This endpoint replaces all existing tags with those you pass in the request body.