Skip to main content

Webhooks

Webhooks let your tools receive real-time updates whenever important activity happens on OfferLab — such as updates on new orders you receive, changes to subscriptions you sell, or when you complete a new referral.

A webhook tells another tool the moment something happens in OfferLab, so your systems stay in step without anyone refreshing a page or exporting a file.

This guide covers what webhooks are, what OfferLab can tell you about, and how to set one up using Zapier, which is the route we recommend today.

What is a webhook?

Most tools make you ask. A webhook flips that around: instead of you checking OfferLab for new orders, OfferLab tells you the instant one lands.

It arrives as an HTTP POST request with a JSON body, sent to a URL you control. That means you can:

  • Sync OfferLab data into your CRM, fulfillment system, or analytics tools

  • Trigger an automation the moment an order or renewal happens

  • Update a membership site or course platform automatically

  • Coordinate creator and seller workflows across several tools at once

If a delivery fails, we retry it automatically on a set schedule, so a receiver that blips for a minute does not cost you the event.

💡 Webhooks are an advanced feature. To use them directly you need somewhere that can receive and process JSON. If that sounds like a project, the Zapier route below does that part for you.

What each event looks like

Every event we send carries the same envelope, whatever the event happens to be:

  • The event type, for example order.created or subscription.updated

  • A unique event ID

  • A timestamp

  • The team ID the event belongs to

  • A payload describing the thing that changed

The simplest way in: connect Zapier

Most people never need to touch a raw webhook, because the OfferLab Zapier app already listens for the things you care about and hands them to whatever tool you point it at.

Connecting it takes about a minute: go to Settings, then Connections in OfferLab, find Zapier, and tap Connect. From there you pick a trigger, such as New Order, Order Updated, New Customer, New Subscription or New Collaboration, and choose what should happen next. The Zapier guide walks through the whole thing and lists every trigger, action and search we support.

💡 Behind the scenes this creates the webhook subscription for you, so everything below about events and payloads still applies. You just never have to wire it up by hand.

If you want the raw payload

Sometimes you want the JSON itself, either because you are building against it or because the tool you are connecting is not in Zapier's catalog. The Webhooks by Zapier app gives you a URL that catches the event and shows you exactly what arrived, and Make works the same way if you prefer it.

This walkthrough goes through it end to end:

  1. In Zapier, create a new Zap and pick Webhooks by Zapier as the trigger, with the Catch Hook event.

  2. Copy the custom webhook URL that Zapier gives you.

  3. Add whatever you like as the action step, such as a row in a spreadsheet, a record in your CRM, or a message in Slack.

  4. Trigger a real event in OfferLab, for example a test order, so you can see the payload before you rely on its shape.

Events you can subscribe to

These are the events OfferLab emits today. For the payload each one carries, see the webhook events reference.

Area

Events

Orders

order.created, order.updated, order.completed, order.deleted

Invoices and payments

orders/invoice.created, orders/invoice.updated, orders/invoice.paid, orders/invoice.completed, orders/invoice.refunded, orders/invoice.status_changed, orders/invoice.deleted

Subscriptions

subscription.created, subscription.updated, subscription.cancel_requested, subscription.cancelled, subscription.deleted

Customers

customer.created, customer.updated

Commissions

commission.created, commission.updated, commission.deleted

Collaborations

collaboration.approved, collaboration.auto_approved

Team and members

membership.created, membership.updated, membership.team_member_created, membership.deleted, invitation.created, invitation.updated, invitation.deleted, user.created, team.referred, team.affiliate_signed_up

💡 If you need something that is not on this list, tell us. The catalog grows based on what people ask for, and we would rather hear it than have you build a workaround.

Already using webhooks?

Nothing has changed for you. Existing subscriptions keep delivering exactly as they were, and there is nothing you need to do.

If you want to add, change, or remove one, get in touch and we will sort it out with you. We are rebuilding how webhooks get configured, and we would rather set yours up correctly than leave you working against a page that is on its way out.

Did this answer your question?