What are webhooks
Webhooks are event-driven integrations that automatically send real-time data from GetAccept to external systems whenever specific actions occur. Instead of polling the GetAccept API to check for updates, webhooks push notifications to your endpoint when events happen, making your integrations faster and more efficient.
Common use cases include:
Automatically updating your CRM when a document is sent or signed.
Triggering downstream workflows in external systems based on GetAccept events.
Syncing recipient engagement data to analytics platforms.
Creating audit logs of document activity.
Notifying team members of critical events in real-time.
How to set up a webhook
Note: Webhooks cannot be created, edited, or deleted from the core GetAccept app. Webhook setup is handled by GetAccept Tech Support. Contact your GetAccept representative with your endpoint URL, the events you want to subscribe to, and any authentication headers your endpoint requires. Tech Support will provision the webhook and confirm the exact event payload structure during setup.
Available webhook events
Webhooks can fire on a range of GetAccept events, including document activity (such as created, sent, opened, signed, expired, recalled), recipient activity, and Deal Room activity. The exact set of events available to you depends on your entity configuration. Tech Support will confirm which events your webhook subscribes to during setup.
Security and IP whitelisting
If your webhook endpoint requires IP whitelisting, GetAccept sends webhooks from a fixed set of IP addresses. See Webhook IP whitelisting for the current list.
You can also configure custom HTTP headers on your webhook (such as an Authorization header with a bearer token) so your endpoint can verify incoming requests. Tech Support configures these during setup.
Webhooks vs. event-based CRM sync
Webhooks are the right choice when you need to push GetAccept event data to a custom endpoint or to a system that isn't a supported CRM. If your goal is specifically to update CRM fields when GetAccept events occur, event-based CRM sync may be a better fit because it can layer in conditions based on CRM data.
With event-based CRM sync, admins can build conditional logic that combines a GetAccept event with CRM field values (such as deal stage, deal value, or any CRM field) to update CRM records only when both the event and the CRM conditions are met. GetAccept reads the live CRM record at the moment the event fires and applies the right update.
For example, when a GetAccept contract is signed:
IF CRM Stage = "Negotiation" AND Amount < $5,000, set "Onboarding Type" = "Self-serve".
IF CRM Stage = "Negotiation" AND Amount >= $5,000, set "Onboarding Type" = "Dedicated CSM".
Event-based sync with CRM field conditions is available for HubSpot, Pipedrive, Upsales, and Microsoft Dynamics 365. Salesforce is not included in this release. If you are routing conditional CRM logic through webhooks today on one of the supported CRMs, you may be able to consolidate that logic back into the native integration.
Note: Event-based CRM sync with CRM field conditions does not replace webhooks. Webhooks remain the right tool for pushing event data to custom endpoints and non-CRM systems.
Related articles
Integrations settings, overview of GetAccept integration options.
Webhook IP whitelisting, IP addresses for firewall configuration.
GetAccept REST API Overview, REST API as an alternative for polling-based integrations.