get_order_detail requires an order_id. Where does that come from?

The order_id is an integer identifier obtained from the results of the get_orders action. The typical workflow is to call get_orders first to retrieve the list of orders and their IDs, then pass a specific order_id to get_order_detail to retrieve the full detail record for that order.

Back to Integrations

Restaurants & Food Service

MarginEdge

Integuru generates a production-ready HTTP API for MarginEdge, the restaurant food cost and invoice management platform. The integration covers 2 actions for order listing and order detail retrieval, both carrying richer docs, enabling restaurant tech teams to access invoice and purchasing data programmatically.

2actions

https://auth.marginedge.com/u/login/identifier

Last reviewed: July 2026

Overview

Integuru's MarginEdge integration provides production-ready HTTP API access to MarginEdge, the restaurant food cost and invoice management platform at auth.marginedge.com, covering 2 actions: get_orders and get_order_detail. Both actions carry richer documentation. Integuru connects via direct HTTP requests rather than browser automation, so calls complete in under 3 seconds with a 99.9%+ success rate.

No public developer API. MarginEdge does not expose an official developer API. Restaurant tech teams and food cost automation platforms that need purchasing order data programmatically have had no standard integration path.

Restaurant tech developers use get_orders to retrieve the list of orders from a MarginEdge account, then get_order_detail to retrieve the full record for a specific order. This two-step pattern supports invoice reconciliation, food cost reporting, and purchasing data pipelines. See the Aloha integration or Resy integration for other restaurant-tech integrations, or browse the full integrations catalogue.

Use Cases

Integuru's MarginEdge integration covers the order data workflows that restaurant tech teams need to automate.

Order listing: Call get_orders with no parameters to retrieve the list of orders from the authenticated MarginEdge account. The results include order_id values used as input to get_order_detail.
Order detail retrieval: Call get_order_detail with the required integer order_id (obtained from get_orders) to retrieve the full detail record for a specific order.

Setup Notes

Integuru's MarginEdge integration authenticates against https://auth.marginedge.com/u/login/identifier. Configure credentials once during Integuru setup; Integuru handles session management automatically.

get_orders requires no parameters. get_order_detail requires an integer order_id, which must be obtained from a prior get_orders call. Richer documentation for both actions is available via the Integuru dashboard after setup.

Available Actions

Click an action to expand its parameters

Overview

Use Cases

Setup Notes

Available Actions

Frequently Asked Questions