Integrations / Statuspage
Statuspage
Atlassian Statuspage incident and status-page management for pages, components, component groups, incidents (including scheduled maintenance), and subscribers.
What Telara does
Capability matrix
Before you connect
Prerequisites
Vendor setup
Get the credential
In Telara
Connect in Telara
Statuspage API key, generated at https://manage.statuspage.io under API info. Sent as `Authorization: OAuth <api_key>` (Statuspage's own scheme, not Bearer/OAuth2 — confirmed against the published spec's securitySchemes and its curl example). Store page_id with the credential to scope page-level actions (components, incidents, subscribers) without asking the caller for it.
In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.
- API key
Knowledge
What gets indexed
| Resource | Coverage |
|---|---|
| Incidents | Partial — not every record the vendor holds is synced |
| Component | Partial — not every record the vendor holds is synced |
| Pages | Partial — not every record the vendor holds is synced |
Sync
Freshness & sync
| Resource | Lag | Deletions |
|---|---|---|
| Incidents | Up to 1 hour | Removed records disappear on the next full sync |
| Component | Up to 1 day | Removed records disappear on the next full sync |
| Pages | Up to 1 day | Removed records disappear on the next full sync |
Data handling
Permissions & data handling
Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.
Excluded from semantic search: Incidents, Component, Pages.
After connect
Verify it worked
After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.
Honesty