Jomioz Webhooks: Receive Real-Time Event Notifications

Jomioz webhooks let you receive instant HTTP notifications whenever something meaningful happens on your account — such as a resource being created or an event firing. Instead of polling the API repeatedly, you register an endpoint on your server and Jomioz delivers a signed JSON payload to it the moment the relevant activity occurs, keeping your application in sync in real time.

Creating a Webhook

Navigate to the Webhooks page

In the Jomioz Dashboard, go to Integrations → Webhooks. You’ll see a list of any existing webhooks on your account.

Click New Webhook

Select New Webhook in the top-right corner to open the webhook creation form.

Configure your endpoint and events

Enter the publicly reachable HTTPS URL where Jomioz should send notifications. Then select one or more event types you want to subscribe to. You can subscribe to all events or choose a specific subset.

Save and store your webhook secret

Click Save. Jomioz generates a unique webhook secret for this endpoint — copy it immediately and store it securely. You’ll use this secret to verify that incoming payloads genuinely originate from Jomioz.

Webhook Payload

Every webhook request Jomioz sends to your endpoint is an HTTP POST with a Content-Type: application/json header. The body contains a consistent JSON structure regardless of the event type.

{
  "id": "wh_01hxyz4k9mq2pv3rst5uvwxyz",
  "event": "resource.created",
  "resource_id": "res_01hxyz1a2b3c4d5e6f7g8h9ij",
  "payload": {
    "id": "res_01hxyz1a2b3c4d5e6f7g8h9ij",
    "name": "My Resource",
    "status": "active",
    "created_at": "2024-06-15T10:30:00Z"
  },
  "timestamp": "2024-06-15T10:30:01Z",
  "signature": "3a7f2c8d1b4e9f6a0c5d2e8b7a1f4c3d6e9b2a5f8c1d4e7b0a3f6c9d2e5b8a1f"
}

Field	Type	Description
`id`	string	Unique identifier for this webhook delivery attempt
`event`	string	The event type that triggered this notification
`resource_id`	string	The ID of the Jomioz resource related to this event
`payload`	object	Full snapshot of the resource at the time of the event
`timestamp`	string	ISO 8601 UTC timestamp of when the event occurred
`signature`	string	HMAC-SHA256 signature for verifying payload authenticity

Verifying Signatures

Always verify the signature on every incoming webhook before processing the payload. Jomioz signs each delivery using HMAC-SHA256 with your webhook secret as the key and the raw request body as the message. Compare the result against the x-jomioz-signature header — if they match, the payload is authentic.

const crypto = require('crypto');

function verifyWebhook(rawBody, headers, webhookSecret) {
  const signature = crypto
    .createHmac('sha256', webhookSecret)
    .update(rawBody)
    .digest('hex');

  const isValid = signature === headers['x-jomioz-signature'];
  return isValid;
}

import hmac
import hashlib

def verify_webhook(raw_body: bytes, headers: dict, webhook_secret: str) -> bool:
    signature = hmac.new(
        webhook_secret.encode(),
        raw_body,
        hashlib.sha256
    ).hexdigest()

    is_valid = signature == headers.get('X-Jomioz-Signature')
    return is_valid

Use the raw request body bytes when computing the signature — do not parse the JSON first. Parsing and re-serializing the body can alter whitespace or key ordering, causing the signature check to fail even for legitimate payloads.

Supported Events

Subscribe to any combination of the following event types when configuring a webhook.

Event	Description
`resource.created`	Fired when a new resource is successfully created on your account
`resource.updated`	Fired when any field on an existing resource is modified
`resource.deleted`	Fired when a resource is permanently deleted
`event.fired`	Fired when a tracked event is recorded against a resource

Retry Behavior

If your endpoint does not return a 2xx HTTP status code within 10 seconds, Jomioz marks the delivery as failed and schedules a retry. Jomioz retries a failed delivery up to 5 times using exponential backoff, with increasing delays between each attempt.

Attempt	Delay after previous failure
1 (initial)	Immediate
2	1 minute
3	5 minutes
4	30 minutes
5	2 hours

After five failed attempts, the delivery is marked as permanently failed. You can view failed deliveries and manually replay them from Dashboard → Integrations → Webhooks → [your webhook] → Delivery Logs.

Your endpoint must return a 200 status code within 10 seconds of receiving a webhook. If it times out or returns a non-2xx response, Jomioz treats the delivery as failed and will retry it. Perform any time-consuming processing asynchronously — acknowledge the webhook immediately, then handle the payload in a background job.

Get Started

Core Concepts

Guides

Integrations

Support

Jomioz Webhooks: Receive Real-Time Event Notifications

Creating a Webhook

Webhook Payload

Verifying Signatures

Supported Events

Retry Behavior

​Creating a Webhook

​Webhook Payload

​Verifying Signatures

​Supported Events

​Retry Behavior

Creating a Webhook

Webhook Payload

Verifying Signatures

Supported Events

Retry Behavior