# input-parameter-error

<Badge variant="warning">400 Bad Request</Badge> <Badge variant="muted">input-parameter-error</Badge>

| Field | Value |
|---|---|
| **Type URI** | `https://docs.kordiam.app/docs/errors/input-parameter-error` |
| **HTTP Status** | `400 Bad Request` |

## Description
A domain-specific input parameter failed validation outside the generic pagination, sorting, and
schema-validation contracts. The request cannot be processed until the parameter value is corrected.

## Response Example
```json
{
  "type": "https://docs.kordiam.app/docs/errors/input-parameter-error",
  "title": "Input Parameter Error",
  "status": 400,
  "detail": "External ID must not be blank",
  "instance": "/api/v2/platforms/external-id/%20",
  "traceId": "abc-123-def"
}
```

## Common Causes
- A lookup external ID is blank or exceeds the allowed length.
- A custom-field option endpoint is used with a field whose placement or type does not allow options.
- A custom-field option write would violate option-level business rules.

## How to Fix
1. Review the endpoint documentation to confirm the allowed values and constraints for each parameter.
2. For pagination, cursor, and sort errors, handle the `bad-request` type instead.
3. Correct the domain-specific value named in `detail` and retry.