Webhooks

Receive real-time notifications when events happen in your marketplace. Connect to external systems like Zapier, Make, or your own backend.

What are Webhooks?

Webhooks are automated messages sent from your marketplace to external systems when specific events occur. Think of them as real-time notifications that let other applications know something happened.

Event Occurs

New order placed

→

Webhook Fires

HTTP POST request

→

Your System

Processes data

Common Use Cases

Inventory Management

Sync orders to your inventory system when purchases are made.

Custom Notifications

Send alerts to Slack, Discord, or email when events occur.

Automation Platforms

Trigger workflows in Zapier, Make (Integromat), or n8n.

CRM Updates

Update your CRM when new sellers register or orders complete.

Analytics Dashboards

Build custom analytics by streaming events to your data warehouse.

Fulfillment Systems

Automatically trigger shipping and fulfillment workflows.

Available Events

Subscribe to any combination of these events when creating a webhook endpoint:

Event	Triggered When
order.created	A new order is placed and payment is confirmed
seller.registered	A new seller signs up for your marketplace

More events (order.completed, listing.created, etc.) will be added in future updates. You'll be able to subscribe to new events as they become available.

Creating a Webhook Endpoint

Follow these steps to set up a webhook endpoint:

Go to Store Settings → Webhooks

Click "Add Endpoint"

Enter your endpoint URL (must be HTTPS)

https://your-server.com/webhook/prometora

Select the events you want to receive

Click "Create Endpoint" to save

Copy the signing secret for verification

Webhook Security

Each webhook endpoint receives a unique signing secret. Use this to verify that incoming requests are genuinely from Prometora and haven't been tampered with.

Signing Secret

whsec_abc123def456...

Store this secret securely. Never expose it in client-side code.

Security Best Practice

Always verify the webhook signature in your endpoint before processing the data. This prevents attackers from sending fake events to your system.

Webhook Payload

Webhook requests are sent as HTTP POST with a JSON body:

{
  "id": "evt_abc123",
  "type": "order.created",
  "created": "2026-01-04T12:00:00Z",
  "data": {
    "id": "ord_xyz789",
    "total": 9999,
    "currency": "usd",
    "customer": {
      "email": "[email protected]",
      "name": "John Doe"
    },
    "items": [
      {
        "listing_id": "lst_123",
        "title": "Handmade Pottery",
        "quantity": 1,
        "price": 9999
      }
    ]
  }
}

Delivery Logs

Every webhook delivery is logged so you can see exactly what happened. Expand the "Recent Deliveries" section on any webhook to view:

Status: Success (green) or failure (red) badge with HTTP status code
Event type: Which event triggered the delivery
Response time: How long your endpoint took to respond (in milliseconds)
Retry indicator: Shows "Retry #1" or "Retry #2" for retried deliveries
Timestamp: When the delivery was attempted

Delivery logs are kept for 7 days. The 10 most recent deliveries are shown per endpoint.

Automatic Retries

If a delivery fails (your endpoint returns a non-2xx status code or times out), Prometora will automatically retry the delivery up to 2 more times with increasing delays:

Attempt	Delay	Description
1st (original)	Immediate	Sent right when the event occurs
2nd (retry #1)	~1 minute	First retry after initial failure
3rd (retry #2)	~10 minutes	Final retry attempt

The exact same payload is resent on each retry, so your endpoint will receive identical data. Each retry attempt appears as a separate entry in the delivery logs.

Auto-Disable Protection

To protect both your system and ours, webhooks are automatically disabled after 10 consecutive failures. This prevents repeated delivery attempts to endpoints that are consistently unreachable.

Webhook Disabled?

If your webhook was auto-disabled, fix the issue with your endpoint and then re-enable it from the webhook settings. The consecutive failure counter resets when a delivery succeeds.

Managing Webhooks

Enable/Disable

Toggle webhooks on or off without deleting them. Disabled webhooks won't receive any events.

View Activity

Each webhook shows when it was last triggered and how many consecutive failures have occurred. Expand "Recent Deliveries" to see detailed delivery history.

Delete

Remove webhook endpoints you no longer need. This action cannot be undone.

Integration Examples

Zapier

Use Zapier's "Webhooks by Zapier" trigger to catch Prometora events and connect to 5,000+ apps.

Learn more about Zapier Webhooks

Make (Integromat)

Create a "Custom Webhook" module in Make to receive Prometora events and build complex automations.

Learn more about Make Webhooks

Slack Notifications

Slack expects a specific payload format, so you need a middleware step to transform Prometora events into Slack messages. Two easy options:

Use Zapier or Make as a bridge — set up a "Webhooks" trigger and a "Slack" action
Write a small serverless function that receives the Prometora payload and posts a formatted message to Slack's Incoming Webhook URL

Pro Tips

Start with a test endpoint (like webhook.site) to see the payload structure
Your endpoint should respond with a 2xx status within 10 seconds to count as successful
Process webhooks asynchronously to avoid timeouts
Implement idempotency using the event ID to handle retries and duplicate deliveries gracefully
Check the delivery logs regularly to ensure your endpoint is responding correctly

Business Plan Feature