Webhooks

Configure webhooks to receive real-time notifications about orders, subscriptions, payments, and other critical events in your Sales Channel.

Overview

Webhooks allow Techrar to push event notifications to your server in real-time. Instead of polling our APIs for status changes, we'll send HTTP POST requests to your configured endpoint whenever important events occur.

Setup Methods

You can register webhooks in two ways:

Via Portal (Recommended for quick setup)

Via API (Coming Soon)

Register Webhook via Portal

Navigate to Settings → Webhooks

Click Create Webhook

Configure your webhook:

URL: Your endpoint that will receive webhook notifications

Events: Select which events to subscribe to

Custom Headers: Add optional headers (e.g., authentication tokens)

Active Status: Enable or disable the webhook

Save and copy your Secret Key (used for signature verification)

List of techrar Meals Events

Name	Description
m.order.completed	This is triggered when an order has been succesfully paid
m.subscription.started	This is triggered when a subscription is started
m.subscription.canceled	This is triggered when a subscription is canceled
m.subscription.ended	This is triggered when a subscription is ended
m.subscription.reopened	This is triggered when a subscription is re-opened again
m.complaint.issued	This is triggered when a complaint is issued
m.complaint.updated	This is triggered when a complaint is updated by the merchant

Webhook Payload Structure

All webhook requests include:

{
  "app_id": 123,
  "timestamp": 1640000000,
  "event": "subscription.created",
  "data": {
    // Event-specific data object
  }
}

Signature Verification

Every webhook request includes an X-Signature header for security verification.

Verify Signature

Always verify signatures before processing webhook data to ensure the request is from Techrar.

Handling Webhooks

Best Practices

Respond Quickly: Return 200 OK immediately, then process asynchronously

Verify Signatures: Always validate the X-Signature header

Handle Idempotency: Use event IDs to prevent duplicate processing

Implement Retry Logic: We retry failed webhooks with exponential backoff

Log Everything: Keep webhook logs for debugging and auditing

Retry Policy (Coming Soon)

If your endpoint returns a non-2xx status or times out:

Attempt 1: Immediate retry

Attempt 2: 1 minute later

Attempt 3: 5 minutes later

After 3 failed attempts, the webhook is marked as failed and will not be retried automatically.

We currently send a webhook notification only once. We are working on a retry logic.

Monitoring & Logs

View Webhook Logs

Access webhook delivery logs via Portal -> Settings → Webhooks → View Logs

Logs include:

Timestamp

Event type

HTTP status code

Response body

Delivery status (success/failed/pending)

Duplicate Events

Use event timestamps and IDs to detect duplicates

Implement idempotency keys in your processing logic

Store processed event IDs to skip duplicates

Overview#

Setup Methods#

Register Webhook via Portal#

List of techrar Meals Events#

Webhook Payload Structure#

Signature Verification#

Verify Signature#

Handling Webhooks#

Best Practices#

Retry Policy (Coming Soon)#

Monitoring & Logs#

View Webhook Logs#

Duplicate Events#

Overview

Setup Methods

Register Webhook via Portal

List of techrar Meals Events

Webhook Payload Structure

Signature Verification

Verify Signature

Handling Webhooks

Best Practices

Retry Policy (Coming Soon)

Monitoring & Logs

View Webhook Logs

Duplicate Events