onelifevibe

Platform API error

client_suspended

client_suspended is a 403 error from the OneLifeVibe Platform API: the operator suspended the client, its keys stop working, and Stripe renewal stops.

Updated November 6, 2026

HTTP status
403
Code
client_suspended
API
Platform API v1

Returned when

What to do

Example answer

HTTP/1.1 403
content-type: application/json

{
  "error": {
    "code": "client_suspended",
    "message": "This client is suspended. Email support@onelifevibe.com."
  }
}

Related errors

What it means

client_suspended is the code the OneLifeVibe Platform API returns with HTTP status 403 when the operator has suspended your client. The suspension applies to the client your integration authenticates with, so it affects every call made with that client's keys rather than one endpoint or one request.

While the suspension is in place, those keys stop working. Calls that present them are refused with this code instead of being processed. Suspension also stops Stripe renewal for the client.

The response keeps the standard error shape: an error object holding code, message and hint. For this case, code is client_suspended and the message may read: This client is suspended. Email support@onelifevibe.com.

Why you are seeing it

You are seeing client_suspended because the operator suspended the client whose key authenticated the request. Once that happens, the client's keys stop working across the whole API, so the error follows the credentials rather than the call you happen to be making.

In practice it usually surfaces first in an unattended path: a background sync, a scheduled job, or a dashboard action. The 403 comes back, the work stops, and nothing else in the response tells you what to do beyond the message.

Do not mix it up with the related codes client_pending and client_rejected. Each has its own code and its own next step, which is exactly why the API keeps codes stable and you should branch on code, never on message text.

How to fix it

Email support@onelifevibe.com. That address is in the error message itself, and it is the route back to a working client. Before you write, check the client in the console: it shows the reason when one was given, and quoting that reason saves a round trip.

Suspension stops Stripe renewal, so if you were expecting a renewal to go through, that is part of the same state, not a separate billing problem to chase.

Until the client is reinstated, treat the integration as down. Pause the calls that use those keys instead of retrying them, and note the timestamp when you first saw the error so support has something concrete to work from.

Handling it in code

Match on the code field, not on the message. Codes are stable and messages are not, so a string comparison against This client is suspended will break the day the wording changes. Check code against client_suspended and take the suspended branch.

Treat that branch as terminal for the current credentials. Retrying with exponential backoff will not clear it, because the keys stop working until the client is reinstated. Stop the retry, stop scheduling work that depends on those keys, and surface message and hint to whoever operates the integration.

HTTP 403 can also come from other authorization failures, so keep this handling separate from the generic one. Log the full error body, raise an alert, and let a person follow up with support@onelifevibe.com.

Questions

What HTTP status code comes back with client_suspended?

HTTP 403. The same response carries the error object with code, message and hint, and code is set to client_suspended.

How do I find out why my client was suspended?

Check the client in the console first, because it shows the reason when one was given. Then email support@onelifevibe.com with that reason and the timestamp when you first saw the error.

Should I retry a request that returns client_suspended?

No. The client's keys stop working until it is reinstated, so retrying will not get the call through; contact support@onelifevibe.com and resume once the client is back.

Keys, plans and usage live in the console: rotate keys, add webhook endpoints, see the last 30 days.

Open the console Plans

Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.