Skip to main content

Creating a quick profile with Postman

Quick profiles in Postman are ideal for one-time tasks that don’t require persistent data storage. When you close a quick profile, it’s automatically deleted along with all associated data, ensuring a clean slate for temporary operations. This guide walks you through launching quick profiles using the POST Start Quick Profile v3 endpoint in Postman, covering proxy configuration, automation options, and headless mode.

What are Quick Profiles?

Quick profiles are temporary browser profiles designed for single-use tasks. They leverage the POST Start Quick Profile v3 endpoint to launch profiles with custom settings, such as proxies, automation frameworks (Selenium, Puppeteer, Playwright), and headless mode, without saving data after the session ends.

Prerequisites​

Before you begin, ensure you have completed the following setup steps:

Before you begin, ensure you have completed the following steps:

  1. Configure Postman Authentication: Complete the three steps outlined in How to Set Up Indigo X API with Postman, including the "Configure the Bearer Token for Requests" section, to ensure proper sign-in.
  2. Access the Postman Workspace: Navigate to the Launcher folder in your Postman workspace.
  3. Select the Endpoint: Choose the POST Start Quick Profile v3 endpoint from the Launcher folder.
Bearer Token Tip

Ensure your bearer token is valid and included in the Authorization tab of your Postman request to avoid authentication errors.

Step 1: Configure the POST Start Quick Profile Endpoint​

To create a quick profile, you’ll use the POST Start Quick Profile v3 endpoint in Postman’s Launcher section. Follow these steps to set it up:

  1. Navigate to the Endpoint:

    • Open your Postman workspace.
    • Go to the Launcher section.
    • Select the POST Start Quick Profile v3 endpoint.

  2. Add a Proxy:

    • Switch to the Body tab in the request editor.
    • Scroll to the flags section and set proxy_masking to custom.
    • Add your proxy details in the proxy parameter (see the example below for the structure).

  3. Configure Automation and Headless Mode:

    • Specify the automation parameter to enable automation frameworks:
      • Options: selenium, puppeteer, or playwright.
      • Including this parameter returns the automation port in the response.
    • Set the is_headless parameter to true or false to enable or disable headless mode.
    • If you don’t need automation or headless mode, deselect these parameters by omitting them or setting them to null.
Optional Parameters

If you’re not using automation or headless mode, simplify your request by excluding these fields. This reduces complexity and keeps the profile lightweight.

Step 2: Prepare the Request Body​

The request body defines the quick profile’s settings, including browser type, operating system, proxy details, and masking flags. Below is an example request body:

{
  "browser_type": "mimic",
  "os_type": "windows",
  "core_version": 124,
  "parameters": {
    "fingerprint": {},
    "proxy": {
      "host": "<string>",     // HOST or IP
      "type": "url",         // HTTP or SOCKS5
      "port": "<integer>",   // PORT
      "username": "<string>",
      "password": "<string>"
    },
    "flags": {
      "audio_masking": "natural",
      "fonts_masking": "natural",
      "geolocation_masking": "custom",
      "geolocation_popup": "prompt",
      "graphics_masking": "natural",
      "graphics_noise": "natural",
      "localization_masking": "mask",
      "media_devices_masking": "mask",
      "navigator_masking": "mask",
      "ports_masking": "mask",
      "proxy_masking": "custom",
      "screen_masking": "natural",
      "timezone_masking": "mask",
      "webrtc_masking": "natural"
    }
  },
  "automation": "selenium",
  "is_headless": false
}

Key Parameters Explained​

  • browser_type: Specifies the browser emulation (e.g., mimic).
  • os_type: Defines the operating system (e.g., windows).
  • core_version: Sets the browser core version (e.g., 124).
  • proxy: Configures the proxy settings, including host, type, port, and credentials.
  • flags: Controls masking behaviors for audio, fonts, geolocation, and more. Set to natural, mask, or custom as needed.
  • automation: Specifies the automation framework (selenium, puppeteer, or playwright).
  • is_headless: Enables (true) or disables (false) headless mode.
Proxy Configuration

Ensure your proxy details (host, port, username, password) are correct. Incorrect settings can cause connection failures or profile launch errors.

Step 3: Run the Script​

To launch the quick profile, execute the request in Postman:

  1. Verify Agent Connection:

    • Ensure the Postman agent is connected, as it facilitates profile launching.
    • Check the agent status in Postman’s bottom-right corner.

  2. Send the Request:

    • Click the Send button in Postman to execute the request.
    • A 200 OK status code indicates success.
    • The response includes the profile ID and, if automation is enabled, the automation port.

Example Response​

{
  "data": {
    "browser_type": "mimic",
    "core_version": 132,
    "id": "d04aa438-d887-11ef-8d6d-0a0027000012",
    "is_quick": true,
    "port": "55579"
  },
  "status": {
    "error_code": "",
    "http_code": 200,
    "message": "Quick profile started successfully"
  }
}