Statuspage, by Atlassian, lets companies communicate service status, incidents, and scheduled maintenance to their customers through a hosted status page. The Nexla Statuspage connector uses the REST API to read pages, subscribers, incidents, and access groups, and to write updates back to those same resources.
Power end-to-end data operations for your Statuspage API with Nexla. Our bi-directional Statuspage connector is purpose-built for Statuspage, 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 Statuspage or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Statuspage 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
Before creating a Statuspage credential, you need an API key from your Statuspage account. Statuspage authenticates every API request with an API key sent in the Authorization header using the format Authorization: OAuth <your-api-key>.
To obtain your Statuspage API key, follow these steps:
Click your avatar in the bottom-left corner of the management dashboard to open the user menu.
Select API info from the menu.
Copy the API key shown on the API info page. Treat this key as a secret, since it grants access to your Statuspage organization and all of its pages.
The API key authenticates your requests and grants access to the pages and resources available to your Statuspage account. If your API key is ever exposed, regenerate it from the API info page. For full details on authentication and available resources, see the Statuspage API Documentation.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter your Statuspage API key in the API Key Value field. This is the key you copied from the API info page in Prerequisites. Nexla sends this value in the Authorization header to authenticate each request to the Statuspage API.
Your API key grants access to your entire Statuspage organization and should be kept confidential. If the key is compromised, regenerate it from the API info page in your Statuspage account.
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.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Statuspage connector tile, then select the credential that will be used to connect to Statuspage, and click Next; or, create a new Statuspage credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Statuspage 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.
[Rest API] List all pages
This endpoint template retrieves data from the Statuspage API to list all pages.
Configure any required parameters for this endpoint, then click the Test button to preview a sample of the data Nexla will fetch before saving the source.
[Rest API] Get page details
This endpoint template retrieves data from the Statuspage API to get page details.
Configure any required parameters for this endpoint, then click the Test button to preview a sample of the data Nexla will fetch before saving the source.
[Rest API] List page members
This endpoint template retrieves data from the Statuspage API to list page members.
Configure any required parameters for this endpoint, then click the Test button to preview a sample of the data Nexla will fetch before saving the source.
[Rest API] View specific user access
This endpoint template retrieves data from the Statuspage API to view specific user access.
Configure any required parameters for this endpoint, then click the Test button to preview a sample of the data Nexla will fetch before saving the source.
[Rest API] List access groups
This endpoint template retrieves data from the Statuspage API to list access groups.
Configure any required parameters for this endpoint, then click the Test button to preview a sample of the data Nexla will fetch before saving the source.
[Rest API] View group details
This endpoint template retrieves data from the Statuspage API to view group details.
Configure any required parameters for this endpoint, then click the Test button to preview a sample of the data Nexla will fetch before saving the source.
[Rest API] List subscribers
This endpoint template retrieves data from the Statuspage API to list subscribers.
Configure any required parameters for this endpoint, then click the Test button to preview a sample of the data Nexla will fetch before saving the source.
[Rest API] Retrieve subscriber details
This endpoint template retrieves data from the Statuspage API to retrieve subscriber details.
Configure any required parameters for this endpoint, then click the Test button to preview a sample of the data Nexla will fetch before saving the source.
[Rest API] Retrieve unsubscribed addresses
This endpoint template retrieves data from the Statuspage API to retrieve unsubscribed addresses.
Configure any required parameters for this endpoint, then click the Test button to preview a sample of the data Nexla will fetch before saving the source.
[Rest API] Count subscribers by channel type
This endpoint template retrieves data from the Statuspage API to count subscribers by channel type.
Configure any required parameters for this endpoint, then click the Test button to preview a sample of the data Nexla will fetch before saving the source.
[Rest API] List templates
This endpoint template retrieves data from the Statuspage API to list templates.
Configure any required parameters for this endpoint, then click the Test button to preview a sample of the data Nexla will fetch before saving the source.
[Rest API] List all incidents
This endpoint template retrieves data from the Statuspage API to list all incidents.
Configure any required parameters for this endpoint, then click the Test button to preview a sample of the data Nexla will fetch before saving the source.
[Rest API] Retrieve incident details
This endpoint template retrieves data from the Statuspage API to retrieve incident details.
Configure any required parameters for this endpoint, then click the Test button to preview a sample of the data Nexla will fetch before saving the source.
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.
Statuspage data sources can also be manually configured to ingest data from any valid Statuspage 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.
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 Statuspage 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.
Click the + icon on the Nexset that will be sent to the Statuspage destination, and select the Send to Destination option from the menu. Select the Statuspage connector from the list of available destination connectors, then select the credential that will be used to connect to Statuspage, and click Next; or, create a new Statuspage credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Statuspage 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.
[Rest API] Update page properties
This endpoint template sends records from a Nexset to the Statuspage API to update page properties.
Each record from the connected Nexset is sent to the Statuspage API as a separate request. Map your Nexset attributes to the fields expected by this endpoint before activating the destination.
[Rest API] Add user access to page
This endpoint template sends records from a Nexset to the Statuspage API to add user access to page.
Each record from the connected Nexset is sent to the Statuspage API as a separate request. Map your Nexset attributes to the fields expected by this endpoint before activating the destination.
[Rest API] Update user permissions
This endpoint template sends records from a Nexset to the Statuspage API to update user permissions.
Each record from the connected Nexset is sent to the Statuspage API as a separate request. Map your Nexset attributes to the fields expected by this endpoint before activating the destination.
[Rest API] Remove user access
This endpoint template sends records from a Nexset to the Statuspage API to remove user access.
Each record from the connected Nexset is sent to the Statuspage API as a separate request. Map your Nexset attributes to the fields expected by this endpoint before activating the destination.
[Rest API] Create access group
This endpoint template sends records from a Nexset to the Statuspage API to create access group.
Each record from the connected Nexset is sent to the Statuspage API as a separate request. Map your Nexset attributes to the fields expected by this endpoint before activating the destination.
[Rest API] Update group settings
This endpoint template sends records from a Nexset to the Statuspage API to update group settings.
Each record from the connected Nexset is sent to the Statuspage API as a separate request. Map your Nexset attributes to the fields expected by this endpoint before activating the destination.
[Rest API] Remove group
This endpoint template sends records from a Nexset to the Statuspage API to remove group.
Each record from the connected Nexset is sent to the Statuspage API as a separate request. Map your Nexset attributes to the fields expected by this endpoint before activating the destination.
[Rest API] Create email/SMS subscription
This endpoint template sends records from a Nexset to the Statuspage API to create email/SMS subscription.
Each record from the connected Nexset is sent to the Statuspage API as a separate request. Map your Nexset attributes to the fields expected by this endpoint before activating the destination.
[Rest API] Modify subscriber preferences
This endpoint template sends records from a Nexset to the Statuspage API to modify subscriber preferences.
Each record from the connected Nexset is sent to the Statuspage API as a separate request. Map your Nexset attributes to the fields expected by this endpoint before activating the destination.
[Rest API] Unsubscribe user
This endpoint template sends records from a Nexset to the Statuspage API to unsubscribe user.
Each record from the connected Nexset is sent to the Statuspage API as a separate request. Map your Nexset attributes to the fields expected by this endpoint before activating the destination.
[Rest API] Resend verification email
This endpoint template sends records from a Nexset to the Statuspage API to resend verification email.
Each record from the connected Nexset is sent to the Statuspage API as a separate request. Map your Nexset attributes to the fields expected by this endpoint before activating the destination.
This endpoint template sends records from a Nexset to the Statuspage API to restore multiple deactivated subscriptions.
Each record from the connected Nexset is sent to the Statuspage API as a separate request. Map your Nexset attributes to the fields expected by this endpoint before activating the destination.
[Rest API] Bulk unsubscribe operation
This endpoint template sends records from a Nexset to the Statuspage API to bulk unsubscribe operation.
Each record from the connected Nexset is sent to the Statuspage API as a separate request. Map your Nexset attributes to the fields expected by this endpoint before activating the destination.
[Rest API] Create message template
This endpoint template sends records from a Nexset to the Statuspage API to create message template.
Each record from the connected Nexset is sent to the Statuspage API as a separate request. Map your Nexset attributes to the fields expected by this endpoint before activating the destination.
[Rest API] Create incident
This endpoint template sends records from a Nexset to the Statuspage API to create incident.
Each record from the connected Nexset is sent to the Statuspage API as a separate request. Map your Nexset attributes to the fields expected by this endpoint before activating the destination.
[Rest API] Update incident status
This endpoint template sends records from a Nexset to the Statuspage API to update incident status.
Each record from the connected Nexset is sent to the Statuspage API as a separate request. Map your Nexset attributes to the fields expected by this endpoint before activating the destination.
[Rest API] Remove incident
This endpoint template sends records from a Nexset to the Statuspage API to remove incident.
Each record from the connected Nexset is sent to the Statuspage API as a separate request. Map your Nexset attributes to the fields expected by this endpoint before activating the destination.
Statuspage destinations can also be manually configured to send data to any valid Statuspage 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.
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 Statuspage endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Statuspage endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
