How to use Resos REST API

We provide API-credentials in order to broaden the spectrum of what can be done with Resos’ restaurant management system. When you use the Resos REST API to streamline your business, you can allow your existing systems to communicate directly with your booking system. The API is an add-on that can give you access to all relevant information from Resos. This includes guest-data, booking-data, or any other data that you might be interested in integrating into another system.

What Resos connects to already, and what you build yourself

Resos has no pre-built POS, EPOS, or till-system integration today. If you want your POS or EPOS to exchange bookings or guest data with Resos, that connection is built on this REST API, either by you or by your POS provider or an integration partner.

Stripe is also the only payment processor Resos supports. Online payment, prepayments, deposits and no-show fees all run through Stripe, and the API does not let you route guest payments through a different processor. When a booking needs prepayment or a no-show fee, a booking created through this API gets a payment deadline and is automatically deleted if the guest never pays. A booking created manually in the dashboard is never deleted this way, even when it needs payment.

The ready-made integrations that do exist are listed under Menu → Settings & add-ons → Integrations. Which ones appear there depends on the country your restaurant is registered in, so it is worth checking that page before you plan any custom work. If you want to connect Resos to another tool without writing code, look at Zapier in that same section first.

Generate keys directly in the system

In order to use our REST API, you need a private API key that will identify and authorize the request. In order to manage your API keys and generate new ones, you go to Menu → Settings & add-ons → Integrations → API. The next step is to click on Activate add-on and then on Generate key, and done!

The API keys give you access to all your data and your customers’ contact information, so be sure to keep it safe and only use it on the server-side code, and not show it to the user. Find out more about the guidelines by reading our API documentation.

The API is a paid add-on, available on any of our paid plans (Basic, Plus, Unlimited). It requires both a paid plan and the API add-on activated.

Once you have a key, see Resos REST API capabilities and limits for what the API can do, how to poll it for changes, its rate limits and page sizes, and how to try it before you commit.

Please let us know at hi@resos.com if you have questions or if something you need is missing. We are extending the API as needed and per your request.