Documentation
  • ๐ŸปIntro
    • Why API Security is Critical?
    • Pynt at a Glance
    • Who Should Use Pynt?
  • ๐Ÿ‘ฉโ€๐Ÿ’ปAPI Security Testing
    • Security Testing Overview
    • Prerequisites for Running Pynt Scans
    • How to Install Pynt CLI
    • How to install Pynt Binary (Linux only)
    • Pynt CLI Modes
      • ๐Ÿ”ตPynt Command CLI Mode
      • ๐Ÿ”ตPynt Listen CLI Mode
    • Pynt Security Tests Coverage
      • Business Logic Tests
      • Injection Tests
      • Authentication Bypass Tests
      • Mass Assignment Tests
      • Server-Side Request Forgery Tests
      • Stack Trace In Response
      • Lack of Resources and Rate Limiting
      • File Path Manipulation
      • GraphQL Introspection Vulnerability
      • GraphQL Alias Overloading
      • LLM APIs Vulnerabilities
      • Insecure Transport Scheme
      • Basic Authentication
      • HTTP Desynchronization (Desync) Attack
    • Sensitive Data Exposure Detection
    • Pynt Scans Troubleshooting
      • Pynt CLI Troubleshooting
      • Pynt for Postman Troubleshooting
        • Troubleshoot Pynt Container not Running Error
        • Troubleshoot Empty API Key Error
        • Troubleshoot Unauthorized API Key Error
        • Troubleshoot Collection Not Found Error
        • Troubleshoot Non-Unique Collection Name Error
        • Troubleshoot Empty Collection Identifier Error
        • Troubleshoot Unreachable Target Error
        • Troubleshoot Target Responds with Errors Error
        • Troubleshoot Unresolved Target Domain Error
        • Troubleshoot Unresolved Variable Error
        • Troubleshoot TLS Handshake Fail Error
        • Troubleshoot Few Requests Error
        • Troubleshoot One User Only Error
        • Troubleshoot Failed Assertions Error
    • How To
      • How to Run Business Logic Tests with Pynt
      • How to associate a Pynt scan to an Application in Pynt Dashboard
      • How to tag a scan in Pynt
    • Benchmarks
      • Pynt vs OWASP crAPI
  • ๐ŸคฒSecurity Testing Integrations
    • ๐ŸŸ Pynt with API Testing Tools
      • ๐Ÿ”˜Pynt for Postman
        • Fork Pynt Collection
        • Run Pynt Container
        • Run Pynt in Postman
        • View Scan Results in Postman
      • ๐Ÿ”˜Pynt for Insomnia
      • ๐Ÿ”˜Pynt for ReadyAPI
    • ๐ŸŸ Pynt with API Testing CLIs
      • ๐Ÿ”˜Pynt for Newman (Postman CLI)
      • ๐Ÿ”˜Pynt for TestRunner (ReadyAPI CLI)
    • ๐ŸŸ Pynt with Testing Frameworks
      • ๐Ÿ”˜Pynt for .NET (xUnit)
      • ๐Ÿ”˜Pynt for Selenium
      • ๐Ÿ”˜Pynt for Rest Assured
      • ๐Ÿ”˜Pynt for Jest
      • ๐Ÿ”˜Pynt for pytest
      • ๐Ÿ”˜Pynt for Go
      • ๐Ÿ”˜Pynt for JMeter
    • ๐ŸŸ Pynt on CI/CD
      • โ—How to get Pynt ID for CI/CD Authentication
      • ๐Ÿ”˜Pynt for GitHub Actions
      • ๐Ÿ”˜Pynt for Azure DevOps Pipelines
      • ๐Ÿ”˜Pynt for GitLab
      • ๐Ÿ”˜Pynt for Jenkins
    • ๐ŸŸ Pynt with Burp Suite
    • ๐ŸŸ Pynt with Browsers
      • ๐Ÿ”˜Pynt for Firefox Browser
    • ๐ŸŸ Live Traffic Connectors
      • ๐Ÿ”˜eBPF
        • ๐Ÿ”˜Key Components
      • ๐Ÿ”˜Traffic Mirroring
    • ๐ŸŸ Advanced Pynt Examples
      • ๐Ÿ”˜Pynt as a Standalone Container
      • ๐Ÿ”˜Pynt with Prerecorded Har Files
      • ๐Ÿ”˜Pynt with cURL
  • ๐ŸˆธApplications View
    • Application View Overview
    • Manage Applications
      • Add Application
      • Delete Application
      • Rename Application
    • Manage Sources for API Discovery
      • Add Source
      • Delete Source
      • View Source Info
      • Source Categories
        • API Documentation
          • Swagger
          • Postman Collection
        • API Gateways
          • AWS API Gateway
          • Azure API Gateway
          • Kong API Gateway
          • GCP API Gateway
          • Gravitee API Gateway
        • Testing (API Security Scans)
        • Live Traffic
          • Data Collection with eBPF
          • ALB Traffic Capture with AWS Traffic Mirroring
        • Code Repository
    • Application Dashboard
    • Generate Pentest Report
  • ๐Ÿ“šAPI Catalog
    • API Catalog Overview
    • Navigate API Catalog
      • Filtering API Catalog by Application
      • API Catalog Customization
      • API Related Info
      • APIs at Risk
    • Manage API Source Gaps
      • New APIs
      • Untested APIs
      • Shadow APIs
      • Undocumented APIs
    • View Detailed Endpoint Info
  • โชScan History
    • Scan History Overview
    • Navigate Scan History
      • Associating Scans with Specific Application
      • Filtering by Application
      • Scan Related Info
      • Scan History Customization
    • View Detailed Scan Info
    • Associate Vulnerabilities to Tickets with JIRA
  • Account Management
    • Single Sign-On (SSO)
      • Setting up Okta
      • Setting up Entra ID
Powered by GitBook
On this page
  • Configure Pynt Collection
  • Running the Collection
  1. Security Testing Integrations
  2. Pynt with API Testing Tools
  3. Pynt for Postman

Run Pynt in Postman

Run Pynt's Postman collection effortlessly! Explore our onboarding guide to learn how to execute the Pynt collection within Postman, ensuring a smooth integration of Pynt's API security features with

PreviousRun Pynt ContainerNextView Scan Results in Postman

Last updated 8 months ago

๐Ÿš€ Quick Start: The easiest way to begin running Pynt in Postman is by using the , which guides you through the integration step-by-step.

Running the Pynt collection in Postman is a straightforward process that allows you to perform comprehensive API security testing. This guide will walk you through the steps to execute a Pynt collection, helping you identify vulnerabilities and assess the security posture of your APIs.


Configure Pynt Collection

๐Ÿ’ก Postman API Key and Collection Setup: Configuring the Pynt collection with the Postman API key and the reference collection name/ID is necessary for Pynt to access your Postman workspace and generate security tests. The API key grants permission for Pynt to interact with your collections, and the collection name/ID ensures that Pynt applies the security tests to the correct API set.

Fill in the required parameters in Pynt's collection:

  • API-KEY: Enter your Postman API key under the 'Current Value' column. Generate a key if necessary at .

  • port: The port number used in the Docker run command (default: 5001).

  • YOUR-COLLECTION: The functional test collection name or UID (UID is preferred).

  • scanId: Output variable (ignore).

๐Ÿ’ก Reference App: Pynt provides a vulnerable app example called 'goat', which you can fork from the for testing purposes.


Running the Collection

  • After filling in the parameters, click 'Save'.

  • If you modify your test collection, re-run the Pynt collection.

  • To test another collection, update the YOUR-COLLECTION variable and re-run the Pynt collection.

โš ๏ธ Tip: Ensure you use the correct API key and accurate collection name or ID to avoid issues while running the collection.



๐Ÿ’ก Pynt for Postman Troubleshooting: For problems with Pyntโ€™s Postman integration, check the for step-by-step troubleshooting assistance.

๐Ÿ’ก Still Need Help? For any questions or troubleshooting, reach out to the .

๐Ÿคฒ
๐ŸŸ 
๐Ÿ”˜
Pynt Postman Wizard
Postman API Keys
Pynt public workspace
Pynt for Postman Troubleshooting Guide
Pynt Community Support
Image 1 - Generate / Copy API Key if forgotten
Image 2 - Enter 'Pynt' collection parameters
Image 3 - Run the 'Pynt' collection to generate full OWASP-10 API-security tests for your collection