To enhance security and better protect our customers from potential vulnerabilities, we’re making changes to how Statuspage API keys work. These changes are being introduced to ensure the security of API tokens used to access Statuspage. We also sent email communications about these changes to Statuspage admins in January 2026.
Update: We’ve extended the deadline for these changes from January 31, 2026 to May 15, 2026.
What happens on May 15, 2026?
api_key in query parameters. After this date, you’ll need to send your API key in the request header instead.If you’re currently using Statuspage API keys, please review your integrations and update them before this date. All accounts that have old API keys will also see a banner to update the API keys.
To make things easy, we have added an identifier for old API keys with a tag "OLD KEY – EXPIRES 15 MAY". We recommend that you:
Generate new API keys.
Configure an expiry for each key (between 1 and 365 days).
Rotate keys regularly as part of your security practices.
API keys are managed by account owners at the organization level. Product admins can manage the organization and page IDs needed when using the API, along with API keys. If you don’t know who your account owner is, you can find their details on the API info page in Statuspage.
We will discontinue support for using api_key in query parameters from May 15, 2026, as part of our efforts to improve the security of API tokens.
api_key in query parameters will no longer be supported
If your integrations currently send requests like:
GET https://api.statuspage.io/v1/pages/{page_id}/incidents?api_key=YOUR_KEY
You’ll need to update them to send the key in the header instead:
GET https://api.statuspage.io/v1/pages/{page_id}/incidents
Authorization: OAuth YOUR_KEY
Please review any scripts, integrations, or tools that call the Statuspage API and update them before May 15, 2026.
For more details, go to Create and manage API keys | Statuspage | Atlassian Support
Deeksha
0 comments