Restaurant365 website screenshot

Restaurant365

Restaurant365 is a cloud-based restaurant accounting, inventory, and operations platform serving thousands of restaurant locations across the United States. Its developer offering centers on the R365 API, which lets approved third-party vendors and partners connect to a customer's R365 database to retrieve data and create or push records such as AP invoices and general ledger entries. A complementary OData connector exposes sales, transaction, location, GL account, employee, and labor data for use in external reporting and business-intelligence tools. API access is provisioned per customer through R365 Support, with bearer-token authentication on the R365 API and Domain\Username basic authentication on the OData connector.

2 APIs 5 Features
RestaurantAccountingInventoryOperationsInvoicesReportingOData

APIs

R365 API

The R365 API lets approved third-party services and vendors connect to a Restaurant365 customer database to retrieve data and create or push records, including AP invoices, GL-c...

Restaurant365 OData Connector

The Restaurant365 OData connector exposes R365 data to OData-compatible reporting and BI tools through read-only views for companies, locations, GL accounts, items, job titles, ...

Collections

R365 API

OPEN

Pricing Plans

Rate Limits

Restaurant365 Rate Limits

3 limits

RATE LIMITS

FinOps

Features

AP Invoice Automation

Push vendor AP invoices into the customer database with item or GL-account detail.

General Ledger Posting

Create balanced journal entries and GL-coded AP invoices via the R365 API.

OData Reporting Views

Read-only OData views for transactions, sales, labor, and reference data.

Incremental Sync

rowVersion property supports pulling only records changed since the last sync.

Audit Tracking

EntityDeleted view exposes records removed from the system for audit reconciliation.

Use Cases

Vendor Invoice Integration

Suppliers push electronic invoices directly into a restaurant's R365 ledger.

BI And Reporting

Pull sales, labor, and financial data into external BI and reporting tools via OData.

Payroll Export

Extract labor detail and payroll summary data for downstream payroll processing.

Data Warehouse Replication

Replicate transactions and sales into a warehouse using date-range chunked pulls.

Integrations

Excel

Connect to OData views through the Excel OData feed and R365 Excel plug-in.

Business Intelligence Tools

Any OData-compatible BI/reporting tool can consume the OData connector views.

POS Systems

POSEmployee and sales views map R365 records to point-of-sale data.

Semantic Vocabularies

Restaurant365 Odata Connector Context

11 classes · 23 properties

JSON-LD

Restaurant365 R365 Api Context

3 classes · 24 properties

JSON-LD

API Governance Rules

Restaurant365 API Rules

25 rules · 6 errors 15 warnings 4 info

SPECTRAL

JSON Structure

Odata Connector Sales Employee Structure

25 properties

JSON STRUCTURE

Odata Connector Transaction Structure

15 properties

JSON STRUCTURE

R365 Api Ap Invoice Structure

16 properties

JSON STRUCTURE

R365 Api Journal Entry Structure

13 properties

JSON STRUCTURE

Example Payloads

Resources

🔗
Website
Website
🔗
Documentation
Documentation
💰
Pricing
Pricing
🔗
Plans
Plans
🔗
RateLimits
RateLimits
🔗
SpectralRules
SpectralRules
🔗
Vocabulary
Vocabulary
📰
Blog
Blog
👥
GitHubOrganization
GitHubOrganization
🔗
LinkedIn
LinkedIn
🔗
LlmsText
LlmsText

Sources

Raw ↑
opencollection: 1.0.0
info:
  name: R365 API
  version: v1
items:
- info:
    name: Authentication
    type: folder
  items:
  - info:
      name: Authenticate And Obtain Bearer Token
      type: http
    http:
      method: POST
      url: https://{customerHost}.restaurant365.com/APIv1/Authenticate
      body:
        type: json
        data: '{}'
    docs: Exchange an R365 username and password for a bearer token that must be sent in the Authorization header on all subsequent
      API requests.
- info:
    name: AP Invoices
    type: folder
  items:
  - info:
      name: Create AP Invoices
      type: http
    http:
      method: POST
      url: https://{customerHost}.restaurant365.com/APIv1/APInvoices
      body:
        type: json
        data: '{}'
      auth:
        type: bearer
        token: '{{bearerToken}}'
    docs: Create one or more accounts payable invoices in the customer database using vendor and product (item) level detail.
      Vendor name and retailer store number must match values configured in the customer's R365 database.
- info:
    name: General Ledger
    type: folder
  items:
  - info:
      name: Create AP Invoices By GL Account
      type: http
    http:
      method: POST
      url: https://{customerHost}.restaurant365.com/APIv1/APInvoicesGL
      body:
        type: json
        data: '{}'
      auth:
        type: bearer
        token: '{{bearerToken}}'
    docs: Create one or more accounts payable invoices or AP credit memos using GL account level detail rather than item detail.
      Use this when invoices should be coded directly to general ledger accounts.
  - info:
      name: Create Journal Entries
      type: http
    http:
      method: POST
      url: https://{customerHost}.restaurant365.com/APIv1/JournalEntries
      body:
        type: json
        data: '{}'
      auth:
        type: bearer
        token: '{{bearerToken}}'
    docs: Create one or more general ledger journal entries. Debits and credits must balance across the lines of each journal
      entry. Payroll journal entries require the payroll-specific fields.
bundled: true