Read a signing link
What the hosted signing page renders - the ask, the partner’s branding and the embedded signing session. Authenticated by the token itself, no API key. The signature itself completes inside the embedded session. The requirement resolves once the signature completes, and the page only ever reads.
Path Parameters
The hosted token from a document link.
^rql_[0-9a-f]{48}$Response
The context.
What the hosted signing page renders, read through the link's own token: the ask, your hosted-page branding, and the embedded signing session. Names only, no identifiers - the holder is your client rather than you.
signing_context open, completed, canceled The after-completion destination minted with the session. The page offers it once the flow completes.
The partner's hosted-page configuration - brand and legal footer.
The embedded signing session the page renders, minted fresh for this page load. Present only while the ask is open.
The one origin allowed to frame this page, when the session was minted for embedding. The hosted page treats this as the authority and refuses to run framed anywhere else. Absent on ordinary sessions.