How to connect to Restaurant365

Connecting Restaurant365 is a short form: there is no authorization pop-up and no app to register. You enter three values — your subdomain, an API username, and its password — and Apideck verifies them for you.

The one thing to sort out first is the credentials themselves, which Restaurant365 issues rather than you generating them yourself.

Prerequisites

Before you can create the connection, you need:

An active Restaurant365 account with Public API access enabled for your database.
An API username and password issued by Restaurant365 for your tenant. These are not self-serve: Restaurant365 Support issues them through their API Credentials Request process. Either you or the team that built your integration can raise that request, and Restaurant365 Support confirms it with both sides before issuing the credentials. Restaurant365 requires a technical contact from the team that built your integration to be named on the request, so let them know when you raise it — that contact is a required part of the request. See the Restaurant365 Public API documentation for how the request is made, and ask your R365 admin, your Customer Success Manager (CSM), or Restaurant365 Support at support@restaurant365.net for an expected timeline.

This step happens outside Vault, between you, Restaurant365, and the team that built your integration. Restaurant365 sends the credentials to whichever side raised the request — so get the username and password from there once they arrive. After that, everything below takes a couple of minutes.

1. Find your subdomain

https://mycompany.restaurant365.com

The subdomain is the middle segment — mycompany in the example above.

Enter only that segment. The Vault form already supplies the https:// prefix and the .restaurant365.com suffix around it, so do not paste the full URL.

2. Have your API credentials ready

You need the two values Restaurant365 Support issued for your tenant:

Username — the API username issued for your Restaurant365 database.
Password — the API password issued alongside that username.

These are credentials created specifically for API access. Copy them exactly as they were provided, with no leading or trailing spaces.

3. Enter the credentials in Vault

Open the Restaurant365 connection in Vault and complete the three fields:

Field	Value
Subdomain	Your subdomain segment from step 1 (e.g. `mycompany`)
Username	The API username from step 2
Password	The API password from step 2

Click Save. Apideck verifies the credentials by making a test call to Restaurant365 and shows a success message when the connection is working.

Your Restaurant365 account is now connected.

Notes

Production only. Restaurant365 has no sandbox or trial environment, so this connection always points at your own live Restaurant365 database. Data you read is live data, and any records you create are created for real. Bear that in mind when testing your integration.
No periodic re-authorization. Apideck exchanges your username and password for a session token on each request, so there is no token for you to refresh or re-approve on a schedule.
If the API password is rotated or revoked by your R365 admin, update it in this connection. Calls will fail until the stored password matches the one Restaurant365 expects.

Troubleshooting

I don't have an API username and password

Restaurant365 API credentials cannot be created from within the Restaurant365 application, and Apideck cannot issue them. Ask your Restaurant365 CSM — or Restaurant365 Support at support@restaurant365.net if you don't have a CSM — to raise an API Credentials Request for your database, and name a technical contact from the team that built your integration on it. See the Restaurant365 Public API documentation.

The connection fails to save, or authentication is rejected

Check the Subdomain field holds only the middle segment (mycompany), not https://mycompany.restaurant365.com and not mycompany.restaurant365.com.
Re-copy the Username and Password, watching for a trailing space picked up from an email or ticket.
Ask your CSM or Restaurant365 Support to confirm the credentials are still active and that Public API access is enabled for your database. Credentials issued for a different R365 database will not work against yours.

The connection saves, but the data belongs to a different company

You are almost certainly pointed at the wrong tenant. Confirm the subdomain against the URL you see when logged in to Restaurant365, and confirm with your admin which database the credentials were issued for.

Anything else

Reach out to Apideck Support.