Skip to main content

https://developers.sysaid.com/reference/createapplicationkey created an application key.

https://developers.sysaid.com/reference/generateaccesstoken-1 created the access token

Any other action under https://developers.sysaid.com/reference fails with the message “sorry, you couldn’t be authenticated with those credentials”.

 

This started happening today.  It worked yesterday.

Hi there,

SysAid Copilot is here with our AI Magic!

Here is the response we thought might assist you:

copilot-1.png
## API Reference "Try It" authentication suddenly failing

Thanks for the clear details. Since Create App Key and Generate Access Token work, but other “Try It” calls in the docs started failing today with “sorry, you couldn’t be authenticated with those credentials,” it’s likely an issue with the docs console session or headers, not your credentials.

Please try:

1) Hard refresh session
- Open the docs in an incognito/private window and sign in again.
- If already open, click “Logout” in the docs console (top-right), then log back in and reselect your account.

2) Verify required headers each call
- Ensure x-sysaid-accountid is set to your exact account ID.
- Use the Bearer token returned from Generate Access Token in Authorization: Bearer .
- Remove any leftover cookies/headers from previous sessions.

3) Re-generate token cleanly
- Generate a fresh access token and use it immediately in a new incognito session.
- Confirm the token hasn’t expired and is copied without extra spaces/line breaks.

4) Check account scope
- Make sure the selected account in the docs console matches the account used to create the app key/token.

5) Known transient issue
- We’ve seen intermittent authentication issues on the docs “Try It” tool causing 401/“couldn’t be authenticated” while the API itself works. As a workaround, call the same endpoints directly (e.g., via Postman/curl) using:
- Base: https://{your-account}.sysaidit.com/connect/v1/...
- Headers: x-sysaid-accountid: {yourAccountId}, Authorization: Bearer {token}

If this persists after the above, please share:
- Exact endpoint(s) failing
- Full request headers (mask secrets)
- Response status code and body
- Time and timezone of the failures

This will help pinpoint whether it’s a docs console bug or header mismatch.

All is working again - was there a system problem?  I had the same issues when using postman.


Reply