Integrations

Zapier and API keys

Trigger Zaps off docEvault events, or create contacts and requests from other apps, using an API key.

Zapier is available on Professional and Enterprise plans.

Getting a key

Generate an API key under Integrations. Treat it like a password: anyone holding it can act against your organization's data through the API.

What you can trigger on

Zaps can fire off docEvault events, including:

  • A new request being created.
  • A document being approved.
  • A request being completed.

What you can do from other apps

You can also go the other direction and create contacts and requests in docEvault from another app — for example, creating a docEvault contact automatically when a new matter is opened in your practice management system.

Debugging

An event log shows recent activity, which is the first place to look when a Zap doesn't fire. If the event isn't in the log, the problem is on the docEvault side. If it's in the log but the Zap didn't run, the problem is in Zapier.

Rotating a key

If a key is exposed, generate a new one and remove the old one. Any integration using the old key stops working immediately, so update your Zaps in the same sitting.

Didn't find what you needed? Email support@docevault.com with your organization name and, if it's about a specific request or contact, which one.

Last updated 2026-08-25