Getting started
This guide takes you through end-to-end integration setup: from initial authentication through to production. This is for Restaurant Point of Sale and Middleware Providers.
What is POS?
A Point of Sale (POS) system is the central software and hardware platform used by restaurants to manage a range of tasks from order taking to kitchen communication. It allows restaurants to create and modify their menu directly in POS and sync it with delivery channels.
What is MWP?
A middleware provider acts as a bridge between the POS system and third-party services, such as online ordering platforms or delivery apps. Middleware solves compatibility and communication challenges between different systems. MWP can push order updates, manage venue availability and sync menu and item availability.
In the next steps you will see mandatory features as well as nice to haves.
Requirements
A thorough understanding of the OAuth method. Public explainers can be found here.
You have a merchant ready and wanting to use this integration with your system and Wolt
As a POS&MWP we require that you integrate Self-service integration (SSIO) or Wolt-led integration (WIO), Order, Venue and Menu API to ensure the best merchant experience. If you are a POS and cannot reach these requirements please reach out to a MWP and consider an integration there. Feel free to peruse our catalogue here to find the right MWP for you.
Request an integration here. After which Wolt will provide you with a client_id and client_secret. You will be sent Terms and Conditions to sign as well.
Setup&Configuration
1. Authentication and onboarding preparation
You selected the OAuth flow your system is going to use WIO and/or SSIO or Brand.
Learned more about OAuth implementation and flow design.
You've chosen an OAuth client library (you can find a list of recommended libraries here and here) or have implemented the OAuth framework yourself.
2. Venue onboarding
2a. Venue onboarding:Wolt-led integration (WIO) VERSION
The Wolt-led integration onboarding flow enables Wolt to onboard integrations for venues on behalf of integration partners. Your system can support both options SSIO&WIO, if needed.
This option is best if you don’t have a UI and/or want to keep the activation step between Wolt & you, without involvement of the merchant.
Prerequisites: you are familiar with OAuth flow and your system is ready to handle it.
Prepare an endpoint in your system which Wolt will use to send you an authorization code for each onboarded venue.
Ensure your system is able to use the authorization code to obtain access and refresh tokens for each venue.
Implement token refresh logic for expired tokens.
Confirm that you know how to extract the Wolt venue ID from the access token, necessary for certain API calls.
Wolt provided a test venue to test your implementation.
2b. Venue onboarding: Self-service integration (SSIO)
The self-service integration onboarding flow allows merchants to activate integrations for their venues via UI. This method is best if you will onboard less than 5 venues at a time. Your system can support both SSIO&WIO.
Prerequisites: you are familiar with OAuth flow and your system supports OAuth flows.
Create a page e.g. starting point in your system where Merchant can initiate the integration of their venues with Wolt.
Create a callback page in your system where merchants will be redirected to after onboarding. The redirect will include an authorization code as parameter in the URL.
Ensure your system is able to use the authorization code to obtain access and refresh tokens for each venue.
Implement token refresh logic for expired tokens.
Confirm that you know how to extract the Wolt venue ID from the access token, necessary for certain API calls.
Wolt provided a test venue to test your implementation.
2c. Venue onboarding: Brand OAuth
Brand authentication allows a brand on Wolt to access marketplace APIs for any venue belonging to the brand using a single access token. A brand refers to an entity that represents a specific merchant or a group of merchants under a common brand name. This entity is used to manage authentication and authorization processes for accessing Wolt's APIs. The brand is typically associated with a set of credentials (client ID and client secret) that are used to authenticate API requests.
Prerequisites: you are familiar with OAuth flow and your system is ready to handle it.
Ensure your system is able to use the refresh token to obtain new access and refresh tokens for your brand
Wolt provided you with venue id information and initial access & refresh tokens.
Wolt provided a test venue to test your implementation.
3. Order
Setup a webhook server to receive order status webhook notifications.
Implement the following Order API endpoints:
Required
Wolt's Order API uses webhook notifications and pull-based order retrieval, ensures that your system can accept, track, and acknowledge orders in real-time.
Optional
Mark order sent to POS(optional)
Accept self-delivery order(if self-delivery)
4. Venue
Wolt’s Venue API allows partners to monitor and manage key operational settings (like online status and opening hours).
Required
Optional
Change delivery provider (if hybrid delivery)
5. Menu
Required
With Wolt’s Menu API a partner can fetch menu data, update item details (e.g., price, availability), and push real-time inventory updates — all without managing full menu structures.
6. Testing & Go Live
Deploy the solution your staging environment.
Provide Wolt with staging access to your system.
Fill in the provided Solution scope document.
Schedule your Q&A (Go-Live) Demo call with a Wolt Technical Account Manager.
Agree with Wolt on the launch date.
Prepare a pilot venue. Deploy your system to production.
Postman Collection
Use the following Wolt public Postman collection.