Skip to content

FousWolt Merchant Portal

Turn the Wolt Merchant Portal into an API

Read your payout reports, Listing manager items and opening times from the Wolt Merchant Portal with one API call each. Or have a workflow pass each new payout report to accounting and list the items disabled in every venue each morning.

Works with your own Wolt Merchant Portal account. Fous is an independent product.

What you can build on the Merchant Portal

  • Get payout reports

    Build this

    Reads the Payout Reports list for one venue and the figures in each Payout report: commissions, platform fee, sales corrections, penalties and the net payout.

    Takes
    Venue, from date (optional)
    Returns
    Payout period, net payout, commissions, platform fee, sales corrections, penalties and additional charges, currency
  • List disabled menu items

    Build this

    Reads the Listing manager for one venue and returns the items that are disabled, with their category and price.

    Takes
    Venue
    Returns
    Item name, category, price, enabled or disabled
  • Get opening times and special hours

    Build this

    Reads Opening times and Special hours under Business details for one venue.

    Takes
    Venue
    Returns
    Weekday, opening and closing time, special hours date, special hours times or closed all day
  • Add special hours for a date

    Build this

    Opens Business details for one venue, selects +Add special hours and saves the hours for a date, or marks the day Closed all day.

    Takes
    Venue, date, opening time, closing time, or closed all day
    Returns
    Venue, date, saved hours or closed all day

Automate the Merchant Portal with a workflow

A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.

  • New payout reports, handed to accounting

    Build this
    Starts
    Every weekday at 8:00
    Step 1
    For each venue you name, get the payout reports from Payout Reports.
    Step 2
    Keep the reports that were not there on the last run.
    Step 3
    Post the payout period, net payout, commissions, platform fee and corrections to your accounting webhook.
  • Disabled menu items in every venue, each morning

    Build this
    Starts
    Every day at 9:00
    Step 1
    For each venue, read the Listing manager and keep the items that are disabled.
    Step 2
    Stop when no venue has a disabled item.
    Step 3
    Email you the list, one section per venue.
  • Opening times and special hours, checked weekly

    Build this
    Starts
    Every Monday at 7:00
    Step 1
    For each venue, read Opening times and Special hours under Business details.
    Step 2
    Keep what changed since the last run.
    Step 3
    Email you the changes, one section per venue.

You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.

Once built, one call from your code

Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get payout reports” would look like.

Example request
curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "merchant.wolt.com/get_payout_reports",
    "input": {
      "venue": "Northwind Kitchen",
      "from": "2026-10-01"
    }
  }'
Example response
{
  "status": "completed",
  "data": {
    "venue": "Northwind Kitchen",
    "reports": [
      {
        "payout_period": "2026-10-16 to 2026-10-31",
        "net_payout": 8412.6,
        "commissions": 2310.4,
        "platform_fee": 412,
        "sales_corrections": -18.5,
        "penalties_and_additional_charges": 24,
        "currency": "EUR"
      }
    ],
    "count": 1
  }
}

An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.

The Merchant Portal’s own options

Wolt's Order, Menu and Venue APIs are built for POS and middleware partners, not for merchants: a partner sends an integration request, meets Wolt's minimum requirements and gets credentials from Wolt. Merchants activate a partner's integration. Payout reports and their documents are downloaded from the Merchant Portal itself.

OptionWhat it coversWhat it takes
Order, Menu and Venue APIsOrders (get, accept, reject, mark ready), menu create and update, venue online status and opening times.An integration partner: an integration request, Wolt's minimum requirements, OAuth 2.0, and a pilot venue before rollout.
Listing manager Google SheetsImport menu items from Google Sheets and export them to Google Sheets.A Merchant Portal user with menu access. Menus linked to a POS are changed through the POS provider.
The Merchant Portal by handPayout Reports with their documents, Listing manager, Business details and Access Management, one venue at a time.A Merchant Portal account for the venue, signed in with a link sent by email.

Read on November 12, 2026: Wolt developer docs: getting started for restaurants, Your guide to Wolt merchant payout reports, A guide to managing your menu on Wolt.

Signing in to the Merchant Portal

The Merchant Portal has no password: you enter the email you registered with and click the login link Wolt sends, a fresh one each time. Users are invited under Access Management. With Fous you sign in once through the Merchant Portal's own sign-in with your own account: the login is sealed with AES-256, sign-in links are handled, and an expired session is signed back in.

Worth knowing

Four documents per payout
Each payout in Payout Reports has a Wolt invoice, a Merchant invoice, a Payout report with the total net payout, and a Sales report with VAT. They download through the three dots and Download documents.
Payout cycles depend on your agreement
Most merchants are paid every 5 days, twice a month or monthly, depending on agreement and country. Payouts typically arrive within 3 to 5 business days.
POS-linked menus change in the POS
When a menu is linked to a POS, items are changed through the POS provider. Otherwise items are disabled, not deleted, in Listing manager with the eye icon.
Only a Restaurant manager adds users
A Restaurant worker can see and edit menus but cannot add users. A Restaurant manager can also invite users under Merchant Admin Users.

More in Food service, restaurants and alcohol

Other industries: Kopra by Mandiri, Comdata iConnectData, Cổng thông tin hóa đơn điện tử, MCA21, Travelport Smartpoint, SIPARE.

Frequently asked questions

Not one a merchant can sign up for. Wolt's Order, Menu and Venue APIs are built by POS and middleware partners, who get credentials from Wolt after an integration request. Merchants activate those integrations. Payout reports are downloaded from the Merchant Portal.

In the Merchant Portal, select the venue and open Payout Reports in the left sidebar. Press the three dots next to a report and choose Download documents to get the Wolt invoice, Merchant invoice, Payout report and Sales report.

Yes. Listing manager has Import from Google Sheets and Export to Google Sheets. If your menu is linked to a POS, you change it through your POS provider.

You enter the email you registered with and click the login link Wolt sends to that inbox. A new link is sent each time you log in. If you no longer have access to that email, Wolt asks you to contact your local Merchant Team.

No. Fous is an independent product. You use it with your own Wolt Merchant Portal account, and a method reads and does only what that account can.

Put Wolt Merchant Portal behind an API call

Describe one job in Studio and see the method it builds, with 100 credits a month and no credit card, or book a demo and bring the sites your team signs in to.

Read nextZomato Restaurant Partner饿了么商家版배민셀프서비스Kopra by MandiriHow methods workHow workflows run

Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of Wolt Merchant Portal (Wolt). The name is used only to say which system this page is about. Something here wrong or out of date? Write to legal@fous.com.