R365 exposes three integration surfaces for building against the R365 platform. This introduction covers each: the R365 Public API (our modern integration surface), Secure Data Share (direct data access via Snowflake), and the R365 Classic API (our current production API, maintained for existing integrations).
R365 Public API
Early Adopter (Closed)
The R365 Public API is currently available to a closed Early Adopter group. Restaurant365 is incorporating participant feedback before it opens access more broadly. Learn more about requesting R365 Public API access.
The R365 Public API is our next-generation, recommended integration surface. It supports both reads and writes, covers all major product areas (with nearly 4× more endpoints than the legacy API Connector), and is built on a standardized URL convention. All endpoints follow the /public/v1/{domain}/{resource} pattern with consistent naming and structure across every domain.
Documentation includes:
All endpoints following the standardized
/public/v1/{domain}/{resource}conventionFull request and response schemas with property-level descriptions
Parameter documentation with valid values and defaults
Error response documentation
Use this reference if you are building a new R365 integration or migrating an existing one.
Secure Data Share
Secure Data Share provides direct, read-only access to R365 data via Snowflake. Rather than pulling data through API requests, you can query R365 data directly from your own Snowflake environment.
Documentation includes:
Setup instructions for connecting to the R365 Snowflake data share
Data dictionary reference for all available views, organized by domain
Use this reference if you need bulk or analytical access to R365 data without making individual API requests.
R365 Classic API
The R365 Classic API is a REST API. It is read-only. Existing integrations built on this surface continue to work as the company moves to the R365 Public API. The R365 Public API is currently an Early Adopter program, and acceptance is closed to new participants. The Classic API remains the production option until Public API access reopens more broadly.
Documentation includes:
All available endpoints, exactly as they exist in production
Full request and response schemas with property-level descriptions
Parameter documentation with valid values and defaults
Error response documentation
FAQ
Which R365 integration option should I use?
Use the R365 Public API to build a new integration or migrate an existing one. It supports both reads and writes. Use Secure Data Share if you need bulk or analytical read-only access to R365 data through Snowflake without making API requests. The R365 Classic API remains the production option for existing integrations.
How do I get access to the R365 Public API?
The R365 Public API is currently available only to a closed Early Adopter group, and acceptance is closed to new participants while R365 incorporates feedback. See requesting R365 Public API access for the current process.
Will my existing Classic API integration stop working when the Public API opens more broadly?
No. Existing integrations built on the R365 Classic API continue to work as R365 moves to the Public API. The Classic API remains the production option until Public API access reopens more broadly.
Do I need to make API requests to use Secure Data Share?
No. Secure Data Share gives you direct, read-only access to R365 data through Snowflake, so you query the data from your own Snowflake environment instead of pulling it through API requests. The documentation includes setup instructions and a data dictionary for all available views, organized by domain.
What URL format do Public API endpoints use?
All Public API endpoints follow the standardized /public/v1/{domain}/{resource} pattern, with consistent naming and structure across every domain.