# INVALID_DATETIME

Canonical page: https://docs.ovok.com/errors/invalid-datetime

**HTTP 422.** Problem type: [`https://docs.ovok.com/errors/invalid-datetime`](https://docs.ovok.com/errors/invalid-datetime).

## What this means [#what-this-means]

A date and time in the query, such as `since` or `until`, is not one Signals can read. Some ISO 8601 forms, such as week dates, pass the format check but are still refused. Nothing changed.

## Troubleshooting [#troubleshooting]

1. Send the value in ISO 8601 with a date and a time, in UTC with a trailing `Z`, such as `2026-11-01T08:30:00Z`.
2. URL-encode the value. An unencoded `+` in an offset arrives as a space.

## Retry safely [#retry-safely]

Fix the value and send the request once. Unchanged, it fails again. Nothing changed.

## If the problem persists [#if-the-problem-persists]

Share the HTTP status, problem `type`, request path, response timestamp and `traceId` with your administrator or support contact. Remove access tokens, provider secrets and patient data first. The [Error responses guide](/errors) explains the response fields, and the [machine-code registry](/errors/machine-codes) lists every endpoint-specific type.
