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.

Restaurant365 publishes 9 APIs on the APIs.io network, including AP Invoices API, Audit API, Authentication API, and 6 more. Tagged areas include Restaurant, Accounting, Inventory, Operations, and Invoices.

The Restaurant365 catalog on APIs.io includes 2 JSON-LD contexts and 2 Spectral governance rulesets.

Restaurant365’s developer surface includes authentication, documentation, pricing, engineering blog, and 10 more developer resources.

🌐 Visit website 📡 Source on GitHub

54.1/100 developing ▬ flat Agent 31/100 agent aware Full breakdown ↓
scored 2026-07-28 · rubric v0.6

AccessPaidSelf serve

9 APIs 5 Features 4 Use Cases

RestaurantAccountingInventoryOperationsInvoicesReportingOData

Kin Score

Kin Score How this is scored →
scored 2026-07-28 · rubric v0.6

Composite quality — 54.1/100 · developing

Contract Quality 19.3 / 25

Developer Ergonomics 4.3 / 20

Commercial Clarity 10.0 / 20

Operational Transparency 4.8 / 13

Governance 8.3 / 12

Discoverability 7.4 / 10

Agent readiness — 31/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/restaurant365: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 9

Individual APIs this provider publishes, each with its own machine-readable definition.

Rate Limits 1

Documented rate limits and quota policies.

Restaurant365 Rate Limits

3 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Restaurant365 Finops

FINOPS

Features 5

Notable capabilities this provider offers.

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.

JSON Schema 6

Standalone JSON Schema definitions for this provider's data models.

Examples 6

Example request and response payloads for these APIs.

Use Cases 4

What developers build with this provider.

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 3

Pre-built integrations with other platforms and tools.

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.

Resources

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

LlmsText

LlmsText

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

SpectralRules

SpectralRules

Vocabulary

Vocabulary

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 1

Status, limits, changes, and where to get help

RateLimits

RateLimits

Commercial 2

Pricing, plans, and the legal terms of use

Pricing

Pricing

Plans

Plans

Company 3

The organization behind the API

Website

Website

Blog

Blog

LinkedIn

Source (apis.yml)

aid: restaurant365
name: Restaurant365
description: 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.
type: Index
accessModel:
  pricing: paid
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Paid · Self-serve signup
  confidence: high
  source:
  - plans
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/restaurant365.png
tags:
- Restaurant
- Accounting
- Inventory
- Operations
- Invoices
- Reporting
- OData
url: https://raw.githubusercontent.com/api-evangelist/restaurant365/refs/heads/main/apis.yml
created: '2026-06-02'
modified: '2026-06-03'
specificationVersion: '0.19'
apis:
- aid: restaurant365:restaurant365-ap-invoices-api
  name: Restaurant365 AP Invoices API
  description: Create accounts payable invoices in the customer database
  humanURL: https://docs.restaurant365.com/docs/r365-api
  baseURL: https://yourcompany.restaurant365.com
  tags:
  - AP Invoices
  properties:
  - type: OpenAPI
    url: openapi/restaurant365-ap-invoices-api-openapi.yml
  - type: Documentation
    url: https://docs.restaurant365.com/docs/r365-api
  - type: Documentation
    url: https://docs.restaurant365.com/docs/r365-api-connector
  - type: Authentication
    url: https://docs.restaurant365.com/docs/r365-api-connector
  - type: JSONSchema
    url: json-schema/r365-api-ap-invoice-schema.json
  - type: JSONSchema
    url: json-schema/r365-api-journal-entry-schema.json
  - type: JSONStructure
    url: json-structure/r365-api-ap-invoice-structure.json
  - type: JSONStructure
    url: json-structure/r365-api-journal-entry-structure.json
  - type: JSONLD
    url: json-ld/restaurant365-r365-api-context.jsonld
  - type: Examples
    url: examples/r365-api-authenticate-example.json
  - type: Examples
    url: examples/r365-api-create-ap-invoices-example.json
  - type: Examples
    url: examples/r365-api-create-ap-invoices-gl-example.json
  - type: Examples
    url: examples/r365-api-create-journal-entries-example.json
  - type: Documentation
    url: https://docs.restaurant365.com/docs/restaurant365-odata-connector
  - type: Authentication
    url: https://docs.restaurant365.com/docs/restaurant365-odata-connector
  - type: JSONSchema
    url: json-schema/odata-connector-transaction-schema.json
  - type: JSONSchema
    url: json-schema/odata-connector-sales-employee-schema.json
  - type: JSONSchema
    url: json-schema/odata-connector-gl-account-schema.json
  - type: JSONSchema
    url: json-schema/odata-connector-employee-schema.json
  - type: JSONStructure
    url: json-structure/odata-connector-transaction-structure.json
  - type: JSONStructure
    url: json-structure/odata-connector-sales-employee-structure.json
  - type: JSONLD
    url: json-ld/restaurant365-odata-connector-context.jsonld
  - type: Examples
    url: examples/odata-connector-list-transactions-example.json
  - type: Examples
    url: examples/odata-connector-list-sales-employee-example.json
- aid: restaurant365:restaurant365-audit-api
  name: Restaurant365 Audit API
  description: Deleted entity tracking
  humanURL: https://docs.restaurant365.com/docs/r365-api
  baseURL: https://yourcompany.restaurant365.com
  tags:
  - Audit
  properties:
  - type: OpenAPI
    url: openapi/restaurant365-audit-api-openapi.yml
  - type: Documentation
    url: https://docs.restaurant365.com/docs/r365-api
  - type: Documentation
    url: https://docs.restaurant365.com/docs/r365-api-connector
  - type: Authentication
    url: https://docs.restaurant365.com/docs/r365-api-connector
  - type: JSONSchema
    url: json-schema/r365-api-ap-invoice-schema.json
  - type: JSONSchema
    url: json-schema/r365-api-journal-entry-schema.json
  - type: JSONStructure
    url: json-structure/r365-api-ap-invoice-structure.json
  - type: JSONStructure
    url: json-structure/r365-api-journal-entry-structure.json
  - type: JSONLD
    url: json-ld/restaurant365-r365-api-context.jsonld
  - type: Examples
    url: examples/r365-api-authenticate-example.json
  - type: Examples
    url: examples/r365-api-create-ap-invoices-example.json
  - type: Examples
    url: examples/r365-api-create-ap-invoices-gl-example.json
  - type: Examples
    url: examples/r365-api-create-journal-entries-example.json
  - type: Documentation
    url: https://docs.restaurant365.com/docs/restaurant365-odata-connector
  - type: Authentication
    url: https://docs.restaurant365.com/docs/restaurant365-odata-connector
  - type: JSONSchema
    url: json-schema/odata-connector-transaction-schema.json
  - type: JSONSchema
    url: json-schema/odata-connector-sales-employee-schema.json
  - type: JSONSchema
    url: json-schema/odata-connector-gl-account-schema.json
  - type: JSONSchema
    url: json-schema/odata-connector-employee-schema.json
  - type: JSONStructure
    url: json-structure/odata-connector-transaction-structure.json
  - type: JSONStructure
    url: json-structure/odata-connector-sales-employee-structure.json
  - type: JSONLD
    url: json-ld/restaurant365-odata-connector-context.jsonld
  - type: Examples
    url: examples/odata-connector-list-transactions-example.json
  - type: Examples
    url: examples/odata-connector-list-sales-employee-example.json
- aid: restaurant365:restaurant365-authentication-api
  name: Restaurant365 Authentication API
  description: Obtain a bearer token for subsequent requests
  humanURL: https://docs.restaurant365.com/docs/r365-api
  baseURL: https://yourcompany.restaurant365.com
  tags:
  - Authentication
  properties:
  - type: OpenAPI
    url: openapi/restaurant365-authentication-api-openapi.yml
  - type: Documentation
    url: https://docs.restaurant365.com/docs/r365-api
  - type: Documentation
    url: https://docs.restaurant365.com/docs/r365-api-connector
  - type: Authentication
    url: https://docs.restaurant365.com/docs/r365-api-connector
  - type: JSONSchema
    url: json-schema/r365-api-ap-invoice-schema.json
  - type: JSONSchema
    url: json-schema/r365-api-journal-entry-schema.json
  - type: JSONStructure
    url: json-structure/r365-api-ap-invoice-structure.json
  - type: JSONStructure
    url: json-structure/r365-api-journal-entry-structure.json
  - type: JSONLD
    url: json-ld/restaurant365-r365-api-context.jsonld
  - type: Examples
    url: examples/r365-api-authenticate-example.json
  - type: Examples
    url: examples/r365-api-create-ap-invoices-example.json
  - type: Examples
    url: examples/r365-api-create-ap-invoices-gl-example.json
  - type: Examples
    url: examples/r365-api-create-journal-entries-example.json
  - type: Documentation
    url: https://docs.restaurant365.com/docs/restaurant365-odata-connector
  - type: Authentication
    url: https://docs.restaurant365.com/docs/restaurant365-odata-connector
  - type: JSONSchema
    url: json-schema/odata-connector-transaction-schema.json
  - type: JSONSchema
    url: json-schema/odata-connector-sales-employee-schema.json
  - type: JSONSchema
    url: json-schema/odata-connector-gl-account-schema.json
  - type: JSONSchema
    url: json-schema/odata-connector-employee-schema.json
  - type: JSONStructure
    url: json-structure/odata-connector-transaction-structure.json
  - type: JSONStructure
    url: json-structure/odata-connector-sales-employee-structure.json
  - type: JSONLD
    url: json-ld/restaurant365-odata-connector-context.jsonld
  - type: Examples
    url: examples/odata-connector-list-transactions-example.json
  - type: Examples
    url: examples/odata-connector-list-sales-employee-example.json
- aid: restaurant365:restaurant365-general-ledger-api
  name: Restaurant365 General Ledger API
  description: Create AP invoices by GL account and journal entries
  humanURL: https://docs.restaurant365.com/docs/r365-api
  baseURL: https://yourcompany.restaurant365.com
  tags:
  - General Ledger
  properties:
  - type: OpenAPI
    url: openapi/restaurant365-general-ledger-api-openapi.yml
  - type: Documentation
    url: https://docs.restaurant365.com/docs/r365-api
  - type: Documentation
    url: https://docs.restaurant365.com/docs/r365-api-connector
  - type: Authentication
    url: https://docs.restaurant365.com/docs/r365-api-connector
  - type: JSONSchema
    url: json-schema/r365-api-ap-invoice-schema.json
  - type: JSONSchema
    url: json-schema/r365-api-journal-entry-schema.json
  - type: JSONStructure
    url: json-structure/r365-api-ap-invoice-structure.json
  - type: JSONStructure
    url: json-structure/r365-api-journal-entry-structure.json
  - type: JSONLD
    url: json-ld/restaurant365-r365-api-context.jsonld
  - type: Examples
    url: examples/r365-api-authenticate-example.json
  - type: Examples
    url: examples/r365-api-create-ap-invoices-example.json
  - type: Examples
    url: examples/r365-api-create-ap-invoices-gl-example.json
  - type: Examples
    url: examples/r365-api-create-journal-entries-example.json
  - type: Documentation
    url: https://docs.restaurant365.com/docs/restaurant365-odata-connector
  - type: Authentication
    url: https://docs.restaurant365.com/docs/restaurant365-odata-connector
  - type: JSONSchema
    url: json-schema/odata-connector-transaction-schema.json
  - type: JSONSchema
    url: json-schema/odata-connector-sales-employee-schema.json
  - type: JSONSchema
    url: json-schema/odata-connector-gl-account-schema.json
  - type: JSONSchema
    url: json-schema/odata-connector-employee-schema.json
  - type: JSONStructure
    url: json-structure/odata-connector-transaction-structure.json
  - type: JSONStructure
    url: json-structure/odata-connector-sales-employee-structure.json
  - type: JSONLD
    url: json-ld/restaurant365-odata-connector-context.jsonld
  - type: Examples
    url: examples/odata-connector-list-transactions-example.json
  - type: Examples
    url: examples/odata-connector-list-sales-employee-example.json
- aid: restaurant365:restaurant365-labor-api
  name: Restaurant365 Labor API
  description: Employees, labor detail, payroll, and POS employees
  humanURL: https://docs.restaurant365.com/docs/r365-api
  baseURL: https://yourcompany.restaurant365.com
  tags:
  - Labor
  properties:
  - type: OpenAPI
    url: openapi/restaurant365-labor-api-openapi.yml
  - type: Documentation
    url: https://docs.restaurant365.com/docs/r365-api
  - type: Documentation
    url: https://docs.restaurant365.com/docs/r365-api-connector
  - type: Authentication
    url: https://docs.restaurant365.com/docs/r365-api-connector
  - type: JSONSchema
    url: json-schema/r365-api-ap-invoice-schema.json
  - type: JSONSchema
    url: json-schema/r365-api-journal-entry-schema.json
  - type: JSONStructure
    url: json-structure/r365-api-ap-invoice-structure.json
  - type: JSONStructure
    url: json-structure/r365-api-journal-entry-structure.json
  - type: JSONLD
    url: json-ld/restaurant365-r365-api-context.jsonld
  - type: Examples
    url: examples/r365-api-authenticate-example.json
  - type: Examples
    url: examples/r365-api-create-ap-invoices-example.json
  - type: Examples
    url: examples/r365-api-create-ap-invoices-gl-example.json
  - type: Examples
    url: examples/r365-api-create-journal-entries-example.json
  - type: Documentation
    url: https://docs.restaurant365.com/docs/restaurant365-odata-connector
  - type: Authentication
    url: https://docs.restaurant365.com/docs/restaurant365-odata-connector
  - type: JSONSchema
    url: json-schema/odata-connector-transaction-schema.json
  - type: JSONSchema
    url: json-schema/odata-connector-sales-employee-schema.json
  - type: JSONSchema
    url: json-schema/odata-connector-gl-account-schema.json
  - type: JSONSchema
    url: json-schema/odata-connector-employee-schema.json
  - type: JSONStructure
    url: json-structure/odata-connector-transaction-structure.json
  - type: JSONStructure
    url: json-structure/odata-connector-sales-employee-structure.json
  - type: JSONLD
    url: json-ld/restaurant365-odata-connector-context.jsonld
  - type: Examples
    url: examples/odata-connector-list-transactions-example.json
  - type: Examples
    url: examples/odata-connector-list-sales-employee-example.json
- aid: restaurant365:restaurant365-metadata-api
  name: Restaurant365 Metadata API
  description: OData service metadata
  humanURL: https://docs.restaurant365.com/docs/r365-api
  baseURL: https://yourcompany.restaurant365.com
  tags:
  - Metadata
  properties:
  - type: OpenAPI
    url: openapi/restaurant365-metadata-api-openapi.yml
  - type: Documentation
    url: https://docs.restaurant365.com/docs/r365-api
  - type: Documentation
    url: https://docs.restaurant365.com/docs/r365-api-connector
  - type: Authentication
    url: https://docs.restaurant365.com/docs/r365-api-connector
  - type: JSONSchema
    url: json-schema/r365-api-ap-invoice-schema.json
  - type: JSONSchema
    url: json-schema/r365-api-journal-entry-schema.json
  - type: JSONStructure
    url: json-structure/r365-api-ap-invoice-structure.json
  - type: JSONStructure
    url: json-structure/r365-api-journal-entry-structure.json
  - type: JSONLD
    url: json-ld/restaurant365-r365-api-context.jsonld
  - type: Examples
    url: examples/r365-api-authenticate-example.json
  - type: Examples
    url: examples/r365-api-create-ap-invoices-example.json
  - type: Examples
    url: examples/r365-api-create-ap-invoices-gl-example.json
  - type: Examples
    url: examples/r365-api-create-journal-entries-example.json
  - type: Documentation
    url: https://docs.restaurant365.com/docs/restaurant365-odata-connector
  - type: Authentication
    url: https://docs.restaurant365.com/docs/restaurant365-odata-connector
  - type: JSONSchema
    url: json-schema/odata-connector-transaction-schema.json
  - type: JSONSchema
    url: json-schema/odata-connector-sales-employee-schema.json
  - type: JSONSchema
    url: json-schema/odata-connector-gl-account-schema.json
  - type: JSONSchema
    url: json-schema/odata-connector-employee-schema.json
  - type: JSONStructure
    url: json-structure/odata-connector-transaction-structure.json
  - type: JSONStructure
    url: json-structure/odata-connector-sales-employee-structure.json
  - type: JSONLD
    url: json-ld/restaurant365-odata-connector-context.jsonld
  - type: Examples
    url: examples/odata-connector-list-transactions-example.json
  - type: Examples
    url: examples/odata-connector-list-sales-employee-example.json
- aid: restaurant365:restaurant365-reference-data-api
  name: Restaurant365 Reference Data API
  description: Companies, locations, GL accounts, items, and job titles
  humanURL: https://docs.restaurant365.com/docs/r365-api
  baseURL: https://yourcompany.restaurant365.com
  tags:
  - Reference Data
  properties:
  - type: OpenAPI
    url: openapi/restaurant365-reference-data-api-openapi.yml
  - type: Documentation
    url: https://docs.restaurant365.com/docs/r365-api
  - type: Documentation
    url: https://docs.restaurant365.com/docs/r365-api-connector
  - type: Authentication
    url: https://docs.restaurant365.com/docs/r365-api-connector
  - type: JSONSchema
    url: json-schema/r365-api-ap-invoice-schema.json
  - type: JSONSchema
    url: json-schema/r365-api-journal-entry-schema.json
  - type: JSONStructure
    url: json-structure/r365-api-ap-invoice-structure.json
  - type: JSONStructure
    url: json-structure/r365-api-journal-entry-structure.json
  - type: JSONLD
    url: json-ld/restaurant365-r365-api-context.jsonld
  - type: Examples
    url: examples/r365-api-authenticate-example.json
  - type: Examples
    url: examples/r365-api-create-ap-invoices-example.json
  - type: Examples
    url: examples/r365-api-create-ap-invoices-gl-example.json
  - type: Examples
    url: examples/r365-api-create-journal-entries-example.json
  - type: Documentation
    url: https://docs.restaurant365.com/docs/restaurant365-odata-connector
  - type: Authentication
    url: https://docs.restaurant365.com/docs/restaurant365-odata-connector
  - type: JSONSchema
    url: json-schema/odata-connector-transaction-schema.json
  - type: JSONSchema
    url: json-schema/odata-connector-sales-employee-schema.json
  - type: JSONSchema
    url: json-schema/odata-connector-gl-account-schema.json
  - type: JSONSchema
    url: json-schema/odata-connector-employee-schema.json
  - type: JSONStructure
    url: json-structure/odata-connector-transaction-structure.json
  - type: JSONStructure
    url: json-structure/odata-connector-sales-employee-structure.json
  - type: JSONLD
    url: json-ld/restaurant365-odata-connector-context.jsonld
  - type: Examples
    url: examples/odata-connector-list-transactions-example.json
  - type: Examples
    url: examples/odata-connector-list-sales-employee-example.json
- aid: restaurant365:restaurant365-sales-api
  name: Restaurant365 Sales API
  description: Sales ticket headers, detail, and payments
  humanURL: https://docs.restaurant365.com/docs/r365-api
  baseURL: https://yourcompany.restaurant365.com
  tags:
  - Sales
  properties:
  - type: OpenAPI
    url: openapi/restaurant365-sales-api-openapi.yml
  - type: Documentation
    url: https://docs.restaurant365.com/docs/r365-api
  - type: Documentation
    url: https://docs.restaurant365.com/docs/r365-api-connector
  - type: Authentication
    url: https://docs.restaurant365.com/docs/r365-api-connector
  - type: JSONSchema
    url: json-schema/r365-api-ap-invoice-schema.json
  - type: JSONSchema
    url: json-schema/r365-api-journal-entry-schema.json
  - type: JSONStructure
    url: json-structure/r365-api-ap-invoice-structure.json
  - type: JSONStructure
    url: json-structure/r365-api-journal-entry-structure.json
  - type: JSONLD
    url: json-ld/restaurant365-r365-api-context.jsonld
  - type: Examples
    url: examples/r365-api-authenticate-example.json
  - type: Examples
    url: examples/r365-api-create-ap-invoices-example.json
  - type: Examples
    url: examples/r365-api-create-ap-invoices-gl-example.json
  - type: Examples
    url: examples/r365-api-create-journal-entries-example.json
  - type: Documentation
    url: https://docs.restaurant365.com/docs/restaurant365-odata-connector
  - type: Authentication
    url: https://docs.restaurant365.com/docs/restaurant365-odata-connector
  - type: JSONSchema
    url: json-schema/odata-connector-transaction-schema.json
  - type: JSONSchema
    url: json-schema/odata-connector-sales-employee-schema.json
  - type: JSONSchema
    url: json-schema/odata-connector-gl-account-schema.json
  - type: JSONSchema
    url: json-schema/odata-connector-employee-schema.json
  - type: JSONStructure
    url: json-structure/odata-connector-transaction-structure.json
  - type: JSONStructure
    url: json-structure/odata-connector-sales-employee-structure.json
  - type: JSONLD
    url: json-ld/restaurant365-odata-connector-context.jsonld
  - type: Examples
    url: examples/odata-connector-list-transactions-example.json
  - type: Examples
    url: examples/odata-connector-list-sales-employee-example.json
- aid: restaurant365:restaurant365-transactions-api
  name: Restaurant365 Transactions API
  description: Financial transactions and transaction detail
  humanURL: https://docs.restaurant365.com/docs/r365-api
  baseURL: https://yourcompany.restaurant365.com
  tags:
  - Transactions
  properties:
  - type: OpenAPI
    url: openapi/restaurant365-transactions-api-openapi.yml
  - type: Documentation
    url: https://docs.restaurant365.com/docs/r365-api
  - type: Documentation
    url: https://docs.restaurant365.com/docs/r365-api-connector
  - type: Authentication
    url: https://docs.restaurant365.com/docs/r365-api-connector
  - type: JSONSchema
    url: json-schema/r365-api-ap-invoice-schema.json
  - type: JSONSchema
    url: json-schema/r365-api-journal-entry-schema.json
  - type: JSONStructure
    url: json-structure/r365-api-ap-invoice-structure.json
  - type: JSONStructure
    url: json-structure/r365-api-journal-entry-structure.json
  - type: JSONLD
    url: json-ld/restaurant365-r365-api-context.jsonld
  - type: Examples
    url: examples/r365-api-authenticate-example.json
  - type: Examples
    url: examples/r365-api-create-ap-invoices-example.json
  - type: Examples
    url: examples/r365-api-create-ap-invoices-gl-example.json
  - type: Examples
    url: examples/r365-api-create-journal-entries-example.json
  - type: Documentation
    url: https://docs.restaurant365.com/docs/restaurant365-odata-connector
  - type: Authentication
    url: https://docs.restaurant365.com/docs/restaurant365-odata-connector
  - type: JSONSchema
    url: json-schema/odata-connector-transaction-schema.json
  - type: JSONSchema
    url: json-schema/odata-connector-sales-employee-schema.json
  - type: JSONSchema
    url: json-schema/odata-connector-gl-account-schema.json
  - type: JSONSchema
    url: json-schema/odata-connector-employee-schema.json
  - type: JSONStructure
    url: json-structure/odata-connector-transaction-structure.json
  - type: JSONStructure
    url: json-structure/odata-connector-sales-employee-structure.json
  - type: JSONLD
    url: json-ld/restaurant365-odata-connector-context.jsonld
  - type: Examples
    url: examples/odata-connector-list-transactions-example.json
  - type: Examples
    url: examples/odata-connector-list-sales-employee-example.json
common:
- type: AgenticAccess
  url: agentic-access/restaurant365-agentic-access.yml
- type: DomainSecurity
  url: security/restaurant365-domain-security.yml
- type: Authentication
  url: authentication/restaurant365-authentication.yml
- type: Website
  url: https://www.restaurant365.com
- type: Documentation
  url: https://docs.restaurant365.com/docs/r365-api
- type: Pricing
  url: https://www.restaurant365.com/pricing/
- type: Plans
  url: plans/restaurant365-plans-pricing.yml
- type: RateLimits
  url: rate-limits/restaurant365-rate-limits.yml
- type: SpectralRules
  url: rules/restaurant365-rules.yml
- type: Vocabulary
  url: vocabulary/restaurant365-vocabulary.yml
- type: Blog
  url: https://www.restaurant365.com/blog/
- type: GitHubOrganization
  url: https://github.com/restaurant365
- type: LinkedIn
  url: https://www.linkedin.com/company/restaurant365-cloud-erp-for-restaurants
- type: LlmsText
  url: https://docs.restaurant365.com/llms.txt
- type: Features
  data:
  - name: AP Invoice Automation
    description: Push vendor AP invoices into the customer database with item or GL-account detail.
  - name: General Ledger Posting
    description: Create balanced journal entries and GL-coded AP invoices via the R365 API.
  - name: OData Reporting Views
    description: Read-only OData views for transactions, sales, labor, and reference data.
  - name: Incremental Sync
    description: rowVersion property supports pulling only records changed since the last sync.
  - name: Audit Tracking
    description: EntityDeleted view exposes records removed from the system for audit reconciliation.
- type: UseCases
  data:
  - name: Vendor Invoice Integration
    description: Suppliers push electronic invoices directly into a restaurant's R365 ledger.
  - name: BI And Reporting
    description: Pull sales, labor, and financial data into external BI and reporting tools via OData.
  - name: Payroll Export
    description: Extract labor detail and payroll summary data for downstream payroll processing.
  - name: Data Warehouse Replication
    description: Replicate transactions and sales into a warehouse using date-range chunked pulls.
- type: Integrations
  data:
  - name: Excel
    description: Connect to OData views through the Excel OData feed and R365 Excel plug-in.
  - name: Business Intelligence Tools
    description: Any OData-compatible BI/reporting tool can consume the OData connector views.
  - name: POS Systems
    description: POSEmployee and sales views map R365 records to point-of-sale data.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com