REST access for catalog, stock, and orders
API key authentication and inbound webhooks.
ElintOm exposes REST endpoints for product catalog sync, stock checks, sales summaries, and order creation. Calls authenticate with an API key header and a user token. Webhooks receive UrbanPiper order updates and WhatsApp delivery receipts. Documentation for your account is issued on a demo. This page does not publish a version number, an OAuth flow, or a database brand.
- Catalog, stock, sales, and order payloads
- API key and user token
- UrbanPiper and WhatsApp webhooks
- Account documentation on request
What a developer can call
Catalog and stock
Read products and current quantities so an external menu or shelf system stays aligned.
Orders
Create orders and read sales summaries. The restaurant captain app uses the order-taking API. The webshop uses the shop API.
Authentication
Send the API key header with the user token. Do not put a key in a public website.
Webhooks
ElintOm listens for UrbanPiper order-status callbacks and WhatsApp delivery receipts.
What this page is not
It is not a public OpenAPI file, an SDK download, or a schema diagram. Ask for the current collection during onboarding.
Related channels
Payment partners, UrbanPiper, NIC e-invoice, and WhatsApp are also described on their own module pages.
API and Webhooks FAQs
Request it on a demo for the account you are integrating. The resources page on this website is not a substitute for that collection.
The API key is sent as X-API-KEY, together with the user token your integration user was given.
See this workflow on a 15-minute demo
The team follows up after you submit the form, walks through inventory, POS, and your channels, then scopes pricing from that conversation—not a public price list.
