Authenticate with the Proof API using an API key or OAuth token as specified in the platform's developer documentation
POST to the transactions endpoint to create a new notarization transaction, supplying the document file (base64-encoded or a presigned URL), signer contact information, and the notarization type (e.g., acknowledgment, jurat)
Retrieve the signer session URL from the transaction creation response and deliver it to the signer via email or embed it in your application
Register a webhook endpoint for transaction status events (COMPLETED, FAILED, WAITING_FOR_PAYMENT) and verify the webhook authenticity using the method specified in the Proof documentation
On receipt of a COMPLETED event, call the transaction documents endpoint to download the notarized document with its electronic notarial certificate and tamper-evident seal
Known gotchas
RON is only legally valid in jurisdictions that have enacted RON-enabling legislation; submitting a RON-notarized document in a state that requires in-person notarization may render the notarization void — verify jurisdiction requirements before automating the workflow
The notary assigned to the session is selected by the platform, not by the API caller; the API caller cannot pre-select or guarantee a specific notary's commission state, which matters for documents requiring notarization by a notary commissioned in a specific state
Signer identity verification for RON (KBA, credential analysis, liveness check) is performed within the platform's session UI; if a signer fails identity verification, the transaction moves to a FAILED state that cannot be retried without creating a new transaction
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp