"Solved": API Key Instructions Unclear, New Key Does Not Work

[R]

I was trying to create a new API key, but it's wasn't working. When I used the new key, I got the following error:

{"error":"Invalid authentication token."}

Here are the steps I took:

1. I clicked on my avatar in the upper-right corner of the page and selected "API Info."

2. Under "Organization API keys", I saw my existing key, which had green text indicating it was active.

3. I deleted the old key and created a new one.

4. The new key does not have the same "active" indicator next to it.

5. The test curl command using this new key failed.

I also noticed a discrepancy in the instructions. The instructions state to "Select your avatar from the bottom left of the management screen." However, I only saw a menu on the upper left, and my avatar is located in the upper right. Therefore, I was unsure if the page I was on was the correct "management screen."

EDIT: The combination of no green "in use" indicator next to the new key, combined with incorrect avatar instructions, clouded my vision, causing me to gloss over a typo in the command. The new API key works.  (facepalm, and other shameful things)

[Nayan Pandey]

Hello R, 

Thank you for contacting the StatusPage community and sharing your detailed feedback and for letting us know about your experience.

We're sorry for the inconvenience and confusion caused by the documentation and the missing 'in use' indicator for new API keys.

We have logged your request with our internal team to update the documentation to accurately reflect the avatar location on the top right corner. Additionally, we've requested that a green 'in use' indicator be added next to active API keys to improve clarity on a feature request with ID: STATUS-1007. Due to the private nature of StatusPage feature requests, you may not be able to view the feature request. However, if you'd like to know the progress on the feature request, please do reach out to us and we will be more than happy to share the update.

We appreciate your patience and for helping us improve the experience for everyone!

Regards,
Nayan