Wemob
API reference

Webhooks

Get notified when things happen in your Wemob account.

Webhooks are the opposite of API calls. Instead of you asking Wemob for information, Wemob sends you information when something interesting happens. You give Wemob a URL you control, and it sends a POST request to that URL every time one of the events you've subscribed to fires.

What webhooks are#

Common reasons to use webhooks:

  • Post a message in your team chat when a deploy succeeds or fails
  • Send yourself an email when someone makes a purchase from your store
  • Sync new orders into your own back-office system
  • Kick off a build or backup job when something changes

Create a webhook#

MethodPathBody
POST/v1/webhooks{ url, events: [...], description }

Available events#

  • app.created — a new project was made
  • app.deployed — a project was successfully published
  • app.deploy_failed — a publish attempt failed
  • order.created — a customer placed an order in your store
  • order.paid — an order was successfully paid for

What the payload looks like#

Every webhook request is a JSON POST with a consistent shape: an event type, a timestamp, and the relevant data. The Studio's webhook page shows you an example payload for each event type, so you know exactly what to expect.

Verifying requests#

Check the signature
Every webhook request includes an X-Wemob-Signatureheader. You should verify this signature against your webhook's secret before trusting the payload. Otherwise, anyone who guesses your webhook URL could send fake events. The Studio shows you the secret when you create a webhook.
Last updated · April 11, 2026