Error reference / consent-required
Consent is required before completing
The recipient tried to act before accepting electronic signing.
| Problem type | /problems/consent-required |
|---|---|
| HTTP status | 409 |
| Emitted by | Signing page |
| Title values | Consent is required before completingConsent is required before completing fields |
| Trigger | Signing page: action before consent was given |
What happened
A field was completed, or completion was attempted, before the recipient gave consent to sign electronically. The response is HTTP 409.
What it means
Consent is the first step of every signing session and is recorded in the audit trail with its time. Field values sent before it are refused, not stored.
What to do next
In the signing page this cannot normally happen; it indicates the consent call was skipped or failed. Integrations embedding the ceremony call the consent endpoint first and retry the field.
Problem body
Every error is an RFC 9457 problem document with media type
application/problem+json. The type member is the
stable identifier to switch on; docs_url is this page.
{
"type": "/problems/consent-required",
"title": "Consent is required before completing fields",
"status": 409,
"instance": "/v1/...",
"docs_url": "https://docs.signenvoy.com/errors/consent-required"
}