Create a Connect key
Open Connect API and create an API key. Copy it once and give it only to your developer or POS provider.
Open Connect APIPartner Docs
Integration guide
A simple guide for connecting your shop, catalog, POS, stock updates, and order notifications to SnapAct. Use this when speaking with your store team, developer, or POS provider.
Plain-English setup
POS ready
Production safe
Quick meaning
Your POS can update SnapAct automatically.
If your store already uses a POS or inventory system, that system can send products, prices, stock count, and availability into SnapAct through Connect API. Buyers then see fresher products without you updating the same item twice.
POS system
Catalog, price, stock
SnapAct Connect
Live products
Buyer app
Connect your POS server
Your POS provider stores the key on their backend and sends product updates to SnapAct whenever price, stock, or availability changes.
Open API docsReceive orders back
Add a webhook if your POS should receive paid SnapAct orders and order status changes automatically.
Add webhookExact POS flow
What happens when POS is connected
- Product ID: your POS product ID becomes SnapAct `external_ref`.
- Price: your POS selling price becomes the final product price buyers see.
- Stock: your POS stock count becomes SnapAct verified quantity.
- Availability: in-stock, low-stock, out-of-stock, on-request, or scheduled-only controls buyer visibility.
- Orders: SnapAct can send paid order events to your POS through signed webhooks.
What to give your POS provider
The only details they need
| Item | Value |
|---|---|
| API base | https://connect.snapact.io |
| Catalog endpoint | POST /connect/v1/catalog/items |
| Inventory endpoint | GET /inventory/nearby |
| SDK | npm install @snapact/connect-sdk |
| Authentication | Authorization: Bearer {Connect API key} |
| Webhook events | order.paid, order.status.updated, catalog.item.upserted, catalog.item.deleted |
Security rule
Never put API keys in public code.
Connect keys belong on a secure server only. Do not place them in website JavaScript, mobile apps, browser extensions, cashier frontend screens, screenshots, or public support tickets. If a key leaks, revoke it and create a new one.
More detail
Full POS integration guide
This Markdown guide is better for sending to a POS provider or internal developer.