Connect POS and RMS to every channel
The Integrations API connects your POS and RMS with every sales channel your merchant operates. If you have built or used an integration like Uber Eats Marketplace, the building blocks will feel familiar: authentication, stores, menus, and orders. The difference is scope — Uber Eats is one channel. Fire spark is your omnichannel aggregator intelligence layer. Instead of integrating each aggregator separately, you connect once to Fire spark. We sync menus with your POS and RMS, apply intelligence across all your channels, and inject orders back into the system where your kitchen and operations already run.New to Fire spark?
Start by connecting a merchant before building against the Integrations API.
What this integration does
Fire spark sits between your operational stack (POS, RMS, inventory) and your sales channels (app, web, kiosk, call center, Uber Eats, Rappi, PedidosYa, and more).| Layer | Role |
|---|---|
| POS / RMS | Source of truth for menus, pricing, availability, and order fulfillment |
| Fire spark | Syncs menus, enriches channels with intelligence, routes orders |
| Sales channels | Where customers discover, order, and pay |
- Authentication — secure API access for your integration
- Store management — which locations are live and how they operate
- Menu synchronization — what customers see in the aggregator app
- Order processing — receiving orders and sending them to your POS
How it works end to end
Authenticate your integration
Your server obtains an access token using OAuth 2.0 client credentials. All
Integrations API requests use this token.
Sync menus with POS and RMS
Fire spark pulls menu structure, items, pricing, and availability from your
POS or RMS. Operational changes flow from that source; you compose what
customers see per channel, store, fulfillment type, or schedule.
Apply intelligence across channels
Fire spark shapes each selling context — channel-specific menus, scheduling,
availability rules, and fulfillment options — without separate integrations
per variation. Your app, aggregators, and in-store surfaces can show
different assortments from the same synced foundation.
Receive orders from any channel
When a customer places an order on any connected channel, Fire spark sends a
webhook to your integration with the order payload.
Integration areas
The API is organized around the same domains you would expect from a marketplace integration, extended for omnichannel operations.Authentication
OAuth 2.0 client credentials secure server-to-server access. Your integration authenticates once and calls endpoints for menus, stores, channels, orders, and fulfillment.Authorize
Obtain an access token with client credentials.
Stores
Stores represent merchant locations. Map each Fire spark store to a location in your POS or RMS so menus and orders stay aligned per site.Menus
Upload and maintain menu structures customers see on each surface. Fire spark synchronizes with your POS and RMS for item changes, pricing, and availability, then applies menu composition — different catalogs by channel, store, fulfillment, or schedule when your strategy requires it.Menu sync guide
Learn how to keep POS, Fire spark, and channels in sync.
Channels
Channels are the surfaces where customers order: owned channels (app, web, kiosk) and aggregators (Uber Eats, Rappi, PedidosYa). Fire spark manages channel configuration and applies intelligence per channel without duplicating integrations.Orders
Orders arrive via webhooks when a customer checks out on any channel. Your integration acknowledges the event, retrieves the full order, and injects it into the POS or RMS.Order injection guide
Learn how to receive webhooks and inject orders into your POS or RMS.
Fulfillment
Fulfillment options (delivery, pickup, dine-in) define how orders are completed per store and channel. Keep fulfillment rules consistent between Fire spark and your operational stack.Uber Eats vs Fire spark
| Uber Eats API | Fire spark Integrations API | |
|---|---|---|
| Channels | Uber Eats only | App, web, kiosk, call center, Uber Eats, Rappi, PedidosYa, and more |
| Menu source | Push to Uber Eats | Sync from POS/RMS; compose per channel, store, fulfillment, or schedule |
| Orders | Uber Eats → your POS | Any channel → Fire spark → your POS/RMS |
| Intelligence | Channel-specific to Uber | Cross-channel rules and enrichment in one layer |
Base URL
Next steps
Authorize
Get an access token
Menu sync
Sync menus with POS and RMS
Order injection
Receive and inject orders
Resource limits
Review rate limits and quotas