Restaurant365 API

Does Restaurant365 have a public API?

Restaurant365 offers an API and an OData connector, but neither is self-serve. R365 Support enables API access for a named vendor and issues the credentials, so an operator's own engineering team cannot generate a key and start pulling data the same afternoon. Integuru generates a production-ready HTTP API for Restaurant365 from your existing login, with 21 verified actions across reporting, accounts payable, menu structure and the org hierarchy.

The gap this fills is the reporting layer: the numbers a controller actually closes the period on live in the P&L reports, the operations overview and the receiving reports, and those views, not the raw ledger tables behind them, are what the actions below return.

| | Restaurant365 API | Integuru for Restaurant365 | |---|---|---| | Access | Enabled by R365 Support per vendor, with R365-issued credentials | Your own Restaurant365 login | | Covers | Retrieving, creating and pushing data, plus an OData connector for BI | P&L, operations overview, receiving and AP report views | | First call | After the vendor approval cycle | Within about 20 minutes of connecting the login |

What you can do with the Restaurant365 API

A multi-unit finance team closes the week by pulling four things: the P&L, the operations overview, what was received, and what is sitting in AP. The actions map onto that routine.

Close the period

• get_pnl_summary returns a P&L for a start_date to end_date range, scoped by location_ids, with include_unapproved for a pre-approval view. Both dates default to yesterday, which suits a nightly pull.
• get_profit_and_loss runs the native fiscal-period report. Pass as_of as M,YYYY or a plain date, pick the calendar basis (fiscal or operational), and set detail_level, report_type and rounding. list_profit_and_loss_options returns the valid as_of_periods and report_types for the account.
• get_profit_and_loss_custom_date compares any range against a prior window using versus_start_date and versus_end_date, defaulting to the same range a year earlier.
• get_operations_overview returns the dashboard operations report for an as-of date, optionally scoped to location_id or location_ids.

Reconcile purchasing and AP

• get_receiving_by_purchased_item returns purchases for a date range by category, with include_items for item-level rows and include_transactions for one row per invoice line including invoice number, unit cost and vendor.
• list_ap_transactions and list_journal_entries page through the AP ledger and journal with OData filter and sort expressions, 250 records per page by default.
• list_vendors, list_payment_terms and list_items return the master data those transactions reference.

Map the menu and the org chart

• list_menu_items, list_catering_menus, list_sales_categories, list_revenue_centers and list_sections describe how sales are categorised.
• list_locations, list_stores, list_sites, list_companies and list_legal_entities return the hierarchy, and list_locations is where the locationId GUIDs used by every scoped report come from.

Who uses this

Restaurant groups consolidating P&L across 20 or more units use the report actions to feed a warehouse or BI tool nightly without a finance analyst exporting from the UI. Food-cost and back-office platforms use get_receiving_by_purchased_item with include_transactions to reconcile their own invoice captures against what Restaurant365 recorded. AP automation tools use list_ap_transactions and list_vendors to detect duplicate or unpaid invoices across locations. Companion pages in this cluster cover COGS-Well, xtraCHEF, MarginEdge and Restaurant System Pro, and the restaurants industry page shows how these fit together.

Setup notes

Integuru authenticates against identity.restaurant365.com with your Restaurant365 user. Use a login whose role can view the reports you plan to pull, because the API returns exactly what that user can see in the UI.

Start every integration with list_locations. Reports accept either location_id (one GUID) or location_ids (a list); when both are present, location_ids wins. For get_profit_and_loss, call list_profit_and_loss_options once and cache the report_types and as_of_periods values rather than guessing them. Keep include_transactions pulls to short date ranges so responses stay under the truncation threshold.

Get started

Install the CLI and connect your Restaurant365 login:

npm install -g integuru

Prefer a browser? Sign in at app.integuru.com, add Restaurant365, and the same 21 actions are ready to call. For an action that is not listed above, such as a report this page does not cover, the Managed Service scopes, builds and maintains it for you.