Skip to content
  1. Blog
  2. API

How to Secure BoldSign API Webhooks with IP Whitelisting

TL;DR: Internet protocol (IP) whitelisting lets your webhook endpoint accept requests only from BoldSign’s IP address for your region and turn away the rest. Pair it with the signature check and Hypertext Transfer Protocol Secure (HTTPS), and your backend acts only on genuine events. Our webhooks introduction explains how our webhooks work.

You have connected BoldSign webhooks to your backend. When a document is signed, your code updates records, creates user accounts or releases a payment.

Your webhook endpoint is public, though. Anyone who finds the address can send it a fake event. This guide shows how to let in only our requests, then adds the other checks a production endpoint needs.

What is IP whitelisting for webhooks?

IP whitelisting means your server accepts requests from a short list of IP addresses and drops the rest. For a webhook, the list holds the address we send events from.

Think of a guest list at a private event. The door staff check each name before anyone walks in, and the hosts inside never meet the uninvited. Your firewall plays the door staff, and your webhook handler plays the host.

The filter runs before your code does. Bots and scanners that probe your webhook route never reach your logic.

Why does a public webhook endpoint need protection?

A webhook event often starts work that is hard to undo. A fake event could start that work without any document being signed.

  • A fake “signed” event creates accounts for people nobody hired.
  • A spoofed callback moves a contract to completed in your sales system.
  • A forged event releases funds before the loan agreement is signed.
  • Repeated hits on the address fill your logs and hide real problems.

IP whitelisting is a cheap first layer against all four. You still need the checks later in this guide.

Which IP addresses does BoldSign send webhooks from?

We send webhooks from one IP address per region. Whitelist the address for the region that hosts your BoldSign account.

Region IP address to whitelist
US 35.243.182.124
Europe 34.141.138.53
Canada 34.130.12.142
Australia 34.40.190.114

Note: Pick the region that hosts your BoldSign account, which may differ from where your servers run. Check the BoldSign webhook IP addresses page for the current list before you change a rule.

How do you set up IP whitelisting for BoldSign webhooks?

Set the rule where traffic first enters your network, then test it from both sides. You need access to your firewall or gateway and the address of your webhook route, such as /webhooks/boldsign.

  1. Find the region that hosts your BoldSign account.
  2. Note that region’s IP address from the table above.
  3. Add a rule that allows your webhook route from that address only.
  4. Block or drop requests to the route from every other address.
  5. Keep the address in configuration for each environment, not in code.

Where can you add the rule?

Most stacks give you more than one place to filter by IP address. Choose the layer your team already manages.

  • A cloud security group in front of your server
  • A web application firewall (WAF) or content delivery network (CDN) rule
  • Allow and deny rules in your reverse proxy
  • An API gateway with IP-based access control

How do you test the rule?

Trigger a real event from BoldSign and confirm your backend receives it. The source address in your access log should match the address you whitelisted.

Then send a request to the same route from another machine. Expect a 403 response. Our guide to automatically downloading signed documents with webhook callbacks gives you a working flow to test with.

How do you check the source IP in Node.js?

Filter at the edge first, then add a check in your app as a second layer. Here is a short Express example you can adapt.

// Behind one trusted proxy, let Express read the client address that proxy added.
app.set("trust proxy", 1);

const allowedIps = new Set(["35.243.182.124", "34.141.138.53"]);

app.post("/webhook", (req, res) => {
  const ip = req.ip;

  // Normalize IPv6-mapped IPv4 (e.g., ::ffff:35.243.182.124)
  const normalizedIp = ip.replace("::ffff:", "");

  if (!allowedIps.has(normalizedIp)) {
    return res.status(403).send("Forbidden");
  }

  // Valid request; proceed
  // Process payload here
  res.sendStatus(200);
});

The sample lets in the US and Europe addresses. Keep only the address for your region.

Note: Any client can send an x-forwarded-for header with any value. Trust it only when your own load balancer or gateway sets it. Set trust proxy to match the number of proxies in front of your app.

What else should you check besides the IP address?

An IP check tells you where a request came from, not what it says. Three more checks cover the rest.

How do you verify the webhook signature?

We sign every webhook event with a hash-based message authentication code (HMAC). The signature travels in the X-BoldSign-Signature header.

You compute the same value from your webhook’s signing secret, the event time and the raw body. Reject the request when the two values differ. Our guide to verify webhook events walks through each step and shows where to reveal the secret.

Can you add your own secret header?

Yes. You can add custom headers to our webhook requests, including secret headers and basic authentication.

We store a secret header’s value encrypted and send it with each request. Your endpoint then rejects any request that arrives without the expected value.

What should your handler check in the payload?

Serve your endpoint over HTTPS so events stay encrypted on the way. Then check the event type and required fields before you change anything.

Our event context object, in beta, tells you who triggered an event and what changed. Use each event’s unique ID to skip duplicates.

What are the limits of IP whitelisting?

IP whitelisting checks the sender’s address, and nothing more. Plan for these gaps.

  • It cannot tell you whether a payload was changed; the signature check covers that.
  • Development, staging and production each need the right rule.
  • It filters outside traffic only, so you still need access control inside your network.
  • Teams can stop at whitelisting and forget HTTPS or payload checks.

Which logs should you watch for webhooks?

Watch four kinds of logs, and send them to the tool your team already uses. Logs show the cause of most webhook problems quickly.

  • Access logs, to confirm requests come from the address you expect
  • Error logs, to catch blocked requests that point to a wrong rule or probing
  • Application logs, to see what your handler did with each event
  • Alerts for repeated rejected requests or sudden spikes

A blocked real event is a failed delivery for us, so we retry it. Our webhook configuration and lifecycle page lists the retry times and how to resend an event.

Where does IP whitelisting matter most?

It matters most where a webhook starts work that costs money or grants access. A few common flows show why.

  • In HR onboarding, a signed offer letter creates accounts and assigns tools.
  • In lending, funds go out only after a signed loan agreement arrives.
  • In healthcare, a signed consent form updates the patient’s electronic health record (EHR).
  • In licensing, a permit application moves forward after a genuine signing event.

In each flow, a forged event would act on a document nobody signed. The IP filter stops most of those attempts at the door.

Which BoldSign plan do you need for webhooks, and what does it cost?

Webhooks and live API access come with the Enterprise API plan. It starts at $30 a month with 40 envelopes, billed yearly, and extra envelopes cost $0.75 each.

You can build and test your webhook endpoint first in our free API sandbox. Prices are in USD, as listed on the BoldSign pricing page in November 2026.

How do you get started with secure webhooks?

Start in a sandbox with a staging endpoint. Add the IP rule and the signature check there, then copy the same setup to production.

Frequently asked questions

How does IP whitelisting protect a BoldSign webhook?

Your firewall or gateway accepts requests to the webhook address only from our IP address for your region. Requests from anywhere else get turned away before your code runs.

Is IP whitelisting enough to secure webhooks?

No, it covers only where a request comes from. Add the signature check on the X-BoldSign-Signature header and serve your endpoint over HTTPS so you also know the content is genuine.

Which BoldSign IP address should I whitelist?

Use the address for the region that hosts your BoldSign account: US, Europe, Canada or Australia. Our developer documentation lists the current address for each region.

Can I whitelist IP addresses behind a load balancer or content delivery network?

Yes. Put the rule on the load balancer, content delivery network or gateway that first receives the request. Your code then sees only traffic that already passed the filter.

Can someone fake the x-forwarded-for header?

Yes, any client can send that header with any value. Trust it only when your own proxy sets it, and configure your framework to read the address that proxy added.

How do I verify that a webhook came from BoldSign?

Check three things: the source IP address, the signature in the X-BoldSign-Signature header and the event type. The signature uses your webhook's signing secret, which you reveal on the webhook overview page.

What happens if my endpoint blocks a real BoldSign webhook?

We treat it as a failed delivery and retry it with growing gaps, from 1 minute up to 24 hours. You can also resend an event from the webhook history once you fix the rule.

Which BoldSign plan includes webhooks?

Webhooks come with the Enterprise API plan, which starts at $30 a month with 40 envelopes, billed yearly. You can build and test them first in a free API sandbox account.

Ranjitha Vazhivittan

Ranjitha is a skilled software developer with 3 years of experience at BoldSign. Alongside her technical expertise, she has a passion for writing and enjoys sharing thoughtful insights on technology and development. Beyond work, she stays curious by exploring emerging tools and trends, constantly seeking opportunities to learn and grow.

More posts by Ranjitha Vazhivittan
Get started

Sign up for your free trial today!

Start free trial
  • 30-day free trial
  • No credit card required