R365 offers three Integration surfaces for third party services, such as vendors, to connect and retrieve or push data to R365 databases. Each section below describes what each surface does and when to use it.
Full reference documentation and more information is available in the R365 Developer Hub.
R365 Public API
The R365 Public API is a standardized REST surface. All endpoints follow the `/public/v1/{domain}/{resource}` pattern with consistent naming and structure across every domain.
Use this if you're building a new R365 integration or migrating an existing one to the standardized API surface.
Request Public API Access
Contact your CSM to complete the API Credentials Request form (internal-access only) for access to the R365 Public API.
If you have R365 Public API access and need access to API documentation, visit the Developer Hub.
Secure Data Share
Secure Data Share gives you direct, read-only access to R365 data via Snowflake. Instead of making API requests, you query R365 data directly from a connected Snowflake environment.
Use this if you need bulk or analytical access to R365 data without making individual API requests.
R365 API Connector
Legacy — Planned for Deprecation
The R365 API Connector is our legacy REST API. It is read-only and will be deprecated in the future as we fully transition to the R365 Public API. If you have an existing integration built on this surface, it will continue to work — but we recommend migrating to the Public API, which offers broader coverage, read/write support, and is the integration surface R365 will continue to build on.
The R365 API Connector is the current production REST API. Use this reference to maintain or extend integrations that already run against it.
Use this if you're maintaining or extending an existing R365 integration.
FAQ
What's the difference between the R365 API Connector and the R365 Public API?
The R365 API Connector is a legacy integration used to push data into R365 (such as AP invoices from a vendor system).
The R365 Public API, documented in the R365 Developer Hub, is the recommended path for new integrations — it covers 68 endpoints across Accounting, Inventory, Sales, Labor, and more, and supports both reading and writing data.
If you're building a new integration, use the Public API. Contact your CSM to request credentials and access scopes.
Who initiates the API access request — the customer or the vendor?
Either party can initiate.
If the customer submits the request to R365 Support first, R365 confirms permission and provides credentials directly to the vendor. If the vendor initiates, R365 confirms with the customer before providing credentials. Both paths end at R365 Support — include a member of the vendor's technical team on any request.
Where do I find my unique customer URL for API requests?
Your unique customer URL is the subdomain that appears before .restaurant365.com when you're logged into R365. For example, if your URL is thedean.restaurant365.com, your customer URL is thedean. Use this value wherever [YOUR-UNIQUE-CUSTOMER-URL] appears in the API documentation.