- Installing and updating
- Navigating Postman
- Sending your first request
- Managing your account
- Syncing your work
- Discovering templates
- Creating your first collection
- Creating a workspace
- Setting up your Postman app
- Importing and exporting data
- Troubleshooting app issues
- Building requests
- Authorizing requests
- Receiving responses
- Grouping requests in collections
- Using variables
- Managing environments
- Visualizing responses
- Specifying examples
- Using cookies
- Working with certificates
- Generating client code
- Troubleshooting requests
- Scripting in Postman
- Writing pre-request scripts
- Writing tests
- Using the Collection Runner
- Scheduling runs with monitors
- Building request workflows
- Importing data files
- Working with your team
- Defining roles
- Requesting access
- Sharing your work
- Your Private API Network
- Commenting on collections
- Versioning APIs
- Using version control
- Using the API Builder
- Managing and sharing APIs
- Validating APIs
- Monitoring your APIs
- Setting up a monitor
- Viewing monitor results
- Monitoring APIs and websites
- Set up integrations to receive alerts
- Running Postman monitors using static IPs
- Troubleshooting monitors
- Monitoring FAQs
- Analyzing with reports
- Documenting your API
- Authoring your docs
- Publishing your docs
- Viewing documentation
- Using custom domains
- Publishing templates
- Publishing to the API Network
- Submission guidelines
- Managing your team
- Purchasing Postman
- Configuring team settings
- Utilizing audit logs
- Onboarding checklist
- Migrating data between teams
- Intro to SSO
- Configuring SSO for a team
- Logging in to an SSO team
- Microsoft AD FS
- Custom SAML in Azure AD
- Custom SAML in Duo
- Custom SAML in GSuite
- Custom SAML in Okta
- Custom SAML in Onelogin
- Custom SAML in Ping Identity
- Migrating to the current version of Postman
- Developing with Postman utilities
- Postman API
- Echo API
- Collection SDK
- Postman Runtime library
- Code generator library
- Postman Collection conversion
You can validate your API schema in Postman, and validate your elements (documentation, tests, mock servers, monitors) against a schema. This helps keep your API well-defined and ensure that your elements are in sync with your schema. If there is a validation error on the schema or elements do not match it, Postman will present a list of issues that have been found, as well as fixes for these issues. You can then apply fixes to the API elements and revalidate them.
Validation is available for OpenAPI 3.0 schemas.
Postman will indicate validation errors on your API schema as you edit it in the Define tab.
The pane below the schema editing area will indicate issues—you can hide and show the error view as you work.
Each error will indicate the type, the line it occurs on, and details of the issue. You can also hover over the error inline in the editor to see information as you type.
Note that sometimes a single error in your schema will cause more than one issue to appear in the list. As you fix your errors you will see the validation issues disappear.
If there is an issue with your schema JSON or YAML syntax, you will see a warning—look for errors indicated in the editor and hover for more detail. Postman will only be able to validate your schema elements if the JSON or YAML is itself well-formed.
If there are no errors, Postman will indicate that your schema is valid.
This section outlines the pre-requisites for validating your elements against an API schema, when validations are triggered, and how to trigger one manually.
For validations to execute, you need the following elements in place:
- An API schema - see Defining an API
- API element(s) - this can be a mock server, documentation, tests, or a monitor
Once the validation is complete, a status will appear next to the element indicating a checkmark if no issues have been found, or a warning message stating
When you add a new element to an API, you need to trigger a validation to check it against the current API schema. The results of the validation will appear next to the element.
You can also trigger a new validation of your element manually in the following cases:
- Re-validating after editing your schema and/or your linked element
- Adding a new schema to an API that already has elements linked to it
You can do so by navigating to your element (eg. Test Suite), clicking the validation status, then Validate Again.
You can also trigger a validation from the issues list by clicking Validate again at the top-right of the page.
If you want your requests to be validated, your collection must be linked to an API.
Postman will validate a request when it is sent. If issues are found, you will see a warning message showing the number of issues next to the name of the request.
Validation is version-specific, and will be performed against the schema of the particular version of the API linked with the collection. If one version of a collection is linked to more than one version of an API, Postman will select the schema from the latest created version of API for validation.
If an issue arises when you run a request, click the warning message next to the name of the request (e.g. 1 issue). This will open a side-panel on the right indicating detailed information about which component of the request is affected and what the issue itself is:
- A direct link to the API against which the request is validated—click the link to open the API within the Postman app.
- More details on where the issue lies within the request.
You can click a specific issue to access the relevant request component.
If your issue relates to another element, navigate to your API by clicking APIs in the app sidebar, then select your API from the list. Open the tab containing the element you want to see issues for (either Develop, Test or Observe).
You will see a status indicating whether issues have been found during validation next to the element. If there are issues, view them by clicking Issues found > View issues. This will take you to a page on the web dashboard summarizing validation issues.
You can access the summary of validation issues from the web dashboard by navigating to your API, then selecting the tab containing the element you want to see issues for (either Develop, Test or Observe).
You will see a status indicating whether any issues have been found during validation next to the element. If there are issues, you can display them by hovering over Issues found, then clicking View issues. This will redirect you to a page summarizing the issues.
The validation summary lists all the issues found between the generated collection and the API schema. You can select suggested changes to make to the collection.
The left sidebar gives you a summary of issues and allows you to navigate between them. The summary includes the following details:
- The request name along with the number of issues found in that request.
- The request elements with issues, along with the issue type and number of occurrences.
You can click on the request name or the request element to navigate directly to the corresponding issue(s).
The right-hand side of the review contains details on what changes need to be made for the API element to be in sync with the schema again. Elements highlighted in red will be removed from the collection. Elements highlighted in green will be added.
For example, if a user updates the description of an endpoint in the schema, the summary will show the text that has been removed in red, and what has been added in green.
You can collapse or expand the list of changes by clicking the arrows next to the request or element name.
You can individually select the changes to be applied to the API element as you review them. Navigate to the change you want to apply and select Make this change to the collection next to it. Repeat the same action for each change you would like to apply.
When you're done selecting the changes to apply, click Confirm Changes to Collection.
Alternatively, you can choose to apply all changes by clicking Select all changes, then Confirm Changes to Collection.
You can access the updated API element by clicking View Updated Collection from the confirmation screen. If you didn't apply all changes, you can also review the remaining issues by clicking View Remaining Issues.
If you've been using this feature, the Postman team would like to hear from you! You can provide feedback on the community forum.
In addition to keeping your API elements in sync with a schema, you can analyze and utilize reporting to promote understanding of how your APIs are performing.