Proof

Salesforce: Set Up API for Testing – Proof Help Center

The article explains how Salesforce administrators or owners can enable testing mode in sandbox or developer environments by activating the "Package Testing Mode" in Custom Settings to use the Proof testing API for validating workflows, transaction creation, webhook behavior, and document retrieval during user acceptance testing before switching to the production API, emphasizing best practices and troubleshooting tips for a smooth integration setup.

The short answer: Enable testing mode in Salesforce to use the Proof testing API for user acceptance testing (UAT). This configuration applies to Salesforce sandbox and developer environments — skip these steps if you're setting up the integration for production. This content is for users with an administrator or owner role with the Salesforce integration enabled.

Testing mode should only be enabled in sandbox, developer, or UAT environments. Production environments should continue using the production API configuration.


Set up for testing

  1. 1.Navigate to Setup > Custom Code > Custom Settings.
  2. 2.Select Manage next to Notarize Package Settings.
  3. 3.Select New.
  4. 4.Select the checkbox next to Package Testing Mode.
  5. 5.Select Save.

To switch back to the Proof production API later, return to this custom setting, uncheck the Package Testing Mode checkbox, and select Save.

Testing mode allows organizations to validate workflows, transaction creation, and integration behavior before moving into production.


Testing environment overview

Testing mode is commonly used during:

  • Salesforce sandbox implementation
  • User acceptance testing (UAT)
  • Integration validation
  • Workflow testing
  • Document generation testing

Fully validate signer workflows, transaction creation, webhook behavior, and document retrieval before switching to the production API.


Best practices

  • Use testing mode only in non-production Salesforce environments.
  • Validate transaction workflows before enabling production access.
  • Test webhook and document retrieval behavior thoroughly.
  • Confirm API credentials are configured correctly for the testing environment.
  • Document any organization-specific Salesforce configuration settings internally.

Troubleshooting

  • Testing mode doesn't activate → confirm the custom setting was saved successfully.
  • Transactions fail during testing → confirm the sandbox environment can communicate with Proof services.
  • Webhook updates not appearing → verify webhook and site configuration settings.
  • Production transactions accidentally routed to testing mode → review the Package Testing Mode checkbox immediately.
  • Users can't access custom settings → confirm the Salesforce account has administrator permissions.

Summary Checklist

  • Sandbox/UAT only — never enable Package Testing Mode in a production Salesforce org.
  • Setup → Custom Code → Custom Settings → Manage next to Notarize Package Settings → New → check Package Testing Mode → Save.
  • To switch back to production: return to the custom setting → uncheck Package Testing Mode → Save.

Still unsure? Contact Proof Support for help.