How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Restaurant365 Sales API

Sales ticket headers, detail, and payments

Restaurant365 Sales API is one of 9 APIs that Restaurant365 publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 10 JSON Schema definitions.

Tagged areas include Sales. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, a JSON-LD context, and 10 JSON Schemas.

This API exposes 3 operations across 3 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version v2.

Requests are made against a single base URL, https://odata.restaurant365.net/api/v2/views.

3 operations 3 paths 3 schemas 3 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v2
Base URL
https://yourcompany.restaurant365.com
Authentication
HTTP Basic
Contact
License
Proprietary
Resource Areas
1

Authentication & Security 1

Restaurant365 Sales API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth).

  • basicAuth — Domain\Username with R365 password

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 3 GET. Each is listed below with its method, path, parameters, and response codes.

Sales 3

Sales ticket headers, detail, and payments

GET
/SalesEmployee
List Sales Employee Tickets
listSalesEmployee 4 params → 200
GET
/SalesDetail
List Sales Detail
listSalesDetail 4 params → 200
GET
/SalesPayment
List Sales Payments
listSalesPayment 4 params → 200

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are SalesEmployee (25 properties), SalesPayment (22 properties), SalesDetail (21 properties). Each schema is shown below with its type and property counts.

SalesPayment
object
22 properties
SalesEmployee
object
25 properties
SalesDetail
object
21 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

restaurant365-sales-api-openapi.yml Raw ↑

Other APIs Restaurant365 publishes across the network.

Restaurant365 AP Invoices API
Restaurant365 Audit API
Restaurant365 Authentication API
Restaurant365 General Ledger API
Restaurant365 Labor API
Restaurant365 Metadata API
Restaurant365 Reference Data API
Restaurant365 Transactions API
Where this information came from

This is an independent, third-party profile of Restaurant365 Sales API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.