Restaurant365

Service ID: restaurant365

Restaurant365 is a cloud ERP built specifically for restaurants, covering accounting, AP automation, inventory, workforce and payroll.

Beta — this connector is in beta. Functionality and resource coverage may change.

At a Glance

Difficulty
⚠️INVOLVEDPartnership-gated Public API access + custom session-based auth (no OAuth)
Authentication
API KeySession-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.
Partnership Required
Yes(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.)
Partnership Application
Restaurant365 Developer Hub↗
Apideck Credentials
Not available(R365 has no OAuth app model, so there is no shared client id/secret.)
Sandbox Availability
Not available(There is no sandbox or trial environment; testing runs against a mutual customer's live instance.)
Account Type Required
An active Restaurant365 account with Public API access enabled by R365.
Consumer Access Level
An R365 administrator with R365-issued API credentials — there is no self-serve authorization step.
Rate Limits
No numeric rate limit published for R365's Public API.

Responsibility matrix

TaskYou (Customer)Your ConsumerApideck
Restaurant365 Technology Partnership——✓
Obtain R365 API Credentials✓ Can initiate✓ Via their R365 CSM or SupportDocs provided
Create Connection in Vault—✓ Enters subdomain, username, passwordSecure connection form
Session Token Handling——✓ Automatic
Build via Unified API✓—Maintains connector
Monitor Connections✓ Via Apideck DashboardCan delete the connectionLogs & alerts

Environments

Production (only)
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.

🚨Important to Know About Restaurant365

  • 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.
⚠️

14 gotchas across 8 resources

Connector-specific behaviors and limitations to be aware of

📦

13 supported resources

View field mappings, supported operations, and schema details