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

# Invalid request

> HTTP 400, invalid-request. Something in the query string or the batch body is wrong. Nothing was done.

| | |
| - | - |
| Type | `https://docs.pinakelai.com/errors/invalid-request` |
| Status | 400 |
| Retry | No. Fix the request and send it again. |

## When it happens

The request has one or more problems, and the `errors` array lists them all, so you can fix everything in one pass. Each entry has a `code`, a `detail`, and either `parameter` (the query parameter) or `pointer` (a JSON Pointer into the batch body, such as `/ids/3`). At most 20 entries are listed; when there are more, `detail` says how many there were.

| `code` | Cause |
| - | - |
| `unknown-parameter` | A parameter that does not exist. The `detail` suggests the closest valid name; the old names `mark_name`, `kind_of_mark` and `expand` point to `mark_text`, `mark_kind` and `include`. |
| `reserved-parameter` | `q`, which is reserved. Use `mark_text_phrase`. |
| `missing-filter` | A search with no filter at all. At least one filter is required; `jurisdiction` counts. |
| `invalid-parameter` | A bad value: a malformed id or date, a class outside 1 to 45, too many values, `from` after `to`, a party filter without `jurisdiction` (or with more than 5 codes), a registration or expiry sort without an anchor filter, a Vienna prefix without a companion filter, `limit` out of range, `since` together with `cursor`, `since` before `feed_start`, and similar. |
| `query-too-long` | A cursor longer than 6,000 characters, or a query string longer than 32 KB. |
| `invalid-body` | A batch body that is not valid JSON, has unknown members, has no ids or more than 100 (25 with a heavy `include`), or contains a malformed id. More than 100 ids is reported once, without checking each id. |
| `not-yet-available` | A parameter reserved for a later version, such as `goods_services_phrase`. |

## What to do

Read every entry in `errors`, fix the request, and send it again. Retrying it unchanged returns the same error.

## Example

```json Body theme={null}
{
  "type": "https://docs.pinakelai.com/errors/invalid-request",
  "title": "Invalid request",
  "status": 400,
  "detail": "The request has invalid parameters; see errors.",
  "request_id": "req_01M7Q40A1B2C3D4E5F6G7H8J9K",
  "errors": [
    {
      "code": "unknown-parameter",
      "detail": "Unknown parameter mark_name. Did you mean mark_text?",
      "parameter": "mark_name"
    },
    {
      "code": "invalid-parameter",
      "detail": "nice_class must be an integer from 1 to 45.",
      "parameter": "nice_class"
    }
  ]
}
```

See the [errors catalogue](https://docs.pinakelai.com/api-reference/errors.md) for every error type, and [Handling errors](https://docs.pinakelai.com/guides/errors.md) for retry strategy.


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