ST-2026-017 · Authentication & identity
Atlassian Statuspage deprecates legacy API keys and query-parameter authentication
Atlassian Statuspage set 30 June 2026 as the deprecation point for existing legacy API keys and for api_key query-parameter authentication, while new keys use selectable expiries from one to 365 days.
Previous state
Statuspage integrations could rely on the legacy API-key version, pass api_key in URL query parameters, view stored key values in the management interface and rename legacy keys.
Current state
Atlassian deprecates existing legacy keys and query-parameter authentication, issues new keys with a one-to-365-day lifetime, stops displaying key values after creation and removes legacy-key renaming.
Affected users
Who needs to care
Statuspage account owners and integrations that use existing API keys, query-string credentials or operational processes that retrieve a stored key value later.
Required response
What to do
Generate replacement keys, select a bounded expiry, copy each value at creation, move authentication out of URL query parameters, update dependent integrations, verify traffic on the new key and then delete the old credential.
Evidence boundary
What the source does not prove
The support page states deprecation and discontinued support from 30 June 2026 but does not state that every legacy key is synchronously revoked at the same instant. The safe operational boundary is therefore migration away from the deprecated version and query-parameter method, not an invented universal hard-failure timestamp.
Lifecycle history
Dated event sequence
- Legacy authentication deprecated
Existing legacy keys and api_key query-parameter authentication reached the stated deprecation date; key display and renaming behaviour also changed.
Evidence ledger
First-party sources
- 01Atlassian Statuspage Support — Create and manage API keys
Current official Statuspage key-lifecycle policy observed · 2026-07-29
Open official source ↗