Disclosure API · problems · HTTP 503
manifest_timestamp_unreadable
The snapshot manifest carries a timestamp this contract cannot serve.
- What it means
- generated_at, snapshot_as_of and artifact_verified_at must each be a readable instant. One was missing or unparseable, so the manifest is withheld rather than served in a form the published schema rejects.
- What to do
- Retry later. The snapshot file itself is unaffected; only its manifest is withheld.
- Retry
- Retry later; the request was sound. Every 503 carries Retry-After with the minimum wait.
- Who changes what
- Veridion. The request was sound; something on our side did not answer within its budget or failed a check. The API returned nothing rather than something partial.
- On the wire
Content-Type: application/problem+json{"type":"https://www.veridionmarkets.com/data-api/problems/manifest_timestamp_unreadable","code":"manifest_timestamp_unreadable","status":503,…,"request_id":"…"}
Documented for version 1.3.17. The request_id in the body equals the X-Request-ID header; quote it to support@veridionmarkets.com. All problems · API page