Notarize
Notarize (rebranded as Proof) provides Remote Online Notarization (RON), eSignature, identity verification, and reusable digital credentials through the Notarize Network. Its REST API (api.proof.com) lets businesses create notarization, eSign, Identify, and real-estate/mortgage closing transactions, attach and template documents, invite signers, manage notaries, and receive V2 webhooks for every transaction and notary state change. Authentication is by API key or OAuth 2.0 client credentials, with a Fairfax test environment for end-to-end sandbox testing. Widely used across proptech, lending, title, and legal workflows.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Notarize the way a machine reads it — 45 machine-readable artifacts across 12 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Notarize scores 54.0/100 (developing), with a separate agent-readiness read of 44/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Put this on your own site. The badge is drawn live from Notarize's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/notarize/"
title="Notarize on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/notarize.svg"
alt="Notarize Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/notarize/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/notarize/"
title="Notarize on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/notarize/card.svg"
alt="Notarize Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Notarize
Each block below is one kind of artifact we hold for Notarize. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 18
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Proof API (formerly Notarize)
REST API for creating and managing notarization, eSign, Identify, and real-estate transactions, documents, signers, notaries, templates, and Webhooks V2 subscriptions.
Notarize Cost Centers API
The Cost Centers API from Notarize — 2 operation(s) for cost centers.
Notarize Documents API
The Documents API from Notarize — 7 operation(s) for documents.
Notarize Eligibilities API
The Eligibilities API from Notarize — 3 operation(s) for eligibilities.
Notarize E Note API
The eNote API from Notarize — 1 operation(s) for enote.
Notarize Integrations API
The Integrations API from Notarize — 1 operation(s) for integrations.
Notarize Notaries API
The Notaries API from Notarize — 4 operation(s) for notaries.
Notarize Notarization Records API
The Notarization Records API from Notarize — 3 operation(s) for notarization records.
Notarize OAuth 2.0 API
The OAuth 2.0 API from Notarize — 7 operation(s) for oauth 2.0.
Notarize OID4VP API
The OID4VP API from Notarize — 4 operation(s) for oid4vp.
Notarize Organizations API
The Organizations API from Notarize — 5 operation(s) for organizations.
Notarize Referrals API
The Referrals API from Notarize — 2 operation(s) for referrals.
Notarize SCIM API
The SCIM API from Notarize — 6 operation(s) for scim.
Notarize Security Events API
The Security Events API from Notarize — 1 operation(s) for security events.
Notarize Templates API
The Templates API from Notarize — 2 operation(s) for templates.
Notarize Title Agencies API
The Title Agencies API from Notarize — 1 operation(s) for title agencies.
Notarize Transactions API
The Transactions API from Notarize — 21 operation(s) for transactions.
Notarize Webhooks API
The Webhooks API from Notarize — 12 operation(s) for webhooks.
Scroll within the panel for all 18 ·
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Notarize Webhooks
ASYNCAPISemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Notarize Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Notarize API Rules
SPECTRALJSON Schema 19
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
authorization_server_metadata
JSON SCHEMAclient_registration_request
JSON SCHEMAclient_registration_response
JSON SCHEMAdocument_creation_params
JSON SCHEMAdocument_params
JSON SCHEMAdocument
JSON SCHEMAdocument_update_params
JSON SCHEMAintrospection_response
JSON SCHEMArevocation_request
JSON SCHEMAsecurity_events_response
JSON SCHEMAtoken_info_response
JSON SCHEMAtransaction_create_params
JSON SCHEMAtransaction_object
JSON SCHEMAtransaction_params
JSON SCHEMAuser_creation_params
JSON SCHEMAx401_handoff_response
JSON SCHEMAx401_payload
JSON SCHEMAx401_result_response
JSON SCHEMAx401_signature_response
JSON SCHEMAScroll within the panel for all 19 ·
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Notarize — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 10
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 10 ·
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/notarize · machine-readable index on apis.io
This is an independent, third-party profile of Notarize, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.