watsonx.ai auth failures: key, region, project ID, and IAM scope order

TL;DR

1) the API key is wrong, has trailing spaces, or expired.

Fix

1. 1) the API key is wrong, has trailing spaces, or expired. Expected: you can confirm this matches your situation.

When to use

• You are setting up or using this watsonx.ai auth failures feature.
• The symptom matches: key, region, project ID, and IAM scope order.

When NOT to use

• Unrelated watsonx.ai auth failures issues (different feature, different failure).
• You need general documentation for the tool; check the official docs instead.

Compatibility

Reported against watsonx.ai auth failures.

Variant phrasings

key, region, project ID, and IAM scope order

Why it happens

Most watsonx 401/403 errors trace to one of four credential fields, in this order.

Edge cases

• If your error message differs even slightly, this is probably a different issue; search the exact text.
• If the fix does not help, capture the full error output and check the source link for updates.

Source: Most watsonx 401/403 errors trace to one of four credential fields, in this order.

Verified resolution: [watsonx troubleshooting guides]: 1) the API key is wrong, has trailing spaces, or expired. 2) the URL does not match your region. 3) the project ID is wrong or you lack access to the project. 4) missing IAM permissions. Test credentials with a minimal ModelInference call before wiring the rest of the app. On REST, a raw API key used where a Bearer token is required also returns 401: re-exchange the IAM token first. 403 means the key lacks access to that project or space, or the region URL is wrong.

Source URL: https://github.com/ibm/watsonx-developer-hub/blob/HEAD/agents/README.md