Webhooks
Connect the POS to external systems by forwarding events to a URL of your choice
Navigate to: Dashboard → System → Webhooks
For Shakira: Webhooks are an advanced feature used to connect your POS to tools like QuickBooks, Slack, or Zapier. KareTech Solutions can set these up for you.
Webhooks let the POS automatically send data to another system whenever something happens — an order completes, stock runs low, a refund is processed. The POS sends an HTTP POST request with event details in JSON format to any URL you configure.
Adding a Webhook Endpoint
- Click Add Endpoint
- Enter a Name (e.g., "QuickBooks Sales Feed", "Slack Inventory Alerts")
- Paste the URL provided by the external service
- Select one or more Events to subscribe to
- Optionally enter a Secret — a shared key used to verify payloads (see Security below)
- Click Save
The endpoint is immediately active and will receive events in real time.
Available Events
| Event | When it fires |
|---|---|
order.completed | An order is fully paid |
order.voided | An order is voided after payment |
order.refunded | A refund is processed |
inventory.low_stock | An inventory item drops below its reorder point |
inventory.out_of_stock | An inventory item reaches zero |
cash_session.opened | A cash shift is opened |
cash_session.closed | A cash shift is closed |
production.logged | A production log entry is saved |
Delivery Log
The Delivery Log tab shows every send attempt for each endpoint:
| Column | Meaning |
|---|---|
| Event | Which event triggered the delivery |
| Status Code | HTTP response (200 = success, 5xx = server error, — = connection failed) |
| Duration | How long the request took in milliseconds |
| Result | Green = success, Red = failed |
| Timestamp | When it was sent |
Click any row to see the full request payload and the server's response body.
If a delivery failed, fix the endpoint URL and test again using the Ping button on the endpoint card.
Webhook Security (Signatures)
When you set a Secret on an endpoint, every request includes an X-Webhook-Signature header containing an HMAC-SHA256 signature of the request body. The receiving system can verify this signature to confirm the request came from your POS and wasn't tampered with.
Example signature header:
Most integration platforms (Zapier, Make, n8n) handle signature verification automatically when you paste the secret into their settings.
Toggling an Endpoint
Click the Active toggle next to any endpoint to pause deliveries without deleting the endpoint. Useful if an external system is temporarily down.
Example Payload
Every webhook payload follows this structure: