> ## Documentation Index
> Fetch the complete documentation index at: https://docs.livingsecurity.com/llms.txt
> Use this file to discover all available pages before exploring further.

# invalid_request

> Public API error invalid_request — validation failed or the current resource state prevents the operation (HTTP 400 or 409).

| | |
| - | - |
| **Code** | `invalid_request` |
| **HTTP status** | `400 Bad Request` or `409 Conflict` |
| **Retryable** | No |

## What it means

The request was syntactically or semantically invalid: a malformed body, a missing required field, or a parameter value outside its allowed range. When the problem is attributable to a single parameter, the `param` field names it.

A `409` response means the request conflicts with current resource state. For
example, OAuth client creation can fail because the target service account is
inactive, lacks a requested permission, or has reached its client limit. Inspect
`status` and `detail` together; the error code alone does not distinguish these
conditions from a malformed request.

## What to do

* Read `detail` and `param` — they describe exactly what failed validation.
* For `400`, correct the request before resending it.
* For `409`, resolve the account state, grant, or capacity conflict first. An OAuth
  client awaiting cleanup still occupies capacity. Preserve the retry key when
  retrying the same creation attempt after resolving the conflict.
* Check the API reference for the operation's required fields, types, and allowed values.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.