Create a Remote Online Notarization transaction for a real estate closing using Proof's Real Estate API
domain: dev.proof.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Get a Proof account and API keys, choosing the Real Estate API (reserved for mortgage/refinance/title/HELOC use cases) rather than the general Business API.
Authenticate using API keys or OAuth client credentials as documented for your environment.
Create a transaction with the signer's email and at least one document carrying a notarization requirement, or start as a draft and add documents later.
Configure the transaction for a notary meeting so the signer is routed through identity verification and a live video notarization session.
Subscribe to Proof's Webhooks V2 events to track transaction status, then retrieve completed, notarized documents via the API once signing finishes.
Known gotchas
The Real Estate API and Business API are separate products with different eligibility — using the wrong one for a real estate closing can hit access restrictions.
Always test against Proof's non-production environment first; the docs explicitly warn not to use the live environment for testing.
Webhook event types and payloads differ between eSign-only and full notarization flows — map the correct event flow for your transaction type.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?