POS integration · Automation
Your shop’s events, signed and sent to your own system
Webhooks POS integration in ArmPOS sends your shop’s events to your own system’s HTTPS address, as JSON. Each delivery is signed with HMAC-SHA256, so your system can check it came from ArmPOS.
- JSON over HTTPS
- Signed with HMAC-SHA256
- Tried again up to 4 times
- Built in
How a webhook delivery works
- A sale is savedor a payment, an expense
- A JSON eventsale.created, with the sale
- Signed and sentX-Webhook-Signature, HMAC-SHA256
- Your system answersa 2xx, or ArmPOS tries again
What ArmPOS does with Webhooks, step by step
- A moment after a sale, payment, purchase or expense is saved, ArmPOS queues the event for each address that is on and chose it
- It POSTs a JSON payload: the event’s id, its name (such as sale.created), created_at, and data with the record as saved
- Each delivery is signed: X-Webhook-Signature is sha256= and the HMAC-SHA256 of the raw body, keyed with that address’s Signing secret
- X-Webhook-Event, X-Webhook-Delivery and X-Webhook-Attempt ride along, so your system can skip a delivery it already took
- Any 2xx answer is a success; otherwise ArmPOS retries after 1 minute, 5 minutes, 30 minutes and 2 hours, 5 tries in all
- Only an https:// address on the internet is taken, checked when saved and again before each send; a redirect is never followed
Which events a webhook sends
You choose them for each address, or tick Every event. Each is named as your developer sees it.
- Salessale.created, sale.updated, sale.deleted and sale_return.created. An update is sent when the total changes.
- Paymentspayment.created and payment.deleted for sales, and payment_purchase.created for purchases.
- Purchases and expensespurchase.created, purchase.updated and expense.created. A purchase update is sent when its total changes.
- New recordsclient.created, product.created and quotation.created.
- On the list, not sent yetpurchase.deleted, payment_purchase.deleted, expense.updated and expense.deleted, plus purchase returns, payments of returns, sale return edits and cash_register.opened.
- Work done in bulkA product import, or a batch of orders pulled from an online store, sends nothing.
Send a test posts webhook.test to the address, signed the same way, so your developer can check the signature first.
Where it works, and for whom
Countries
- Every country: your system needs only an https:// address on the internet
For
- Retail & grocery
- Fashion & beauty
- Health & pharmacy
- Phones & electronics
- Hardware & building materials
- Wholesale & distribution
- Hospitality
Set up in 3 steps
- Open Integrations › Automation › Webhooks, and click Set up.
- Click Set up under the list, type a Name and the Address your system gave you, and tick the Events to send.
- Click Save: ArmPOS adds the address and sends it a test. Edit shows its Signing secret for your developer.
Words you’ll see on the screens
- Add an address
- Name
- Address
- Events to send
- Every event
- Wait for an answer (seconds)
- Signing secret
- Make a new one
- Send a test
- Received
- Activity
What it doesn’t do
- It only sends: a message to ArmPOS’s receiving address is listed under Received, and changes nothing in the shop.
- Stock levels and low stock aren’t webhook events: Slack and Telegram carry stock alerts.
- No http:// or private network address: the address must start with https:// and be on the internet.
Questions
How do I verify an ArmPOS webhook signature?
Compute the HMAC-SHA256 of the raw request body with the address’s Signing secret, in hex. It must equal X-Webhook-Signature after its “sha256=” prefix.
Which webhook events can I subscribe to?
Sales, sale returns, payments, purchases, new expenses, and new customers, products and quotations: 13 events in all. The list shows more that aren’t sent yet.
What does my system receive?
A POST with a JSON body: id, event, created_at, and data holding the record’s id, its type and its fields as saved.
How often does ArmPOS retry a failed webhook?
After 1 minute, 5 minutes, 30 minutes and 2 hours. After the fifth try it’s marked Failed, and whoever runs your shop’s settings is told, at most once an hour.
How do I avoid handling one event twice?
Keep each X-Webhook-Delivery you have taken. A retry carries the same number, with X-Webhook-Attempt one higher.
Can a webhook go to an http address or a local server?
No. The address must start with https:// and be on the internet. ArmPOS checks it when you save and again before each send.
Can I get alerts in Slack or Telegram without a developer?
Yes. Slack and Telegram have their own integrations, which post your alerts with no code.
Works well with
Get Started
Run your shop on ArmPOS
Start free with point of sale and inventory management in one app. No card needed; upgrade when your business grows.
- 14-day free trial
- No card needed
- Android & iPhone
