[Final notice] Update your Statuspage API keys before January 31, 2026

G'day Sirah, This is your final reminder to update your Statuspage API keys. On January 31, 2026, we will complete the update to our API authentication. If you do not update your API keys and how you pass them to your page, that is mapped to the atlassian organization cial before the change takes effect, your API requests may start failing. Immediate action required Please ensure you have: Created new API keys, and Replaced all existing keys in your code, scripts, and integrations. To create a new API key: Select your avatar from the top right of the management screen. Select API info from the menu that appears. Select Create key. Enter a key name - Choose a descriptive name so you can identify which application is using it. Select the Copy icon to copy the API key. Select Confirm. Update all integrations to use this new key, ensuring you send it in the request headers. After January 31, 2026, the following will apply Query parameter support (important): api_key will not be accepted in query parameters; it must be sent in headers only. Copying API keys: Keys can only be copied at the time of creation; copying from the API key list will not be possible. Token expiration dates: You can configure keys to expire within 1 to 365 days API key display: Keys will no longer be shown in plain text in the list. Renaming API keys: Keys cannot be renamed; you'll need to delete and recreate them as needed. For step-by-step guidance, visit our support article. Cheers, Statuspage Team

ProTip: Add incident templates for fast and consistent messaging In the heat of an incident, it's often extremely difficult to get your messaging just right. Incident templates let you set up standard incident names and messages in advance, so with just a few clicks you can get that first message out to your customers. Don't want these emails anymore? Unsubscribe

465 Pine St, Floor 13 San Francisco, CA 94104