BetterStack Uptime

BetterStack Uptime is a website monitoring and status page service that helps businesses track website availability, receive instant alerts when sites go down, and maintain transparent communication with users through status pages.

Power end-to-end data operations for your BetterStack Uptime API with Nexla. Our bi-directional BetterStack Uptime connector is purpose-built for BetterStack Uptime, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to BetterStack Uptime or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your BetterStack Uptime workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

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:

1. Sign in to your BetterStack Uptime account using your administrator credentials.

2. Navigate to Integrations in your BetterStack Uptime account dashboard, typically accessible from the main navigation menu or settings.

3. In the Integrations section, navigate to the APIs tab or API Settings to access API token management.

4. Look for the Team Token or API Token section in your BetterStack Uptime API settings.

5. If you don't have a team token yet, click Generate Token or Create Team Token to create a new API token.

6. 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

7. 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.

8. 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.

Authenticate

Credentials required

Field	Required	Secret	Description
Uptime Team Token	Yes	Yes	Enter the token generated that authorizes your application. Click on Integrations, go to APIs tab and copy the API token.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – BetterStack Uptime

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. 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.

4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the BetterStack Uptime connector tile, then select the credential that will be used to connect to the BetterStack Uptime instance, and click Next; or, create a new BetterStack Uptime credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common BetterStack Uptime endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Get all Status Pages

This endpoint template fetches a list of all your status pages from your BetterStack Uptime account. Use this template when you need to access status page information, status page settings, or status page metadata for analysis, reporting, or integration purposes.

• This endpoint automatically retrieves a list of all your status pages from your BetterStack Uptime account. No additional configuration is required beyond selecting this endpoint template. The endpoint uses incrementing page number pagination to handle large datasets efficiently, returning up to 200 records per page by default.

This endpoint returns a list of all your status pages from your BetterStack Uptime account, including status page IDs, names, URLs, and other status page metadata. The endpoint uses incrementing page number pagination with page and limit parameters to handle large datasets efficiently. Nexla will automatically follow the pagination to fetch subsequent pages of data.

For detailed information about status pages, API response structures, pagination, and available status page data, see the BetterStack Uptime API documentation.

Get a Status Page

This endpoint template gets a status page based on Status ID from your BetterStack Uptime account. Use this template when you need to access detailed status page information, status page settings, or status page metadata for a specific status page for analysis, reporting, or integration purposes.

• Enter the Status Page ID in the Status Page ID field. This should be the unique identifier of the status page you want to retrieve. The Status Page ID determines which status page's information will be retrieved. You can find the Status Page ID by using the "Get all Status Pages" endpoint or from your BetterStack Uptime dashboard.

This endpoint returns a status page based on Status ID from your BetterStack Uptime account, including status page IDs, names, URLs, and other status page metadata. The Status Page ID identifies the specific status page whose information will be retrieved.

The Status Page ID can be found by using the "Get all Status Pages" endpoint or from your BetterStack Uptime dashboard. For detailed information about status pages, API response structures, and available status page data, see the BetterStack Uptime API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

BetterStack Uptime data sources can also be manually configured to ingest data from any valid BetterStack Uptime API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

BetterStack Uptime API responses typically nest the relevant records in a top-level data array, so the path to data for manual configuration would typically be entered as $.data[*].

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new BetterStack Uptime data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the BetterStack Uptime destination, and select the Send to Destination option from the menu. Select the BetterStack Uptime connector from the list of available destination connectors, then select the credential that will be used to connect to the BetterStack Uptime instance, and click Next; or, create a new BetterStack Uptime credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common BetterStack Uptime endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Create Status Page

This endpoint template creates a new status page from records in a Nexset in your BetterStack Uptime account. Use this template when you need to automatically create status pages based on data from your Nexla flows.

• This endpoint sends data as JSON in the request body to create new status pages. Each record from your Nexset will be sent as a separate API request to create a status page. The request body should contain the status page data in the format required by the BetterStack Uptime API, including all required properties for status page creation.

This endpoint sends data as JSON in the request body to create new status pages in your BetterStack Uptime account. Each record from your Nexset will be sent as a separate API request to create a status page. The request body should contain the status page data in the format required by the BetterStack Uptime API, including all required properties for status page creation.

The status page structure must match the BetterStack Uptime API's expected format. Ensure your status page data includes all required fields. Check out the documentation URL for more details. For detailed information about status page creation, request body formats, and available status page properties, see the BetterStack Uptime API documentation.

Manual configuration

BetterStack Uptime destinations can also be manually configured to send data to any valid BetterStack Uptime API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

The BetterStack Uptime APIs typically expect JSON format for most operations. For update/upsert operations, include the ID of the object to be updated at the end of the URL.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured BetterStack Uptime endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the BetterStack Uptime endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.