What is Webhook IP Whitelisting?

Webhook IP whitelisting is a security practice where you configure your firewall or network security tools to allow incoming requests only from specific IP addresses. GetAccept sends webhook notifications from a limited set of IP addresses, and if your network doesn't recognize these addresses, your firewall may block the webhook delivery. Whitelisting GetAccept's webhook IPs ensures that notifications reach your system reliably without being filtered as potential security threats.

Note: Webhook delivery will fail if GetAccept's IP addresses aren't whitelisted in your firewall.

Why Webhooks May Be Blocked

Webhooks are automated, outbound HTTP requests that GetAccept sends to your system whenever certain events occur (like a document being signed or a deal room being created).

Pro-tip: Keep your whitelist updated whenever GetAccept notifies you of IP address changes.

If your organization runs a firewall or uses network-level security controls, incoming requests from unknown IP addresses are often blocked by default as a protection measure. Without whitelisting GetAccept's IP addresses, webhook payloads will fail to reach your endpoint, even if your webhook configuration in GetAccept is correct.

GetAccept Webhook IP Addresses by Region

GetAccept is hosted on Amazon Web Services infrastructure across three main regions. Depending on your data center location (set during account creation), webhooks originate from one of the following IP ranges. You should whitelist all IPs for your region to ensure reliable webhook delivery.

EU Region

3.127.46.199
35.157.43.138
52.58.99.121
52.59.99.121

US Region

44.232.34.102
44.233.210.197
44.233.237.84

APAC Region

18.139.16.85
3.0.71.130
52.76.113.194

Note: Your data center region is set when you create your GetAccept account and cannot be changed later. If you're unsure which region your account uses, contact your GetAccept administrator or support team.

How to Whitelist GetAccept IPs in Your Firewall

The exact steps for whitelisting IPs depend on your firewall solution. Below is generic guidance for common approaches; consult your firewall documentation for specific instructions.

For Network/Enterprise Firewalls

Log in to your firewall management console (e.g., Palo Alto Networks, Fortinet FortiGate, Cisco ASA)
Navigate to Outbound Rules or Access Control Lists (ACLs)
Create a new rule allowing inbound HTTPS traffic (port 443) from the GetAccept IP addresses for your region
Set the destination to your webhook endpoint URL
Save and apply the rule

For Cloud Security Groups (AWS, Azure, GCP)

Open your cloud provider's security group or network security settings
Add an inbound rule allowing traffic on port 443 (HTTPS)
Enter the GetAccept IP addresses in the source field (e.g., as a CIDR block or individual IPs)
Save the changes

For Application-Level Firewalls (WAF)

Access your Web Application Firewall (WAF) settings
Whitelist the GetAccept IPs in the allowed sources list
Ensure HTTPS (port 443) traffic is permitted
Test the connection after applying changes

Which Events Trigger Webhooks

Webhooks are event-driven , they fire automatically when specific actions occur in GetAccept. Common webhook-triggering events include:

Document created, sent, or recalled
Recipient opened document or clicked a link
Document signed by all required parties
Document expired or rejected
Deal Room created, published, or updated
Participant joined or engaged with content
Form field completed by recipient
Chat message sent or comment added

By whitelisting these IP addresses, you ensure that real-time notifications of these events reliably reach your downstream systems (CRM, automation platform, data warehouse, etc.).

Testing Webhook Connectivity

After whitelisting GetAccept's IP addresses, verify that webhooks are being delivered correctly.

Using a Webhook Testing Service

Generate a temporary webhook URL using a service like Webhook.cool, RequestBin, or Postman
In GetAccept, navigate to Settings (top-right profile image) → Webhook Settings
Enter your test URL and select at least one event type to trigger
Send a test document or create a draft and perform an action that triggers the webhook
Check your testing service to confirm the webhook payload was received

Checking Webhook Logs in GetAccept

Go to Settings → Webhook Settings
Look for delivery logs or history that shows successful vs. failed webhook attempts
Failed deliveries often indicate IP blocking or network issues
Successful deliveries (HTTP 200 response) confirm the connection is working

Troubleshooting Webhook Delivery Failures

If webhooks are not reaching your system, follow these steps to identify the issue:

Verify IP Whitelisting

Confirm you've whitelisted all GetAccept IPs for your region
Check that your firewall rule allows inbound HTTPS (port 443) traffic
Verify the rule applies to your webhook endpoint domain
If using multiple firewalls or proxies, ensure all layers allow the traffic

Check Endpoint Configuration

Ensure your webhook endpoint URL is correct and publicly accessible
Confirm your endpoint accepts HTTPS requests (not HTTP)
Verify your endpoint returns an HTTP 200 or 2xx status code to acknowledge receipt
Check server logs on your endpoint to see if requests are arriving

Review Webhook Settings in GetAccept

Go to Settings (top-right profile image) → Webhook Settings
Confirm the webhook URL and event types are configured correctly
Verify the webhook is enabled (not paused or deactivated)
Test by triggering a manual event (e.g., send a test document)

Common Failure Reasons

IP not whitelisted: Firewall blocks the request before it reaches your endpoint
SSL/TLS certificate issue: Your endpoint has an invalid or expired certificate
Endpoint timeout: Your system takes too long to respond; GetAccept gives up
Authentication required: Your endpoint requires API keys or headers that aren't configured
Wrong region IPs: Whitelisted IPs don't match your account's data center location

If webhooks still fail after whitelisting and verification, contact your IT/network team to check server logs and confirm the firewall rules are correctly applied.

Configuring Webhooks in GetAccept

Whitelisting IPs is just the network-level preparation. To actually set up and configure which webhooks GetAccept sends, visit Settings (top-right profile image) → Webhook Settings. There, you'll define your endpoint URL, select which events trigger webhooks, and view delivery history. For detailed instructions on creating and managing webhooks in GetAccept, see the related articles below.

Important: Webhook configuration and IP whitelisting must both be in place. Even if your webhooks are configured correctly in GetAccept, they won't be delivered if the firewall blocks the IP address.