Getting Started

API Reference

We are pleased to inform you about an update in our API services involving the implementation of new domains for certain specific endpoints. From now on, some of our API services will be exclusively available through these new domains, while others will continue to function normally with the current domains.

It's important to note that the previous domains will remain operational and will continue to be the access route for the vast majority of our endpoints. However, certain specific services and functionalities will require the use of the new domains for access.

Rappi recommends that you familiarize yourself with the terminology used during the process, authentication methods, and understand the requirements for a successful integration.

Country Domains

When making API requests, the system requires you to specify the domain of your country.

The following table contains all the country domains used for making API Requests:

CountryDomain URL
Costa Rica

For testing purposes, use the Developer domain:

Rules for using the new Domains

To utilize these domains, it's crucial to adhere to the following rules:

Common base path

All API calls start with the common base path /restaurants/{Module Name}. For example:


Authentication token


Read information about audiences to have a broader context of what will be mentioned Read Here


The audience's {Country domain} marker refers to the following domains Read Here

With the new domains, even though previously different audiences could be used for authentication, now only a single audience in the generated token is allowed. This audience must exclusively be {Country domain}/api/v2/restaurants-integrations-public-api.