Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

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.

5 operations 2 paths 19 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0
Base URL
https://b2b.revolut.com/api/1.0
Authentication
HTTP Bearer
Resource Areas
1

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.

Locations 5

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…

POST
/api/locations
Create a location
createLocation 1 param body → 201400401404
GET
/api/locations
Retrieve location list
retrieveLocationList 2 params → 200401
GET
/api/locations/{location_id}
Retrieve a location
retrieveLocation 2 params → 200401404
PATCH
/api/locations/{location_id}
Update a location
updateLocation 2 params body → 200400401404
DELETE
/api/locations/{location_id}
Delete a location
deleteLocation 2 params → 204401404

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.

Location-Update-Physical
object
Location object represents merchant locations depending on type.
Location-Creation
object
Request body for creating a location. The structure of the details object depends on the type of the location.
Error
object
2 properties 2 required
Location-Creation-Online
object
3 properties 3 required
Location
object
Location object represents merchant locations depending on type.
Location-Physical-Details
object
Additional details of the location.
3 properties 3 required
Opening-Hours
object
An object containing the opening hours for each day of the week. A day can have multiple intervals (e.g., closing for a lunch break).
7 properties
Location-Physical
object
4 properties 4 required
Geo-Location
object
Coordinates of the location.
2 properties 2 required
Location-Update-Online
object
2 properties
Day-Opening-Hours
array
A list of one or more time intervals for a single day. A day can have multiple intervals (e.g., closing for a lunch break).
Location-Creation-Physical
object
3 properties 3 required
Location-Type
string
Type of the location. | Value | Description | | ----- | ----------- | | online | Represents an online store. | | physical | Represents a physical point of sale…
Address-v3
object
Details of a physical address.
6 properties 4 required
Location-Name
string
Name of the location. :::warning The name parameter's value must be unique across all locations. :::
Location-Update
object
Request body for updating a location. The structure of the details object depends on the type of the location.
Location-Online
object
4 properties 4 required
Location-Id
string
Unique ID representing the location where merchants sells products. :::info For more information, see: [Locations](https://developer.revolut.com/docs/api/merch…
Location-Online-Details
object
Additional details of the location.
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

revolut-locations-api-openapi.yml Raw ↑

Other APIs Revolut publishes across the network.

Revolut Accounting API
Revolut Accounting categories API
Revolut Accounts API
Revolut Apple Pay merchant registration API
Revolut Applications API
Revolut Balance API
Revolut Card invitations API
Revolut Cards API
Revolut Configuration API
Revolut Counterparties API
Revolut Customers API
Revolut Disputes API