← Back to all docs

MarketMan API

MarketMan is a cloud-based restaurant inventory, purchasing, and cost-control platform that centralizes inventory tracking, vendor ordering, recipe costing, and accounts payable for over 15,000 restaurants. An API lets you programmatically pull inventory items, vendors, purchase orders, invoices, and recipe costs—and push orders, counts, and price updates back into MarketMan.

By Alex KlarfeldMay 30, 2026
MarketMan API

What is MarketMan?

MarketMan is a cloud-based platform that centralizes inventory control, purchasing, expense tracking, and recipe costing to help restaurants reduce food costs and improve profitability. Restaurants—from single-location operators to multi-unit chains and ghost kitchens—use MarketMan to track live inventory, automate vendor ordering, manage invoices and accounts payable, and surface real-time COGS, food cost, and menu profitability analytics across their operations.

Core product areas include:

  • Inventory Management (live stock tracking, counts, transfers, and waste monitoring)
  • Purchasing & Ordering (AI-powered order suggestions and vendor management)
  • Recipe Costing (ingredient-level cost breakdowns and menu profitability)
  • Accounts Payable (invoice management and accounting software integrations)
  • Mobile App (order placement and inventory counts from phones and tablets)
  • Reporting (real-time COGS, food cost, and menu profitability analytics)

Common data entities:

  • Inventory Items, Stock Levels, Counts, Transfers
  • Vendors, Purchase Orders, Order Suggestions
  • Invoices, Price Tracking, Credits
  • Recipes, Menu Items, Ingredient Costs
  • Waste Logs, COGS, Food Cost Reports
  • Locations, Buyers, Accounting Mappings

The MarketMan Integration Challenge

Restaurants run daily purchasing and cost-control workflows on MarketMan, but turning its portal- and mobile-driven workflows into reliable API-driven automation is non-trivial:

  • Partner API gating: MarketMan's API is positioned for third-party and partner integrations, often requiring approval and credential provisioning before access
  • Mobile-first data: Many counts, orders, and waste logs are entered through the mobile app, so the freshest data lives behind authenticated app sessions
  • Multi-location spread: Inventory, vendors, and pricing differ per location and buyer group, so generic integrations break across a multi-unit account
  • Vendor and price variability: Catalogs, units of measure, and price tracking change frequently, requiring careful normalization across distributors
  • Accounting sync nuance: Invoice and AP exports must map to each restaurant's GL accounts and accounting integration (Xero, QuickBooks, and others)
  • Recipe-cost dependencies: Menu profitability depends on ingredient costs that shift with every invoice, so recipe data is only meaningful when kept current

How Supergood Creates MarketMan APIs

Supergood reverse-engineers MarketMan's authenticated browser and mobile flows alongside its REST API surface to deliver a resilient, normalized API layer for your MarketMan account—across every location and buyer group.

  • Handles API token, username/password, and MFA challenges securely in a managed session
  • Maintains session continuity with automated refresh and change detection
  • Normalizes responses across inventory, purchasing, invoices, and recipe costs so you integrate once and rely on consistent objects
  • Aligns with per-location catalogs, units of measure, and accounting mappings to keep data accurate across multi-unit accounts

Use MarketMan with AI agents: MarketMan MCP Server →

Getting Started

  • Schedule Integration Assessment

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

  • Supergood Generates and Validates Your API

We deliver a production-ready MarketMan adapter tailored to your account configuration and catalogs.

  • Deploy with Monitoring

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

marketman

API Endpoints

Authentication

POST/authenticate

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

Inventory

GET/inventory_items

List inventory items with current stock levels, units of measure, and cost across one or more locations.

Purchasing

GET/vendors

Retrieve vendors, catalogs, and contact details available to a location and buyer group.

Purchasing

POST/create_purchase_order

Create and submit a purchase order to a vendor with line items, quantities, and delivery details.

Accounts Payable

GET/invoices

Pull vendor invoices with line items, price tracking, credits, and accounting mappings.

Recipes

GET/recipes

List recipes and menu items with ingredient-level cost breakdowns and current food cost.

Use Cases

Sync inventory and stock levels across locations

- Pull live inventory items, stock levels, and units of measure into a central warehouse - Stream counts, transfers, and waste logs to downstream analytics and forecasting tools - Reconcile on-hand quantities across multiple locations for unified reporting

Automate vendor ordering and purchase orders

- Generate and submit purchase orders to vendors based on par levels and order suggestions - Pull vendor catalogs and pricing to keep ordering systems current - Route order approvals and delivery confirmations without portal clicks

Reconcile invoices and accounts payable

- Sync vendor invoices, credits, and price changes into AP and general ledger systems - Map invoice line items to each restaurant's accounting integration and GL accounts - Flag price variances and short-shipments to cost-control workflows

Keep recipe costing and menu profitability current

- Pull recipes and ingredient costs that update with every invoice - Surface real-time COGS, food cost, and menu profitability to BI dashboards - Trigger menu re-pricing alerts when ingredient costs cross thresholds

Technical Specifications

Authentication

API token or username/password and MFA handled in a managed session

Connectivity

Authenticated browser and mobile flows plus MarketMan's REST API where exposed

Response format

Normalized JSON across inventory, purchasing, invoice, and recipe objects

Rate limits

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

Session management

Automatic session refresh, MFA replay handling, and credential rotation

Data freshness

Near real-time pulls for inventory, orders, and invoices 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, purchase order status, count submissions, and price changes

Latency

Sub-second reads on cached entities; multi-second writes when submitting purchase orders and counts

Throughput

Horizontally scaled workers sized to multi-location, multi-vendor volume

Reliability

Retry, backoff, and idempotency keys for purchase orders, invoices, and inventory adjustments

Adaptation

Continuous monitoring of MarketMan releases, catalog changes, and account-specific configuration drift

Frequently asked questions

Yes. Supergood normalizes inventory, vendors, pricing, and invoices across every location and buyer group in your MarketMan account, so multi-unit operators integrate once and rely on consistent objects.

Yes. Counts, orders, and waste logs entered on phones and tablets are captured through authenticated sessions and surfaced in the same normalized API, so mobile-entered data is available alongside portal data.

Supergood works with your existing MarketMan account and authenticated sessions. Where MarketMan's partner API is available we use it; otherwise we operate against the same authenticated surfaces your team already uses.

Each account is profiled against its configured vendors, catalogs, and units of measure. Supergood preserves account-specific pricing, conversions, and accounting mappings rather than forcing a generic schema.

Yes. Recipes, ingredient costs, COGS, and food-cost reports are exposed through the same normalized API surface, so menu profitability data sits alongside inventory and invoice entities.

Ready to get a real API?