account-unavailableCopy Anchor Link

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.

{
  "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 meansCopy Anchor Link

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 itCopy Anchor Link

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

This is scoped to the one account whose key you presented. Keys for any other accounts are unaffected, so treat it as a per-account condition rather than an API-wide outage.

Retry behaviourCopy Anchor Link

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.