Access Webhook Settings
Webhooks are configured through the GetAccept settings panel. To access your webhook settings:
Click your profile image in the top-right corner
Select Settings
Under Integrations, select Webhook
You'll see a list of all webhooks configured for your entity, with their status, event type, and endpoint URL displayed.
Note: Webhook settings are configured at the entity level and affect all users in your organization.
What Are Webhooks and Why Use Them
Webhooks are event-driven integrations that automatically send real-time data from GetAccept to external systems whenever specific actions occur. Instead of polling GetAccept repeatedly to check for updates, webhooks push notifications to your endpoint when events happen , making your integrations faster, more efficient, and more responsive.
Pro-tip: Set up webhooks for high-frequency events to avoid manual data syncing between systems.
Common use cases for webhooks 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 all document activity
Notifying team members of critical events in real-time
Supported Webhook Events
GetAccept supports webhooks for the following events:
Document Created , A new document has been created in draft state
Document Sent , A document has been sent to recipients
Document Opened , A recipient has opened the document for the first time
Document Signed , All required signers have completed signatures; document is now legally binding
Document Reviewed , A recipient has viewed the document but not yet signed
Document Expired , The document has passed its expiration date
Document Recalled , The sender has pulled back a sent document to edit and resend
Recipient Added , A new recipient has been added to a document
Recipient Signed , An individual recipient has completed their signature
Chat Message Sent , A message has been posted in document or Deal Room chat
Deal Room Created , A new Deal Room has been created
Deal Room Published , A Deal Room has been published and shared with participants
Add a New Webhook
To create a new webhook:
Navigate to Settings > Integrations > Webhook
Click the Add Webhook button (or + icon)
Enter your webhook URL , this is the endpoint where GetAccept will send event data
Select the Event Type you want to listen for from the dropdown menu
Optionally add custom headers for authentication (e.g., API keys or bearer tokens)
Click Create Webhook or Save
Your webhook is now active and will fire whenever the selected event occurs.
Edit an Existing Webhook
To modify a webhook's configuration:
Navigate to Settings > Integrations > Webhook
Click on the webhook name or the Edit icon
Update the URL, event type, headers, or other settings as needed
Click Save Changes
Changes take effect immediately for new events. Previously configured webhooks will not be re-triggered.
Delete a Webhook
To remove a webhook:
Navigate to Settings > Integrations > Webhook
Find the webhook you want to remove
Click the Delete or Remove icon (typically a trash bin)
Confirm the deletion
Once deleted, the webhook will no longer receive events from GetAccept.
Test a Webhook
Before relying on a webhook in production, test it to confirm your endpoint is receiving data correctly:
Navigate to Settings > Integrations > Webhook
Click on the webhook you want to test
Look for a Send Test Event or Test button
Click to send a sample payload to your endpoint
Check your endpoint logs to verify the test event was received
The test event uses the same payload structure as real events, so you can validate your parsing and handling logic before going live.
Webhook Payload Structure
Each webhook payload contains metadata about the event and the affected resource. A typical payload includes:
event_type , The type of event that triggered the webhook (e.g., "document.signed")
timestamp , ISO 8601 formatted date and time when the event occurred
document_id , Unique identifier for the document (if applicable)
deal_room_id , Unique identifier for the Deal Room (if applicable)
recipient_id , Unique identifier for the recipient (if applicable)
recipient_email , Email address of the recipient
sender_id , Unique identifier for the sender
data , Additional event-specific information (e.g., signature timestamp, engagement metrics)
Use the webhook detail view in Settings to inspect the actual payload structure for specific events. You can view recent payloads and their delivery status to debug integration issues.
Webhook Retry Logic
If your endpoint fails to respond successfully to a webhook delivery, GetAccept automatically retries the request. The retry behavior includes:
Multiple retry attempts over an extended period
Exponential backoff , time between retries increases with each attempt
Retry status visible in the webhook detail view , you can see the number of retries and results for each event
For a webhook delivery to succeed, your endpoint must respond with an HTTP status code in the 2xx range (e.g., 200, 201). Responses outside that range (4xx, 5xx) are treated as failures and trigger retries.
IP Whitelisting for Webhook Security
If your webhook endpoint requires IP whitelisting for security, GetAccept sends webhooks from a set of static IP addresses. Refer to the article on Webhook IP whitelisting for the current list of IP addresses to add to your firewall or endpoint access controls.
Authentication and Custom Headers
To secure your webhook endpoints, you can configure custom HTTP headers that GetAccept includes with every webhook request. Common authentication methods include:
API Key Header , Add a custom header like
X-API-Key: your-secret-keyand verify it in your endpoint logicBearer Token , Include an Authorization header:
Authorization: Bearer your-tokenCustom Headers , Define any additional headers needed for your system (e.g.,
X-Webhook-Signature)
Configure these headers when creating or editing the webhook. Your endpoint should validate all incoming requests using these headers before processing the payload.
Related Articles
For more information on integrations and automation, see:
Integrations settings , Overview of all GetAccept integration options
Getting Started with GetAccept Automation , Alternative to webhooks for workflow automation
Webhook IP whitelisting , IP addresses for firewall configuration