parental-consent
parental-consent

Preview Signed Form

The completed form, as it WILL look, before anything is recorded.

A guardian signing on a phone sees a scrolling web form: labels, radio buttons and a signature box. What they are actually agreeing to is a document -- and until now the first time anyone saw the two joined together was after the consent had already been stored. Showing the finished page first is the difference between signing a form and signing a screenshot of one.

Writes NOTHING. It takes the same payload as the submit below, renders it onto the school's own PDF and hands it back. A guardian who does not recognise what they see goes back and edits, and no record was created in the meantime.

Unauthenticated, like the rest of the guardian flow: the token IS the authorisation. It is deliberately tolerant about missing fields -- a preview of a half-filled form is useful, and the submit endpoint is what enforces completeness.

post/parental-consent/sign/{token}/preview

Path parameters

tokenstring required

Query parameters

formatstring
pageinteger

Request body

object required

Response

Successful Response

{"stackTrail":"paths:/parental-consent/sign/{token}/preview:post:responses:200:content:application/json:schema","oasType":"schema","type":"unknown"}

Changes

Changed in 2 of the 25 revisions of this API.3

Of the 25 revisions, 1 has no diff computed.