# Restaurant365 — Accounting API: overview > Canonical URL: https://developers.apideck.com/apis/accounting/restaurant365/overview Restaurant365 is a cloud ERP built specifically for restaurants, covering accounting, AP automation, inventory, workforce and payroll. - Status: beta - Authentication: apiKey - **difficulty:** involved - **sandbox note:** There is no sandbox or trial environment; testing runs against a mutual customer's live instance. - **beta:** true - **partnership url:** https://www.restaurant365.com/partner-ecosystem/#become-partner - **sandbox available:** false - **environment notes:** - **environment:** Production (only) - **description:** Testing and production share one set of credentials: every connection points at the consumer's own live R365 database at their tenant subdomain, and there is no sandbox/production selector. Test against a mutual customer's instance and treat all data as production. - **account type required:** An active Restaurant365 account with Public API access enabled by R365. - **partnership required:** true - **difficulty reason:** Partnership-gated Public API access + custom session-based auth (no OAuth) - **partnership note:** Each connection uses per-tenant credentials from the customer's R365 CSM — the path that works today. Apideck's partner application is pending since 2026-08-03. - **rate limits:** No numeric rate limit published for R365's Public API. - **consumer access level:** An R365 administrator with R365-issued API credentials — there is no self-serve authorization step. - **important to know:** R365's Public API has no accounts-receivable or customer-invoicing surface, so customers, invoices, invoice items and tax rates cannot be served by this connector at all — that is a product-surface gap in R365, not a mapping gap Apideck can close. The API does expose more than accounts payable, though: general ledger accounts, journal entries, vendors, purchase orders, legal entities, locations and bank accounts are all separate, non-AP endpoints this connector already reads. A multi-consumer rollout is paced one R365 account at a time, so plan a phased onboarding rather than switching every consumer on at once. Bills and credit notes are create-and-read only through this connector: approving, rejecting and deleting them are not exposed at all, so an AP approval workflow cannot be driven through Unify today. - **authentication note:** Session-based: a username and password are exchanged for a session token; not OAuth. - **webhooks:** Virtual webhooks — R365 publishes no native webhooks or event subscriptions; Apideck polls 10 of the 13 supported resources for changes. - **apideck credentials note:** R365 has no OAuth app model, so there is no shared client id/secret. - **supported resource categories:** - **name:** Accounts Payable - **resources:** bills credit-notes bill-payments payments - **resources:** ledger-accounts journal-entries general-ledger-transactions - **name:** General Ledger - **name:** Vendors & Purchasing - **resources:** suppliers purchase-orders - **name:** Company Structure - **resources:** subsidiaries company-info locations - **name:** Banking - **resources:** bank-accounts - **partnership portal name:** Restaurant365 Developer Hub - **responsibility matrix:** - **apideck:** ✓ - **area:** Restaurant365 Technology Partnership - **customer:** ✓ Can initiate - **consumer:** ✓ Via their R365 CSM or Support - **area:** Obtain R365 API Credentials - **apideck:** Docs provided - **area:** Create Connection in Vault - **consumer:** ✓ Enters subdomain, username, password - **apideck:** Secure connection form - **area:** Session Token Handling - **apideck:** ✓ Automatic - **area:** Build via Unified API - **customer:** ✓ - **apideck:** Maintains connector - **area:** Monitor Connections - **customer:** ✓ Via Apideck Dashboard - **consumer:** Can delete the connection - **apideck:** Logs & alerts - **apideck credentials available:** false ## Supported resources [Accounting data model](/guides/accounting-data-model.md) - **id:** bills - **downstream name:** Ap Invoices - **status:** live - **name:** Bills - **downstream id:** ap-invoices - **custom field support:** true - **status:** live - **downstream id:** ap-credit-memos - **id:** credit-notes - **downstream name:** Ap Credit Memos - **name:** Credit Notes - **custom field support:** true - **custom field support:** true - **id:** bill-payments - **status:** live - **name:** Bill Payments - **downstream id:** ap-payments - **downstream name:** Ap Payments - **id:** payments - **downstream id:** ap-payments - **name:** Payments - **downstream name:** Ap Payments - **status:** live - **custom field support:** true - **downstream name:** Journal Entries - **custom field support:** false - **status:** live - **name:** Journal Entries - **id:** journal-entries - **downstream id:** journal-entries - **id:** ledger-accounts - **custom field support:** false - **status:** live - **name:** Ledger Accounts - **downstream id:** gl-accounts - **downstream name:** Gl Accounts - **id:** suppliers - **downstream id:** vendors - **custom field support:** true - **name:** Suppliers - **status:** live - **downstream name:** Vendors - **id:** purchase-orders - **name:** Purchase Orders - **downstream id:** purchase-orders - **downstream name:** Purchase Orders - **custom field support:** true - **status:** live - **status:** live - **downstream name:** Legal Entities - **custom field support:** false - **id:** subsidiaries - **name:** Subsidiaries - **downstream id:** legal-entities - **status:** live - **custom field support:** false - **name:** Company Info - **id:** company-info - **downstream id:** legal-entity - **downstream name:** Legal Entity - **downstream name:** Locations - **custom field support:** false - **id:** locations - **downstream id:** locations - **status:** live - **name:** Locations - **downstream id:** bank-accounts - **status:** beta - **name:** Bank Accounts - **id:** bank-accounts - **downstream name:** Bank Accounts - **custom field support:** false - **name:** General Ledger Transactions - **custom field support:** false - **downstream name:** Transactions - **status:** beta - **id:** general-ledger-transactions - **downstream id:** transactions An omitted operation list does not establish operation support. Verify the selected operation in the coverage matrix. [API reference](https://developers.apideck.com/apis/accounting/reference.md) · [Coverage matrix](https://developers.apideck.com/apis/accounting/coverage)