BrowserStack API token expiry impact on active test sessions

BrowserStack supports API key authentication with role-based least-privilege permissions for programmatic access. Tokens are issued with an expiry period and can be rotated via dashboard or API.

The documented behavior for token expiry during an active session is unclear. API responses for expired tokens versus insufficient permissions are not clearly distinguished, and the UI may show a generic login prompt without differentiating token expiry from password expiry.

Token expiry intervals may differ by plan and role permissions are set per user account, which affects applicability.

Does the documentation specify whether an ongoing test session continues, pauses, or terminates when the API token expires mid-session? Is token expiry distinguished from insufficient permissions in API error codes and UI messaging? What is the documented default token expiry interval for API keys across BrowserStack plans?