consent_captured_in_future
POST /v1/contacts received a consent capture timestamp after the server's current time. Evidence must describe an event that already happened; correct the source record's timestamp and retry.
Problem shape
Every non-2xx response is an RFC 9457 application/problem+json body. The type URI below is stable and machine-matchable, so branch on the final path segment (the code) and treat the status as redundant confirmation. See the error-handling guide.
{
"type": "https://docs.vocapable.com/errors/consent_captured_in_future",
"title": "…",
"status": 422,
"detail": "…",
"instance": "/v1/…"
}