For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Postman
PricingEnterprise
Contact SalesSign InSign Up for Free
HomeDocs
HomeDocs
      • Overview
      • Onboarding checklist
      • Roles and permissions
      • System service accounts
      • Free and Solo experience
      • Team migration
        • Overview
        • Webhooks
        • Installed apps
        • CI integrations
          • All integrations
          • APIMatic
          • Datadog
          • GitLab
          • New Relic
          • OpenAPI
          • PagerDuty
          • Splunk
          • Splunk On-Call
          • Statuspage
      • Admin FAQs
Postman API Platform

Product

  • Postman Overview
  • Enterprise
  • Spec Hub
  • Flows
  • Agent Mode
  • API Catalog
  • Fern
  • Postman CLI
  • Integrations
  • Workspaces
  • Plans and pricing

API Network

  • App Security
  • Artificial Intelligence
  • Communication
  • Data Analytics
  • Database
  • Developer Productivity
  • DevOps
  • Ecommerce
  • eSignature
  • Financial Services
  • Payments
  • Travel

Resources

  • Postman Docs
  • Academy
  • Community
  • Templates
  • Intergalactic
  • Videos
  • MCP Servers

Legal and Security

  • Legal Terms Hub
  • Terms of Service
  • Postman Product Terms
  • Security
  • Website Terms of Use

Company

  • About
  • Careers and culture
  • Contact us
  • Partner program
  • Customer stories
  • Student programs
  • Press and media
Twitter iconLinkedIn iconGithub iconYouTube iconInstagram iconDiscord icon
Download Postman
Privacy Policy

© 2026 Postman, Inc.

On this page
  • Retrieve your PagerDuty integration key
  • Configure Postman with PagerDuty
  • View PagerDuty results
Administer PostmanIntegrationsPostman integrations

Integrate Postman with PagerDuty

||View as Markdown|
Was this page helpful?
Previous

Integrate Postman with OpenAPI

Next

Integrate Postman with Slack

Built with

PagerDuty is an incident management solution that integrates with monitoring stacks for alerting, on-call scheduling, and automatic escalation of critical incidents.

This integration triggers incidents in PagerDuty based on your Postman Monitor results so that your team can investigate and resolve collection run failures.

Retrieve your PagerDuty integration key

  1. Sign in to PagerDuty.
  2. In PagerDuty, click Services. If you’re creating a new service for this integration, click Services and then + New Service.
  3. Enter a Service Name.
  4. Using the Integrations dropdown menu, search and click Postman.
  5. Click the Add Service link at the bottom of the page to create a new service.
  6. Copy and save the PagerDuty integration key to use later.

Configure Postman with PagerDuty

  1. Click Integrations from Postman’s Home page.
  2. Search and select PagerDuty.
  3. Click Add Integration and enter the following:
    • Nickname - A nickname for your integration.
    • Choose workspace - The workspace that contains your monitor.
    • Choose Monitor - Send this monitor’s results to Splunk On-Call.
    • PagerDuty Integration Key - The API key from the Splunk On-Call Integrations page.

You can view your configured integrations on the Browse Integrations page. If any other integrations have been configured for that same monitor, you’ll see an Integrations label with a number in parentheses that indicates the number of integrations already configured for that monitor, click the label to view the integrations. Learn more about viewing or editing integrations.

View PagerDuty results

The PagerDuty console updates continuously to display any incidents that result from your Postman Monitors. If the selected monitor fails, PagerDuty notifies you according to the formatting and business rules you set.