Slice API
Slice runs Slice Register, the point-of-sale and shop-management system that independent pizzerias use as their back-office system of record—the register where the shop rings up phone, online, and walk-in orders, manages one synced menu, processes payments, and watches sales and daily totals in real time. This unofficial API surfaces that back-office operating data—the pizzeria's own orders, menu/catalog, sales, payments, customers, and register reporting—not the consumer-facing Slice marketplace. Programmatically pull orders, menu items, sales and daily totals, payments and payouts, and customer records, and push menu and price updates back into the shop's register.
What is Slice?
Slice builds technology for independent pizzerias, including Slice Register—a point-of-sale and shop-management system built specifically for pizza shops and now used across Slice's network of 18,000+ independent pizzerias. This page is about that back-office side: the register and owner tools a pizzeria runs its own operations on, not the consumer marketplace where diners browse and order. On Slice Register the shop rings up phone, online, and walk-in orders through one unified system, manages a single menu that syncs everywhere, takes credit, cash, and mobile payments, and tracks sales, orders, and daily totals in real time from the Owner's App.
The back-office shop-operations data the register holds includes:
- Orders — phone, online, and walk-in tickets for to-go, dine-in, and delivery, unified in one system
- Menu / catalog — items, modifiers, sizes, and prices in one menu that syncs across every channel
- Sales and daily totals — consolidated offline and online reports, real-time sales, and end-of-day totals
- Payments and payouts — credit card, cash, and mobile payments with daily payouts to the shop
- Customers — the shop's own customer records and ordering habits used for promos and reorder reminders
- Deliveries — driver assignments and live tracking for the shop's delivery orders
The Slice Integration Challenge
A pizzeria runs its whole day on Slice Register, but getting that back-office operating data out programmatically is hard:
- No self-serve public API: Slice Register is a closed, vertically integrated POS—there is no published developer portal where a shop can mint its own keys, so access is OAuth-gated and non-self-serve
- Tablet/mPOS-first surface: the Owner's App and register live on tablets and mobile, so much of the sales, order, and daily-total data is only exposed through authenticated app flows, not a documented HTTP API
- Marketplace vs. back-office split: Slice's public surfaces are built for diners ordering pizza; the shop's own register, sales, and customer data sit behind owner authentication and are not part of any consumer ordering interface
- One-menu sync semantics: a single menu fans out to the website, Google, Facebook, Instagram, and Slice's own apps, so menu and price writes have to respect the shop's canonical catalog rather than edit a channel copy
- Mixed online and offline reporting: consolidated reports blend in-store, phone, and online orders, so totals must be reconciled across payment types and channels to match what the owner sees
- Payments and payout timing: card, cash, and mobile tenders settle into daily payouts, so pulling clean sales-versus-payout data requires handling settlement timing and tender mix
How Supergood Creates Slice APIs
Supergood reverse-engineers the authenticated Slice Register and Owner's App flows to deliver a resilient API layer over your pizzeria's own back-office data—orders, menu, sales, payments, and customers—without waiting on a public developer program. You connect once with the shop's owner credentials and read or write the same operating data the register runs on.
- Authenticates with the shop's owner login and handles OAuth-gated, non-self-serve access in a managed session
- Maintains session continuity for the tablet/mPOS surface with automated refresh and change detection
- Normalizes orders, menu items, sales/daily totals, payments, and customers into consistent JSON so you integrate once
- Respects the one-menu sync model so menu and price writes land on the shop's canonical catalog and propagate to every channel
Use Slice with AI agents: Slice MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your Slice Register setup, owner access, and which back-office entities (orders, menu, sales, payments, customers) you need.
- Supergood Generates and Validates Your API
We deliver a production-ready Slice adapter tailored to your shop's register data and authentication model.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adaptation as Slice Register evolves.
API Endpoints
Authentication
/authenticateAuthenticate with the pizzeria's Slice Register owner credentials and obtain a session token for back-office calls.
Orders
/ordersList the shop's own orders—phone, online, and walk-in—across to-go, dine-in, and delivery, with status, channel, and date filters.
Menu
/menuRetrieve the shop's canonical menu: items, modifiers, sizes, and prices from the single menu that syncs across every channel.
Menu
/menuUpdate menu items, availability, and prices on the shop's canonical catalog so changes propagate to all ordering channels.
Sales
/salesPull consolidated offline and online sales reports, real-time sales, and end-of-day daily totals for the register.
Payments
/paymentsRetrieve card, cash, and mobile payment transactions and daily payouts settled to the shop.
Customers
/customersList the shop's own customer records and ordering habits used for segmentation, promos, and reorder reminders.
Use Cases
Sync register orders into the back office
- Pull phone, online, and walk-in orders from Slice Register into a single warehouse - Reconcile to-go, dine-in, and delivery tickets across channels in real time - Stream new-order events to kitchen-display, accounting, and analytics tools
Manage the shop's menu and pricing programmatically
- Read the shop's canonical menu items, modifiers, sizes, and prices - Push price and availability changes to the one menu that syncs everywhere - Keep an external catalog or PIM aligned with the register's source of truth
Reconcile sales, payments, and daily totals
- Sync consolidated offline and online sales reports into the general ledger - Match card, cash, and mobile tenders against daily payouts - Surface end-of-day totals and item-level sales to BI dashboards
Activate the shop's own customer data
- Export the pizzeria's customer records and ordering habits for segmentation - Trigger reorder reminders and targeted promos from external marketing tools - Keep CRM and loyalty systems in sync with register customer activity
Technical Specifications
Authentication
Slice Register owner credentials handled in a managed session over an OAuth-gated, non-self-serve surface
Connectivity
Authenticated Slice Register and Owner's App flows reverse-engineered into a stable API layer
Response format
Normalized JSON across orders, menu, sales, payments, and customer objects
Rate limits
Adaptive throttling tuned to the shop's tablet/mPOS surface to avoid register-side limits
Session management
Automatic session refresh, re-auth handling, and credential rotation for the owner login
Data freshness
Near real-time pulls for orders, sales, and daily totals with optional scheduled batch syncs
Security
Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging
Webhooks
Event-style callbacks for new orders, menu changes, payment settlement, and daily-total close
Latency
Sub-second reads on cached menu and sales data; multi-second writes when posting menu and price updates
Throughput
Workers sized to a busy pizzeria's order, sales, and payment volume across channels
Reliability
Retry, backoff, and idempotency keys for menu writes and payment/payout reconciliation
Adaptation
Continuous monitoring of Slice Register releases and Owner's App changes with automatic adjustment
Frequently asked questions
No. This API is strictly about the back-office side—Slice Register, the POS and shop-management system the pizzeria runs its own operations on. It surfaces the shop's own orders, menu, sales, payments, and customers (the system of record), not the consumer-facing marketplace where diners browse and order pizza.
No. Slice Register is a closed, vertically integrated POS with no published developer portal where a shop mints its own keys. Supergood provides API access over the authenticated owner surface, so you connect with the shop's own credentials rather than waiting on a public program.
You can read the shop's orders (phone, online, walk-in), the canonical menu/catalog, consolidated sales and daily totals, payments and payouts, and customer records. You can write menu and price updates back to the shop's one synced menu.
Slice Register keeps a single canonical menu that fans out to the website, Google, Facebook, Instagram, and Slice's own apps. Writes land on that canonical catalog and propagate to every channel, rather than editing a per-channel copy.
Yes. Slice Register's consolidated reports blend in-store, phone, and online orders. Supergood normalizes sales, tender mix, and daily totals across channels and payment types so the API totals match what the owner sees in the register.