◎ Introduction
This guide walks you through the authentication process in Bridgewise (BW). Authentication is essential for protecting the security and integrity of your organization’s data and ensuring safe access to BW services.
1 Step 1: Identify Yourself
To begin, you’ll need valid credentials.
- If you have not received your credentials, please contact our support team at support@bridgewise.com .
- For Machine-to-Machine (M2M) authorization, you will need an Application Client ID and a Secret Key.
2 Step 2: Grant Access Token
Once your credentials have been verified, you must request an Access Token.
This endpoint is available in any BW Product Swagger documentation. For example, StockWise API .
You will receive an Access Token tied to your application’s Client ID. This token grants access only to the services your application is licensed for.
- Tokens can only be used with APIs and Widgets.
- Tokens expire after 24 hours.
You should request a new token once per day and store it securely in your backend for reuse.
? Machine-to-Machine (M2M) Tokens
M2M tokens allow secure communication between services or applications without user involvement.
- Direct application-to-API communication
- Automated processes and background tasks
- Server-to-server interactions
- Issued to applications: Represents the identity of an application, not a user
- Longer validity: Designed for systems that run continuously
- Scoped permissions: Access rights are based on license and application needs
- No user context: Used solely for service-to-service authentication
⚠ Error Codes & Messages
? Using the Access Token
API API Example
Add the token in the Authorization Header:
UI Widget Example
Pass the token as the accessToken parameter: