Summary and recommendation
Proof (formerly Notarize) does not expose a publicly documented REST API for user CRUD operations. The Proof developer API exists but is scoped exclusively to notarization transaction workflows - it is not a user-management or provisioning surface.
No base URL, auth method, or user-object schema for identity operations is available in official documentation as of the policy date.
SCIM provisioning is not confirmed. Enterprise SSO (Okta, Entra ID) is supported, but automated user provisioning and deprovisioning via SCIM is undocumented. JIT (Just-In-Time) provisioning via SSO appears to be the only automated onboarding path, and even that is not fully specified in public help content.
Any integration targeting user lifecycle management - create, update, deprovision - would require direct engagement with Proof's enterprise team. Treat this app as an identity graph gap until official provisioning APIs are confirmed.
API quick reference
| Has user API | No |
| SCIM available | No |
| SCIM plan required | Enterprise |
Authentication
Auth method: Not documented
User object / data model
User object field mapping is not yet verified for this app.
Core endpoints
Endpoint coverage is not yet verified for this app.
Rate limits, pagination, and events
Rate limits: Not documented
Rate-limit headers: No
Retry-After header: No
Rate-limit notes: Not documented
Pagination method: none
Default page size: 0
Max page size: 0
Pagination pointer: Not documented
Webhooks available: No
Webhook notes: No publicly documented webhook system for user-management events found in official Proof/Notarize documentation.
Alternative event strategy: Proof does offer transaction/notarization event webhooks for business integrations via their developer API, but these are scoped to notarization workflow events, not user lifecycle management.
SCIM API status
- SCIM available: No
- SCIM version: Not documented
- Plan required: Enterprise
- Endpoint: Not documented
Limitations:
- No SCIM provisioning support documented publicly for Proof (formerly Notarize).
- Enterprise plan supports SSO via Okta and Microsoft Entra ID, but automated user provisioning/deprovisioning via SCIM is not confirmed in official documentation.
- User management for enterprise accounts appears to be handled manually through the admin console or via SSO JIT (Just-In-Time) provisioning only.
Common scenarios
No user-management API scenarios can be documented from available public sources. The Proof developer API covers notarization transaction events (initiation, completion, status webhooks) but these are orthogonal to user provisioning. No endpoints for listing users, creating accounts, updating roles, or deprovisioning exist in official documentation.
Webhooks are available for notarization workflow events only - not for user lifecycle events such as account creation, role change, or removal. There is no retry-after header, no documented rate limit tier, and no pagination schema applicable to user objects because no user-listing endpoint is publicly available.
Scenario implementations are not yet verified for this app.
Why building this yourself is a trap
The primary integration trap is conflating Proof's transaction API with a user-management API - they are entirely separate concerns. Developers who locate the proof.com/developers surface may assume user provisioning endpoints exist; none are publicly documented.
The rebrand from Notarize to Proof means older API references, community threads, and third-party integration guides may point to deprecated or incorrect documentation. Always verify against current proof.com/developers content.
Enterprise SSO support (Okta, Entra ID) can create a false sense of provisioning coverage. SSO handles authentication; without confirmed SCIM, deprovisioning remains a manual admin action. Any identity graph that treats SSO presence as equivalent to lifecycle automation will produce stale access records for this app.
Automate Notarize workflows without one-off scripts
Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.
