Generate a Full-Access API Key – Proof Help Center
The Proof Help Center explains that organization owners or admins with proper permissions can generate full-access API keys via the Settings > API Keys menu to enable broad API integration and automation capabilities, emphasizing secure storage, restricted access, and key rotation to protect sensitive credentials.
Before you begin.
Availability: API key functionality may require enablement by Proof. Contact your Customer Success Manager (CSM) or Sales representative for enablement assistance.
Important: Full-access API keys provide broad API access to your Proof account. Store API keys securely and never share them publicly.
The short answer: Organization owners and admins can generate a full-access API key from Settings to use with integrations, EasyLinks, and API-based workflows.
Full-access API keys should be treated as sensitive credentials. Anyone with access to a valid API key may be able to perform API actions on behalf of your organization.
Required permissions
Only organization owners, administrators, or users with the appropriate API management permissions can generate and manage full-access API keys.
Common use cases
- Connecting an external system to the Proof API
- Creating transactions through an integration
- Supporting EasyLinks or embedded workflows
- Automating transaction creation and management
- Testing API-based workflows in an approved environment
Security considerations
- Store API keys in a secure credential management system.
- Never expose API keys in source code repositories or client-side applications.
- Limit access to API keys to authorized users only.
- Rotate API keys according to your organization’s security policies.
- Delete unused or compromised API keys immediately.
Generate the API Key
- 1.Log in to your Proof account to complete the steps below.
- 2.Click Settings from the navigation panel on the left.
- 3.Select API Keys from the Settings menu.
- 4.Click Generate Full Access Key at the top of the page. A new key appears in the list below the button.
- 5.Click the Settings icon next to the newly created API key.
- 6.Configure the API key settings as needed, such as name, payer, minimum signers, maximum signers, and other available options.
- 7.Click Save.
- 8.Return to the main API Keys page and click the copy icon to copy the API key.
Important: Copy and store the API key securely. Do not send API keys through email, chat, support tickets, or any unsecured channel.
Summary Checklist
- Navigate to Settings > API Keys and click Generate Full Access Key.
- Open the key's settings, configure the name and available options, and click Save.
- Copy the API key from the main API Keys page using the copy icon.
- Store the API key securely and limit access to authorized users only.
Troubleshooting
- If you do not see the API Keys option, confirm your organization has API access enabled.
- If you cannot generate a key, confirm you have the required organization role or API management permissions.
- If an integration cannot authenticate, confirm the correct API key is being used.
- If an API key may have been exposed, delete the key and generate a new one.
Still Unsure?
Our support team is happy to help. Submit a support request or chat with us from any page in the app.
Related
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.
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.
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.
eVaults for business – Proof Help Center
Proof integrates with eOriginal to enable business customers to securely eVault PDF documents by setting up their own eOriginal vault, configuring the integration via Proof’s admin panel with eOriginal credentials, marking documents for eVaulting either through the Proof interface or API, and after completing meetings, storing original signed documents in the eOriginal vault while retaining watermarked copies and audit trails within Proof.
Proof General Terms
The Proof General Terms, last updated June 19, 2026, govern all Users accessing the Platform—including Subscribers, End Users, Participants, Notary Users, and Verification Portal Users—requiring acceptance via agreement and mandating individual arbitration instead of jury trials or class actions, with detailed definitions and remedies outlined in the document.
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.