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.
Audience: Organizations
The short answer: Here's how to delete an OAuth client application or revoke a client secret. Only organization owners and admins (or users with appropriate API/developer permissions) can perform these actions. OAuth is a paid feature — contact your Customer Success Manager (CSM) or Sales team to enable it.
Warning:
Deletion is immediate and cannot be undone. Deleting a client application or revoking a secret immediately disables authentication for any integrations using those credentials. In most cases, rotating or replacing a secret is preferred over deleting an active application. If an integration still requires access, generate and configure a new client secret before revoking the existing one.
Delete a client application
- 1.Select Settings from the navigation on the left.
- 2.Select OAuth from the Settings page menu.
- 3.Select Delete next to the client application you want to delete.
- 4.Review the warning message carefully.
- 5.Select the button to confirm deletion.
Warning:
Any systems, APIs, middleware, or integrations using the deleted OAuth client application will immediately fail authentication.
Revoke an app secret
- 1.Select Settings from the navigation on the left.
- 2.Select OAuth from the Settings page menu.
- 3.Select View client application next to the one you'd like to open.
- 4.Select the trash icon next to the secret you'd like to revoke.
- 5.Select the button in the pop-up window to confirm deletion.
Warning:
Any application or integration using the revoked secret will immediately fail authentication until it is updated with a valid secret.
Troubleshooting
- Integration stopped working after deletion → verify the external system has been updated with the new OAuth credentials.
- Deleted OAuth secrets cannot be recovered — a new secret must be generated and configured.
- Deleting a client application or secret does not remove existing transactions or audit history.
Summary Checklist
- Confirm replacement credentials are configured and tested before deleting or revoking.
- Delete app: Settings → OAuth → Delete → review warning → confirm.
- Revoke secret: Settings → OAuth → View client application → trash icon → confirm.
- Deletion is immediate and irreversible — affected integrations will fail authentication instantly.
Still unsure? Contact Proof Support for help.
Related
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.
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 API Users in Encompass – Proof Help Center
The article guides Encompass administrators through creating an API user with specific permissions—including Read/Edit Loans, Edit Subordinate Loans, and Encompass LO Mobile Connect—to enable Proof's integration using provided API keys, and instructs notifying the Proof Solutions Engineer to complete the connection and receive necessary eClosing forms.
eVault & eOriginal Integration Overview
The eVault & eOriginal integration allows Proof customers with an active eOriginal account to securely store notarized documents and eNotes in a tamper-proof electronic vault that permanently seals documents and signatures to create an unalterable audit trail, with setup guides available for business and real estate transactions and support offered through Proof's app.
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.
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.