Fix UPCS Error 401 Invalid or Inactive API Key (key_inactive)

An HTTP 401 with the message "Invalid or inactive API key" means the key you sent is wrong, disabled or expired. Requests with that key are refused until the key is active again or you use another one. The code key_inactive appears only on an embedded map that is already running, when the key behind its session is disabled or expires; it reaches your page through onError.

Symptom

Direct API calls and session creation fail with success: false and the message "Invalid or inactive API key" (no code field). A running embedded map reports the code key_inactive through onError. The same request worked earlier, or works with a different key.

Likely causes

• The key was disabled in the partner panel.
• You are using an old key after creating a replacement.
• The key belongs to a different environment or account than you expect.

Fix it step by step

1. Sign in to the partner panel and open the API keys card.
2. Find the key that starts with upcs_ and matches the one in your configuration. Compare the whole value, not only the first characters.
3. If the key is disabled and should be in use, enable it again.
4. If you intentionally rotated keys, copy the new key and update every place that uses the old one: your server code, environment variables, and plugin settings.
5. Clear any cached configuration on your site so the new key is actually read.
6. Keep keys on the server. Never place them in browser-side code.

Confirm it is fixed

Repeat the request that failed. A successful response is no longer a 401. In a store plugin, use the connection test in the settings page; the WordPress guide explains what to check if that still fails.

When to contact support

If the key shows as active in the partner panel but the error continues, or if you cannot see the key at all, contact support with the first and last four characters of the key (never the full key) and the time of the request.