Skip to content
PartyPad logoPartyPad

Connect your booking system with webhooks

Send orders and customers from the booking system you already use into PartyPad automatically, and keep the connection healthy.

If customers book you through another system, it can send each new or changed order to PartyPad as a webhook, and PartyPad turns it into an event with its customer. The Webhooks page is where you register each system allowed to send. The flow runs one way: PartyPad doesn't send orders back.

Before you start

  • You need the Tenant Admin role. Anyone else sees "You don't have permission to manage webhooks."
  • Your booking system has to send webhooks signed with a shared secret.
  • Automatic tasks for incoming confirmed orders are a Professional plan feature. Orders still arrive on the Free plan; you create their tasks by hand.

Add your booking system

  1. Open Webhooks and click Add Source.
  2. Give it a Name.
  3. Pick the Source System: BounceOps v1, Bouncer v3, Inflatable Office or Custom System.
  4. Click Generate next to Webhook Secret, or paste the secret your booking system gave you. Copy it somewhere safe before you save. PartyPad won't show it again.
  5. Optionally fill in IP Whitelist with the addresses your booking system sends from, comma-separated. Once it's set, PartyPad refuses a correctly signed delivery from any other address. Leave it empty to accept any address. Check with your booking system before you fill it in: if its servers move, orders stop arriving until you update the list.
  6. Click Create Source.

A source accepts every order event its system sends: created, updated, confirmed, cancelled and export.

You can have one source per source system. Adding a second source for the same system overwrites the first one's name and secret.

Set up the sending side

In your booking system's webhook settings, enter:

  • URL: https://gopartypad.com/api/v1/webhooks/orders, sent as a POST with a JSON body.
  • Secret: the Webhook Secret from step 4. The system signs each delivery with it (HMAC SHA-256 of the body) and sends the signature in the X-Webhook-Signature header.
  • Company: your Company ID in the X-Tenant-Id header. That's the URL Slug under Settings, Organization.
  • User-Agent: PartyPad picks which source's secret to check from this header. It must contain BounceOps-v1, Bouncer-v3 or InflatableOffice for those systems. Anything else is checked against your Custom System source.

Each delivery's timestamp must be within 24 hours of now. A delivery that fails the signature check is refused and nothing is written.

What PartyPad does with an order

  • Customers are matched by email. A new email creates a customer; a known one updates it.
  • Orders are matched by event name, which is normally the order number, ignoring capitals. A new name creates an event, and a known one updates it.
  • An order sent as Confirmed gets its delivery, setup and pickup tasks on the Professional plan. See How tasks are generated.
  • A cancelled or declined order becomes Cancelled, and its open tasks are cancelled with it.
  • A changed delivery or pickup time moves the matching tasks.
  • The same delivery sent twice is recognized and applied once.

Your booking system owns these orders' status. Approving crew work in PartyPad doesn't move them to Delivered or Completed. See Order statuses.

Keep it healthy

The Webhook Sources table shows each source's Status, Health score and Last Activity, the last delivery that passed the signature check.

Each delivery with a bad signature lowers the health score. After 10 in a row, PartyPad turns the source off. A good delivery resets it to 100%.

When an accepted delivery fails to process, PartyPad emails you the order numbers and the error. On the Professional plan, Webhook Delivery History under Settings, Integrations lists recent deliveries and whether each one completed or failed.

Manage a source

Open the menu in a source's Actions column:

  • Disable stops accepting deliveries from it. Enable turns it back on.
  • Regenerate Secret replaces the secret and shows the new one once. The old one stops working at once, so update your booking system straight away.
  • Delete removes the source. Deliveries from that system are refused from then on.

Not working?

  • Last Activity says "Never": check the URL, X-Tenant-Id, User-Agent and secret on the sending side, and that the source is Active.
  • The source keeps turning itself off: the secrets don't match. Regenerate it and update your booking system.
  • Orders arrive but have no tasks: see Tasks not being created.