account-unavailable

HTTP 403. The key is valid and resolved to a real connection, but the Supliful account that owns it can no longer use the API.

Code
{
  "type": "https://developers.supliful.com/errors/account-unavailable",
  "title": "Account unavailable",
  "status": 403,
  "detail": "This account can no longer use the API. Contact help@supliful.com.",
  "instance": "/v1/me"
}

What it means

The account has been disabled or deactivated. This is a state of the Supliful account itself, not of the key or the connection — which is why it answers 403 rather than invalid-api-key. Your credential is intact; the account behind it is not currently permitted to operate.

Account status is checked on every request, not at the moment a key is issued. Keys outlive account state, so a key that worked yesterday will start returning this the moment the account changes, with no action on your side and no change to the key.

How to fix it

This is not something a change to your integration can resolve. Contact help@supliful.com to find out why the account is in this state and what is needed to restore it.

If you integrate on behalf of several merchants, note that this is scoped to the one account whose key you presented. Other merchants' keys are unaffected, so treat this as a per-account condition rather than an API-wide outage — keep processing the accounts that still work.

Retry behaviour

Do not retry on a short interval. The condition persists until an account-level change is made, which is a human process measured in hours or days, not seconds. Surface it to whoever operates your integration so they can follow it up, and stop sending requests for that account until it is resolved.