R365 provides read-only access to your data through the OData Connector (also called the Read API or API Read Access). This is the supported method for pulling report data, sales details, and other records out of R365 into external tools such as Power BI, Excel, Postman, or custom applications. A separate Write API is also available for pushing data into R365 (for example, posting AP invoices), and requires different credentials.
Most OData access issues are caused by incorrect user configuration rather than a broken connection. This article covers how to enable and troubleshoot OData access.
Symptoms
Attempting to authenticate at odata.restaurant365.net returns an error or a blank SVG response instead of data
A user has OData credentials but queries are returning no data or access denied errors
An external tool like Power BI or Postman cannot authenticate against the OData endpoint
A query against the SalesDetail endpoint times out or crashes when requesting more than one day of data
Steps to Resolve
Step 1: Verify the OData User Is Configured Correctly
OData access is controlled through the R365 user account used to authenticate. The account must meet two requirements:
Open the Admin app.
Under Users & Security, click Users.
Find and open the user account used for OData authentication.
Confirm that the All Locations toggle is enabled. OData will not return data if the user is limited to specific locations — all locations must be selected.
Confirm that the user has the appropriate report or data access permissions assigned.
The user does not need Full Access specifically, but must otherwise have the Accounting Clerk role assigned.
Step 2: Authenticate Correctly Against the OData Endpoint
The base URL for the OData Connector is:
https://odata.restaurant365.net/api/v2/Authenticate using Basic Authentication with the R365 username and password of the dedicated OData user. If the response is an SVG file instead of data, the authentication failed — confirm the username and password are correct and that the account has All Locations enabled.
Step 3: Use Filters to Avoid Query Timeouts
Some endpoints — particularly SalesDetail — have data volume limits. Requesting more than one day of data at a time can cause queries to time out or crash.
For large data pulls, apply date filters to limit each request to one day at a time, then loop across date ranges in your tool. This is expected behavior and is not a connection issue.
Step 4: Understand What the Write API Covers
The Write API (REST API) is a separate access path used to push data into R365. It covers a limited set of operations:
AP Invoices
AP Invoices by GL Account
Journal Entries
Write API credentials are separate from OData credentials and must be requested through R365 Support. Write API access cannot be used to read data out of R365.
Note that R365 does not provide direct database access. OData is the only supported read layer.
For full API documentation, see R365 API Connector.