A 403 from PSRESTful means we stopped the call before any data came back. Most of the time the API key isn't valid, or the supplier needs your own login for that service. A 401 only comes up with OAuth tokens. When the supplier itself turns down your login, the error usually arrives inside a normal answer as code 105 or 104, not as a 401.
What the message tells you
Every 403 comes with a message. Find yours here.
| Message | What it means |
|---|---|
Invalid API key |
The API key your system sent doesn't exist or was deleted. |
Anonymous users don't have access to this endpoint |
No API key was sent. |
Invalid Public API key or Origin |
A public key was used from a website that isn't in your Allowed origins. |
SanMar requires your own credentials for the INV service |
The supplier only allows that service with your own login. The supplier and service in the message change. |
You don't have access based on your credentials |
Order status, shipment notifications, invoices and purchase orders need your own login for that supplier. |
Your account needs credentials for ... Customer pricing |
Your negotiated pricing needs your own login. |
No credentials found for supplier ... |
We don't hold agent credentials for that supplier, and your account has none saved. |
You don't have access to account ... |
The account ID sent with the call isn't one your login can use. |
When the supplier turns down the login, you'll see one of these PromoStandards codes instead, in the Data Explorer, in the credential test, or in the response body:
| Code | What it means |
|---|---|
105 Authentication Credentials failed |
The username or password is wrong. |
104 This account is unauthorized to use this service |
The login works, but the supplier hasn't turned on that service for you. |
100 ID (customerID) not found |
The supplier doesn't recognize the ID. |
110 Authentication Credentials required |
No login reached the supplier. |
Fix it
- Open /dashboard/api-keys/ and check that the key your system sends is on the Private Keys tab.
- If it isn't there, click Generate API Key and put the new key in your system.
- Open /dashboard/configure-credentials/ and search for the supplier.
- If the supplier isn't in the table and the message asks for your own credentials, click One Credential and add your login.
- Click the play button (Test credentials) on the supplier's row.
- Hover over any red service to read the supplier's code.
- For
105or100, confirm the login with the supplier, delete the row with the trash icon and add it again. - For
104, ask the supplier to turn on that service for your login. - Make the call again.
Add your supplier credentials has the full steps for adding a login, and Agent credentials vs your own explains which services need yours.
If that didn't work
- You only saved a Staging login. Production calls fall back to it, and the supplier may not accept it there. Add the Production login.
- One service fails and the others pass. Some suppliers use a separate login for some services. Add it under Show Services on the supplier's row.
- Product data stopped working after you added your login. Once your own login is saved, we use it for everything from that supplier. Fix the login, or delete the row to go back to our agent credentials.
Still stuck? Contact us with the supplier code, the endpoint or tool you used, and the time of the call.
PSRESTful returns 401 when an OAuth2 bearer token can't be verified (expired, wrong audience or wrong issuer). Every other access problem is a 403 with a JSON detail. On the PromoStandards proxy endpoints, a supplier login error comes back as HTTP 200 with the code in ServiceMessageArray, ErrorMessage or errorMessage, so check the body as well as the status. The /extra product detail endpoints turn a supplier login error into a 403 with "code": "supplier_credentials_failed".