← Back to all docs

MarginEdge API

MarginEdge is a restaurant management platform that automates back-office work—invoice processing, food cost and inventory tracking, recipe and menu analysis, ordering, and bill pay—and syncs purchasing and sales data into accounting systems. MarginEdge offers a read-only public API, but an unofficial Supergood API lets you programmatically pull invoices, products, vendors, orders, sales, and menu/recipe data with consistent, normalized objects across every location.

By Alex KlarfeldMay 30, 2026
MarginEdge API

What is MarginEdge?

MarginEdge is a restaurant management platform that eliminates manual back-office work by automating invoice processing, food cost and inventory tracking, recipe and menu analysis, ordering, and bill pay. It captures invoices line by line, pulls sales data from the POS, produces daily P&Ls and food-cost reporting, and automatically sends purchasing and sales data into the restaurant's accounting system.

Core product areas include:

  • Invoice Processing (automated line-item capture, categorization, and price tracking)
  • Cost Management (daily P&Ls and real-time food cost tracking)
  • Inventory & Food Usage (on-hand counts, waste measurement, and usage analysis)
  • Menu Analysis (performance metrics from ingredient pricing and sales mix)
  • Ordering, Commissary, and Bill Pay (purchase orders, multi-location transfers, and vendor payments)
  • POS and Accounting Integrations (Toast, Square, SpotOn, 7shifts; QuickBooks, Sage Intacct, NetSuite, Xero, Restaurant365)

Common data entities:

  • Invoices, Line Items, Categories, Price History
  • Products, Units, GL Codes, Vendors
  • Orders, Purchase Orders, Transfers, Commissary
  • Recipes, Menu Items, Sales Mix
  • Inventory Counts, On-Hand, Waste, Usage
  • Restaurants/Locations, Daily P&Ls

The MarginEdge Integration Challenge

Restaurant groups run daily purchasing, costing, and accounting workflows on MarginEdge, but turning that back-office data into broader automation is non-trivial:

  • Read-only, one-way public API: The official MarginEdge public API only pushes data out of MarginEdge—it can't read from external systems and only exposes data you've already uploaded or created
  • Restaurant-scoped authorization: Only parties a restaurant explicitly authorizes can retrieve that restaurant's data, so multi-location access requires per-restaurant credentialing
  • Write-back gaps: Creating orders, adjusting products, or pushing inventory counts isn't covered by the public API and lives behind the web app
  • Coverage tied to upstream data: Invoice, product, and sales availability depends on what's been captured, OCR'd, and categorized—integrations must handle partial and in-progress records
  • Cross-location normalization: Product names, units, GL codes, and vendors vary across restaurants in a group, complicating consolidated reporting
  • Accounting and POS coupling: Data flows through Toast/Square/SpotOn and QuickBooks/Sage/NetSuite connectors, each with its own timing and field semantics

How Supergood Creates MarginEdge APIs

Supergood reverse-engineers authenticated MarginEdge web flows alongside the official public API to deliver a resilient, full-coverage API layer for your MarginEdge account—across every restaurant and location in the group.

  • Handles username/password and MFA securely in a managed session
  • Maintains session continuity with automatic refresh and change detection
  • Normalizes invoices, products, vendors, orders, and sales across locations so you integrate once and rely on consistent objects
  • Adds write-back and read paths the public API doesn't expose, scoped to your authorized restaurants

Use MarginEdge with AI agents: MarginEdge MCP Server →

Getting Started

  • Schedule Integration Assessment

Book a 30-minute session to confirm your locations, modules, and authentication model.

  • Supergood Generates and Validates Your API

We deliver a production-ready MarginEdge adapter tailored to your account and authorized restaurants.

  • Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as MarginEdge evolves.

marginedge

API Endpoints

Authentication

POST/authenticate

Authenticate to a MarginEdge account using credentials or API key and obtain a session token for downstream calls.

Invoices

GET/invoices

List captured invoices with line items, categories, vendors, and price history, filtered by restaurant and date range.

Products

GET/products

Retrieve the product catalog with units, GL codes, and current pricing across one or more locations.

Vendors

GET/vendors

Pull vendor records and supplier details linked to invoices, orders, and bill payments.

Ordering

POST/create_order

Create a purchase order or commissary transfer for a restaurant, including products, quantities, and vendor.

Sales

GET/sales

Retrieve POS sales and menu sales-mix data used for food cost and menu performance analysis.

Use Cases

Sync invoices and purchasing into your data warehouse

- Pull captured invoices, line items, and price history across every location - Stream vendor and product data to BI and procurement tools - Reconcile purchasing spend against budgets and daily P&Ls

Automate accounting and GL exports

- Map invoices and bills to GL codes for QuickBooks, Sage Intacct, or NetSuite - Push categorized purchasing and sales data without manual entry - Surface uncategorized or in-progress invoices for review workflows

Drive menu and food cost analytics

- Combine recipe costs, ingredient pricing, and sales mix for margin analysis - Track food cost percentage and waste across locations - Flag menu items whose costs have drifted from target margins

Automate ordering and inventory operations

- Generate purchase orders and commissary transfers from par levels - Sync on-hand counts and usage back into operational systems - Normalize products, units, and vendors across restaurants in a group

Technical Specifications

Authentication

Username/password and MFA, or MarginEdge public API key, handled in a managed session

Connectivity

Authenticated web flows plus the official MarginEdge public API where exposed

Response format

Normalized JSON across Invoices, Products, Vendors, Orders, and Sales objects

Rate limits

Adaptive throttling tuned to your account to avoid MarginEdge-side limits

Session management

Automatic session refresh, MFA replay handling, and credential rotation

Data freshness

Near real-time pulls for invoices and sales 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 invoices, price changes, order status, and inventory counts

Latency

Sub-second reads on cached entities; multi-second writes when posting orders and transfers

Throughput

Horizontally scaled workers sized to multi-location restaurant-group volume

Reliability

Retry, backoff, and idempotency keys for orders, transfers, and accounting exports

Adaptation

Continuous monitoring of MarginEdge releases, POS/accounting connector changes, and per-restaurant configuration drift

Frequently asked questions

The official public API is read-only and pushes data one way out of MarginEdge, exposing only data you've already uploaded or created. Supergood adds read coverage and write-back paths the public API doesn't offer, with normalized objects across every location.

Yes. Supergood normalizes products, units, GL codes, and vendors across every restaurant in your group so you can integrate once and report on consolidated, consistent data.

Yes. Beyond read access, Supergood supports write operations such as creating purchase orders and commissary transfers, scoped to the restaurants you've authorized.

Yes. Supergood works alongside MarginEdge's POS connectors (Toast, Square, SpotOn, 7shifts) and accounting integrations (QuickBooks, Sage Intacct, NetSuite, Xero, Restaurant365), exposing the resulting invoices, sales, and GL data through one normalized surface.

MarginEdge scopes data access per restaurant. Supergood credentials each authorized restaurant individually and maintains those authenticated sessions so multi-location access stays compliant.

Ready to get a real API?