Troubleshooting
Fix UPCS Error 403 partner_required
The 403 partner_required error means the API key is not linked to a partner account. See how to set up a partner account and use its keys.
Updated 14 October 2026 · 2 min read
The partner_required error (HTTP 403) means the request needs a partner account behind the API key, and none was found. The embed and server API are available to partners, so the request is refused until a valid partner key is used.
Symptom
A call to the embed sessions endpoint or another API endpoint returns success: false with the code partner_required, even though a key is being sent.
Likely causes
- You have not yet created a partner account.
- The key you are using was not issued from a partner account (for example, a value copied from another system).
- You are signed in to a different account from the one that owns the key.
Fix it step by step
- Go to the partner page and create a partner account if you do not have one.
- Sign in to the partner panel and create or copy an API key. Keys start with
upcs_. - Replace the key in your code, environment variable or plugin settings with this key.
- Register your site under Allowed origins (https only). See origin_not_allowed if the origin is refused afterwards.
- Send the key in the
x-api-keyheader. If you get a 401 instead, follow missing or invalid x-api-key.
Confirm it is fixed
Create an embed session or call the lookup endpoint again. A successful response returns the data (for example a session_token) and no partner_required code.
Still stuck?
If you have a partner account and an active key but still see this error, contact support and tell us the email or business name on the account and the endpoint you called.
Frequently asked questions
Where do I get API keys?
Businesses create a partner account and manage API keys and allowed origins in the partner panel. Keys start with upcs_.
