Create an OAuth Client Application – Proof Help Center
The Proof Help Center guide explains that organization owners, admins, or users with API management permissions can create OAuth client applications—a paid feature enabled by Proof—to securely connect external systems to Proof accounts using token-based authorization instead of passwords, with each client application having a unique App ID, multiple one-time-viewable App secrets, full API key scope, and tokens that expire every two hours, recommending separate clients for different environments and emphasizing secure storage of secrets.
Audience: Organizations
OAuth is a standard authorization protocol that lets you securely connect external systems to your Proof account without sharing passwords. Here's how to create an OAuth client application to get started.
Only organization owners, admins, or users with API management permissions can create OAuth client applications. For technical details, refer to the OAuth developer documentation.
Note: OAuth is a paid feature and must be enabled by Proof. Contact your Customer Success Manager (CSM) or have an owner/admin contact the Sales team using an email address connected to your company's Proof account.
Security: OAuth client applications provide API access to your Proof account. Store all generated secrets securely and never share them publicly.
How it works
Instead of sharing a username and password, OAuth uses tokens that provide specific, limited permissions. A common example is signing in with Google or Apple. In Proof, OAuth is offered as an alternative to API keys.
To use OAuth, you create a client application. You can create an unlimited number of client applications. Each client application:
- Has one unique App ID
- Can have multiple random App secrets
- Has a scope equivalent to a full-access API key
App secrets:
- Are displayed to you only once — copy and store them immediately
- Show the date and time of creation
- Can be deleted unless they're the only secret associated with the client application
OAuth tokens expire every 2 hours.
Best practice: Create separate OAuth client applications for production, testing, and development environments whenever possible.
Common use cases
- Integrating external systems with the Proof API
- Automating transaction creation workflows
- Managing API authentication without sharing account credentials
- Supporting secure third-party integrations
- Separating production and sandbox API environments
Security considerations
- Store OAuth client secrets in a secure credential management system.
- Never expose OAuth secrets in source code repositories or client-side applications.
- Rotate client secrets regularly according to your organization's security policies.
- Revoke unused or compromised secrets immediately.
Create an OAuth client application
- 1.Select Settings from the menu on the left.
- 2.Select OAuth from the Settings page menu.
- 3.Type the name of the client application.
- 4.Select Create client application.
- 5.Select Copy to clipboard to copy the secret.
- Be sure to copy the secret — it will not be visible once you navigate away from this page.
Important: If you lose the client secret, it cannot be recovered — a new secret must be generated.
Troubleshooting
- If your integration cannot authenticate, verify the correct App ID and secret are being used.
- OAuth client secrets are only visible once after creation.
- Expired OAuth tokens must be refreshed through the OAuth flow.
- Ensure OAuth has been enabled for your organization before attempting to create a client application.
Summary Checklist
- OAuth must be enabled by Proof before you can create a client application — contact your CSM or sales.
- Navigate to Settings → OAuth, name the application, and select Create client application.
- Copy the client secret immediately — it's shown only once and cannot be recovered if lost.
- Store secrets securely and rotate them regularly. OAuth tokens expire every 2 hours.
Still unsure? Contact Proof Support for help.
Related
Delete an OAuth Client Application or Secret – Proof Help Center
The Proof Help Center guide explains that only organization owners or admins can immediately delete an OAuth client application or revoke a client secret—actions that disable authentication for all integrations using those credentials—and recommends rotating secrets instead of deleting active applications, providing step-by-step instructions and warnings about the irreversible impact on connected systems.
Cloning a Child Organization in Command Center
The guide explains how Command Center owners and administrators can clone a child organization by copying specific settings like billing and notary instructions from an existing or root organization to create a new child organization, while noting that certain elements such as EasyLinks, API keys, and users do not transfer, and provides step-by-step instructions along with recommendations to review settings post-cloning and contact support if issues arise.
API Supplement
The API Supplement, effective December 16, 2024, is incorporated into the Proof General Terms and grants Subscribers a limited, revocable license to use Proof’s APIs solely for integrating their applications with Proof’s Services, requires secure handling and non-sharing of API Keys, restricts API use to approved purposes, and governs access to sensitive personal data such as homeowner and financial information under strict compliance conditions.
Business API quick start guide – Proof Help Center
The Business API quick start guide for Proof explains that eligible organizations can use the RESTful Proof Business API to send documents, create transactions, connect signers for notarization or eSignature workflows, monitor transaction status via webhooks, and retrieve completed documents, while emphasizing secure handling of API keys and OAuth credentials, providing links to detailed API references and instructions for generating API keys within a Proof account.
2025-05-12 Proof Release Notes
The May 12, 2025 Proof release introduces OAuth authentication for API users (delayed to May 19), improved Kentucky notary seal formatting, removal of commission expiration from Colorado quick stamps, and a new default fully zoomed-out document preview for signers to enhance document review across all devices.
Set Up a Proof Administrator Account for Adobe Integration
This article guides organizations through setting up a Proof administrator account for Adobe Acrobat Sign integration by accepting an email invitation, creating a password, generating a full access API key in Proof's settings, securely storing the key, and entering it into Adobe Sign's Notary Settings, while emphasizing prerequisites, best security practices, and troubleshooting steps for missing invitations.