Skip to main content

Stopping a profile with Postman

This guide walks you through the process of stopping a regular or quick browser profile using the GET Stop Browser Profile endpoint in Postman. By following these steps, you can efficiently manage your browser profiles via API.

Prerequisites​

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

  1. Set up Postman: Install Postman and configure your workspace.
  2. Obtain a Bearer Token: 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.
  3. Access the API Documentation: Familiarize yourself with the GET Stop Browser Profile endpoint.
Need Help?

If you’re new to Postman or API authentication, check out our Getting Started with APIs guide for a step-by-step walkthrough.

Step 1: Locate the Profile ID​

To stop a browser profile, you need the profile_id. You can find this ID in one of two ways:

  • Via DevTools Panel: Access the profile ID from the DevTools panel.
  • Via UI

Profile ID Location

Quick Tip

Save the profile_id in a secure place, as you’ll need it for the Postman request.

Step 2: Configure the Postman Request​

Follow these steps to set up the GET Stop Browser Profile request in Postman:

  1. Open Postman: Launch Postman and navigate to your workspace.
  2. Select the Endpoint: In the Launcher section, locate and select the GET Stop Browser Profile endpoint.
  3. Insert the Profile ID:
    • In the request script, find the profile_id variable.
    • Replace it with the profile_id you obtained in Step 1.

Here’s an example of how the variable should look in your request:

{
  "profile_id": "your_profile_id_here"
}
Double-Check the ID

Ensure the profile_id is correct. An invalid ID will result in a failed request.

Step 3: Send the Request​

With the request configured, you’re ready to stop the browser profile:

  1. Add the Bearer Token: Ensure your bearer token is included in the Authorization tab of the request.
  2. Send the Request: Click the Send button in Postman to execute the request.
  3. Verify the Response: A 200 OK status code indicates the profile was successfully stopped.
Success!

A 200 status code means the browser profile has been stopped. You can verify this in your dashboard.

Troubleshooting​

If you encounter issues, try the following:

  • Invalid Profile ID: Double-check the profile_id in the request.
  • Authentication Error: Ensure your bearer token is valid and properly configured.
  • Non-200 Status Code: Refer to the API documentation for error code details.