Skip to main content
The BrowserStack Enterprise API needs the Enterprise plan, and BrowserStack lets only members with the Owner or Admin role use it. BrowserStack gives access to the Users and Teams APIs through its support team, so ask BrowserStack Support to enable them before you connect.

Ask BrowserStack to turn on the Users and Teams APIs

BrowserStack gives access to its Users and Teams APIs through its support team.

  • Ask BrowserStack Support to enable the Users and Teams REST APIs for your organization. BrowserStack lists the Enterprise plan and this request under What You’ll Need in its Enterprise API reference.
  • Connect once BrowserStack tells you the APIs are on for your organization.

Choose whose key to use

The username and access key belong to one BrowserStack member, and StackOne acts with that member’s role.

  • Use a Group Admin, BrowserStack’s name for a member whose IAM Role is Admin for the whole organization rather than for one team. BrowserStack says this role can invite and remove members, change member roles, and change which products other members can use.
  • An Owner also works. There is one Owner per organization. The Owner adds subscription changes, which StackOne does not use, and can read the audit log without changing any setting.
  • Do not use a Team Admin, whose key reaches only its own team’s members.
  • BrowserStack documents one access level for the Users and Teams APIs, Owner or Admin, and names no read-only key. The actions that create, change or remove users and teams use the same key. If auto user provisioning is on, BrowserStack sends team creation and deletion to your identity provider instead.
  • Use an Admin who will stay in the organization. BrowserStack suggests resetting access keys when members leave the organization.

Let a Group Admin read the audit log

BrowserStack lets only the Owner view audit logs by default, and the audit log read is the only action that needs more than a Group Admin key. Skip this if you do not need the audit log read or you use the Owner’s key. Sign in to BrowserStack as the Owner.

  • Open Settings > Permissions.
  • Select the IAM roles tab.
  • Under Account Insights and Reports, select Allow Group Admins to view Audit logs.
  • Select Save.

Copy your username and access key

Sign in to your BrowserStack account as the Group Admin or Owner you chose, and open the Settings page under Account > Settings.

1

Copy the username and access key

Under Local Testing, select the copy icon next to each value.

  • Copy the Username across.
  • Copy the Access Key across.
BrowserStack Settings page with the copy buttons for Username and Access Key under Local Testing highlighted

Rotate or replace the access key

An access key does not expire by default. If your organization turns on auto-rotation, BrowserStack replaces every user access key after the period it sets and emails the member 14 days before. Key validity status under Settings > Product > Local Testing shows the next date.

1

Generate a new access key

Sign in to BrowserStack as the key’s owner and select the User Profile icon in the top-right corner.

  • Select Account & Profile > My Profile.
  • In Authentication & Security, select the rotate icon next to Access Key.
  • Select Confirm.
  • Copy the new Access Key across.
BrowserStack My Profile page with the rotate icon next to Access Key under Authentication & Security highlighted
1

Connect

  • Click Connect.
  • If applicable, the provider will redirect you to a sign-in or authorization page. Complete the provider’s authorization flow.
  • Once authorization is successful, you will see a confirmation popup.
2

Use Actions

Connect an AI platform to the linked account’s actions. See AI Platforms.Other ways to call actions are listed in Protocols & SDKs.

Next Steps

Webhooks setup

Configure receiving Events for BrowserStack into StackOne.