Authorization
BetterStack Uptime
Prerequisites
Before creating a BetterStack Uptime credential, you need to obtain your Team Token from your BetterStack Uptime account. BetterStack Uptime uses Bearer token authentication for all API requests.
To obtain your BetterStack Uptime Team Token, follow these steps:
-
Sign in to your BetterStack Uptime account using your administrator credentials.
-
Navigate to Integrations in your BetterStack Uptime account dashboard, typically accessible from the main navigation menu or settings.
-
In the Integrations section, navigate to the APIs tab or API Settings to access API token management.
-
Look for the Team Token or API Token section in your BetterStack Uptime API settings.
-
If you don't have a team token yet, click Generate Token or Create Team Token to create a new API token.
-
Configure your token settings:
- Enter a name for the token (e.g., "Nexla Integration")
- Review the token permissions or scopes (if applicable)
- Click Create or Generate to create the token
-
After the token is created, copy the Team Token or API Token value immediately, as it may not be accessible again after you navigate away from the page.
-
Store the token securely, as you will need it to configure your Nexla credential. The Team Token is sensitive information and should be kept confidential.
The Team Token is sent as a Bearer token in the Authorization header for all API requests to the BetterStack Uptime API. The token authenticates your requests and grants access to BetterStack Uptime resources based on your account permissions. If your token is compromised, you should immediately revoke it in your BetterStack Uptime account settings and generate a new one. For detailed information about obtaining team tokens, API authentication, and available endpoints, refer to the BetterStack Uptime API documentation.
Create a BetterStack Uptime Credential
- To create a new BetterStack Uptime credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
New Credential Overlay – BetterStack Uptime

Credential Name & Description
-
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Resource descriptions are recommended but are not required. They should be used provide information about the resource purpose, data freshness, etc. that can help the owner and other users efficiently understand and utilize the resource.
Bearer Token Authentication
BetterStack Uptime uses Bearer token authentication for all API requests. The Team Token is sent in the Authorization header.
-
Enter your Uptime Team Token in the Uptime Team Token field. This is the token generated that authorizes your application. Click on Integrations, go to APIs tab and copy the API token. The token is sent as a Bearer token in the Authorization header for all API requests to the BetterStack Uptime API. The Team Token is sensitive information and must be kept confidential.
Your BetterStack Uptime Team Token can be found in your BetterStack Uptime account under Integrations > APIs tab. Click on Integrations, go to APIs tab and copy the API token. The token is sent as a Bearer token in the Authorization header for all API requests to the BetterStack Uptime API.
If your token is compromised, you should immediately revoke it in your BetterStack Uptime account settings and generate a new one. The Team Token provides access to your BetterStack Uptime account data and should be treated as sensitive information. Keep your token secure and do not share it publicly.
For detailed information about obtaining team tokens, API authentication, and available endpoints, see the BetterStack Uptime API documentation and BetterStack overview.
Save the Credential
-
Once all of the relevant steps in the above sections have been completed, click the Save button at the bottom of the overlay to save the configured credential.
-
The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.