Revolut Locations API
The Locations API is designed to help merchants manage multiple points of sale, including both **online storefronts** and **physical stores**. Registering locations lets you differentiate and group your orders from different stores. You can also introduce custom business logic for each location, such as different inventory management, pricing, or shipping rules.To start using locations, follow the relevant use case for your business:### Online locations 1. Register an online location using the [Create a location](https://developer.revolut.com/docs/api/merchant#create-location)endpoint, setting the `type` to `online`. 1. Configure your custom processes on your backend for each registered location (e.g., groupingorders, custom pricing, etc.). 1. Send the `location_id` parameter in the request body during [order creation](https://developer.revolut.com/docs/api/merchant#create-order)to assign the order to a specific location.### Physical locations 1. Register a physical location using the [Create a location](https://developer.revolut.com/docs/api/merchant#create-location)endpoint, setting the `type` to `physical`. 1. In case of Revolut POS, our system handles order creation including `location_id` to associatethe order with your location.## Fast checkout for multiple storefrontsLocations are particularly useful for tailoring the user experience on each of your online storefronts, especially when using features like [**Fast checkout**](https://developer.revolut.com/docs/guides/merchant/optimise-checkout/fast-checkout).For example, if you operate two online stores with different shipping rules, you can register two separate `online` locations. By then using the `location_id` to [register a distinct address validation endpoint](https://developer.revolut.com/docs/api/merchant#register-address-validation-endpoint) for each one, your backend can apply the correct shipping logic and pricing for the specific storefront a customer is buying from.
Revolut Locations API is one of 46 APIs that Revolut publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Locations. The published artifact set on APIs.io includes an OpenAPI specification.
This API exposes 5 operations across 2 paths, and defines 19 schemas. It is described by OpenAPI 3.0.1, at version 1.0.
Requests are made against 2 base URLs: https://b2b.revolut.com/api/1.0, https://sandbox-b2b.revolut.com/api/1.0.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Revolut Locations API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (AccessToken).
AccessToken— Each Business API request must contain an authorization header in the following format to make a call: Bearer . The access token will be obtained the first tim…
Paths & Operations 5
Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.
The Locations API is designed to help merchants manage multiple points of sale, including both online storefronts and physical stores. Registering locations lets you differentiate…
Schemas 19
The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are Opening-Hours (7 properties), Address-v3 (6 properties), Location-Online (4 properties), Location-Physical (4 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Revolut 12
Other APIs Revolut publishes across the network.