Platform API error
client_rejected
client_rejected is a 403 error returned when the client behind your console access or API key has an application that was not approved.
Updated November 6, 2026
- HTTP status
- 403
- Code
client_rejected
Returned when
- The console or a key belongs to a client whose application was rejected.
What to do
- Write to support@onelifevibe.com if you think the decision was wrong.
Example answer
HTTP/1.1 403
content-type: application/json
{
"error": {
"code": "client_rejected",
"message": "This application was not approved."
}
}Related errors
- client_pending The client is not approved yet.
- client_suspended The client was suspended by the operator.
What it means
The Platform API returns client_rejected with HTTP status 403 when the console or API key on the request belongs to a client whose application was rejected. In plain terms, the application for that client was not approved. The request may be well formed; the refusal comes from the state of the client's application.
Responses follow the error shape error.code, error.message, and error.hint. The message may be "This application was not approved." Treat error.code as the contract: codes are stable, messages are not. A check against the message string is fragile.
Why you are seeing it
You will see this code when the console you are signed in to or the API key you are sending is tied to a client whose application was rejected. The same decision applies to both, so the code can appear from console actions as well as API calls.
Related codes include client_pending and client_suspended. They are separate codes with their own meanings. Read error.code to know which client state you are dealing with, and do not infer one state from another.
How to fix it
If you think the decision was wrong, write to support@onelifevibe.com. Say which client the console or key belongs to and include the error response so support can see the code and message. That is the documented remedy for client_rejected.
The code is about the client's application approval, not about the request body. Editing the request is not the documented fix. Keep the response body with error.code, error.message, and error.hint when you contact support.
Handling it in code
Parse the response body and branch on error.code. Check for client_rejected, then show the text in error.message and surface error.hint in your logs. Keep a default branch for codes you do not recognize, because the API can return other client codes such as client_pending and client_suspended.
Do not match on message text; messages can change while codes stay stable. A 403 is an authorization refusal, so avoid retry loops that resend the same credential. When a developer needs the decision reviewed, point them to support@onelifevibe.com.
Questions
What does client_rejected mean in the OneLifeVibe Platform API?
It means the application for the client behind the console or API key was not approved. The Platform API returns it with HTTP status 403 and the message This application was not approved.
What HTTP status does client_rejected return?
HTTP 403. The error body has error.code set to client_rejected, plus error.message and error.hint.
How do I fix client_rejected?
If you think the decision was wrong, write to support@onelifevibe.com. Otherwise, treat the code as the client's application state and handle it in code rather than retrying the same request.
Keys, plans and usage live in the console: rotate keys, add webhook endpoints, see the last 30 days.
Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.