We have noticed the following message on our Status page:
“All of your old API keys will automatically expire on 15 May 2026. Please update to new API keys now to avoid disruption.”
We have already generated a new API key, but we are unsure where it needs to be updated.
We referred to the steps in the documentation below; however, the More actions (•••) option mentioned is not visible on our side in the API Info:
https://support.atlassian.com/statuspage/docs/create-and-manage-api-keys/#Rename-API-keys
(Step referenced: Select the More actions icon (•••) next to the API key you want to rename.)
Could you please assist us in identifying the correct process to update the API key?
Hi there,
Thanks for reaching out to Atlassian Community about the Statuspage API key changes.
Great news — since you've already generated a new API key, you're halfway there! Here's what you need to do next:
Where to update the new key:
You'll need to replace the old API key with your new one in every integration, script, automation, or external tool that currently uses it. Statuspage doesn't have a centralised place to push key updates — you'll need to update each integration individually.
Common places to check:
Authorization headerAbout the More actions (•••) option:
The Rename functionality (and the ••• menu) applies only to old API keys. With the new key format, renaming is no longer supported — you can only delete keys. This is expected behaviour and part of the deprecation changes rolling out ahead of the May 15, 2026 deadline.
Important reminders:
api_key in query parameters is also being discontinued)For the full details, refer to: Create and manage API keys | Statuspage | Atlassian Support
Hope that helps! Let us know if you have further questions.
Regards,
Aditya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.