# date-format-error

<Badge variant="warning">400 Bad Request</Badge> <Badge variant="muted">date-format-error</Badge>

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

## Description
A date or date-time value in the request could not be parsed. The value does not conform to the expected format.

## Response Example
```json
{
  "type": "https://docs.kordiam.app/docs/errors/date-format-error",
  "title": "Date Format Error",
  "status": 400,
  "detail": "Invalid date format",
  "instance": "/api/v2/elements",
  "traceId": "abc-123-def"
}
```

## Common Causes
- The date is provided in a non-ISO 8601 format (e.g., `MM/DD/YYYY` or `DD.MM.YYYY`).
- The date-time string is missing a required component such as the timezone offset.
- Invalid date values were supplied (e.g., month 13, day 32).

## How to Fix
1. Use ISO 8601 format for date values: `2026-01-15`.
2. Use ISO 8601 format for date-time values: `2026-01-15T10:30:00Z` (UTC) or `2026-01-15T10:30:00+01:00` (with offset).
3. Verify that the date components are valid (e.g., month between 01 and 12, day within range for the given month).