FousGlovo Manager Portal
Turn the Glovo Manager Portal into an API
Read your Order History, Performance metrics and customer Reviews from the Glovo Manager Portal with one API call each. Or have a workflow check yesterday's orders with operational issues every morning, store by store, before the lunch shift.
Works with your own Glovo Manager Portal account. Fous is an independent product.
What you can build on the Manager Portal
Get order history
Build thisReads Order History for one store and a date range, filtered by order status, type, payment method or operational issue.
- Takes
- Store, from date, to date, order status (optional), operational issue (optional)
- Returns
- Order code, date and time, status, type, payment method, operational issue, total
Get store performance
Build thisReads the sales, operations and customer metrics on the Performance page for one store and period.
- Takes
- Store, period
- Returns
- Sales metrics, operations metrics, customer metrics, period
Get customer reviews
Build thisReads the customer ratings and reviews listed under Reviews for one store.
- Takes
- Store, since date (optional)
- Returns
- Date, rating, review text
Set a special schedule in Opening Times
Build thisOpens Opening Times for one store and adds a special schedule for a date, with the hours you give or closed for the day.
- Takes
- Store, date, opening hours or closed
- Returns
- Store, date, hours saved
Automate the Manager 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.
Yesterday's orders with operational issues, every store
Build this- Starts
- Every day at 8:00
- Step 1
- For each store you name, get yesterday's Order History.
- Step 2
- Keep the orders that show an operational issue.
- Step 3
- Email you the list, one section per store, with order code, issue and total.
Weekly performance report for each store
Build this- Starts
- Every Monday at 9:00
- Step 1
- For each store, get last week's sales, operations and customer metrics from Performance.
- Step 2
- Have an AI step write a short summary per store.
- Step 3
- Post the metrics and the summary to your reporting system's webhook.
New low-rated reviews, posted to your team
Build this- Starts
- Every day at 17:00
- Step 1
- For each store, get the customer reviews from the last 2 days.
- Step 2
- Keep the reviews that were not there on the last run and have a rating of 3 or less.
- Step 3
- Post each one, with store, date, rating and text, to your Slack webhook.
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 order history” would look like.
curl https://api.fous.com/v1/runs \
-H "Authorization: Bearer $FOUS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"method": "portal.glovoapp.com/get_order_history",
"input": {
"store": "Acme Burgers, Central",
"from": "2026-11-11",
"to": "2026-11-11",
"operational_issue": "any"
}
}'
{
"status": "completed",
"data": {
"store": "Acme Burgers, Central",
"orders": [
{
"order_code": "A7KQ2P",
"placed_at": "2026-11-11T12:41:00",
"status": "Delivered",
"type": "Delivery",
"payment_method": "Card",
"operational_issue": "Late pickup",
"total": 18.4,
"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 Manager Portal’s own options
Glovo's Partners API is for POS providers and integrators: it sends orders to your POS and lets you upload menus, update products and close a store temporarily. Access is requested from Glovo's partner integrations team and is tested on a stage environment before production. Order History, Performance and Reviews are read in the Manager Portal itself.
| Option | What it covers | What it takes |
|---|---|---|
| Partners API: orders | New, picked-up and cancelled orders posted to your webhooks, and updates such as accept, ready for pickup and adjusted preparation time. | Access requested by email, your webhook endpoints, testing on the stage environment, then production rollout with Glovo's local teams. |
| Partners API: menu and store | Menu upload, changes to products, attributes and items in bulk, and a temporary closing that overrides regular opening times. | The same credentials: a shared token per integration. Limit of 120 requests per minute; menus must match Glovo's JSON schema. |
| The Manager Portal by hand | Dashboard, Performance, Order History, Reviews, Advertising, Promotions, Menu, Opening Times and Settings. | A Manager Portal account: email and password. |
Read on November 12, 2026: Glovo Partners API, How to use the Manager Portal.
Signing in to the Manager Portal
The Manager Portal signs you in with your email and password. New partners get a "Welcome to the Manager Portal" email with a Create password button, and Forgot password? resets it. With Fous you sign in once through the Manager Portal's own sign-in with your own account: the login is sealed with AES-256, and an expired session is signed back in.
Worth knowing
- Stores per city, addresses per location
- Glovo's Partners API documentation counts one store per city and one store address per physical location, each with its own store id. Build each method to take the store as an input.
- Settings can limit what an account sees
- Settings lets you restrict access to certain sections or stores within your account. A method reads only the stores and sections that the account it signs in with can open.
- Help replies arrive only in the Inbox
- Answers to requests sent through Help appear in the Inbox of the Help section, and you get no email when one arrives. Check that Inbox for anything you raise through Help.
- The Partners API is built for a POS
- Its documented endpoints cover orders, menus, products and temporary closing. You need webhook endpoints to receive orders, and the access token is static for each environment and webhook.
More in Food service, restaurants and alcohol
- SGWS Proof
- Provi
- myCoke
- BEES
- METRO Online-Kundenkonto
- Sligro
- Deliveroo Partner Hub
- DoorDash Merchant Portal
- foodpanda Partner Portal
- GrabMerchant
- Grubhub for Restaurants
- iFood Portal do Parceiro
- Just Eat Partner Hub
- PedidosYa Partner Portal
- Rappi Aliados
- Swiggy Partner
- Uber Eats Manager
- Wolt Merchant Portal
- Zomato Restaurant Partner
- 饿了么商家版
- 배민셀프서비스
- Gordon Ordering
- PFG CustomerFirst
- Sysco Shop
- US Foods MOXē
- Bidfood Direct
- Brakes
- Transgourmet Webshop
- レストランボード
- OpenTable GuestCenter
- TheFork Manager
- Restaurant365
- 食べログ店舗管理画面
- Oracle MICROS Simphony Reporting & Analytics
- Toast Web
- Insights C3M
Other industries: Bradesco Net Empresa, Portal Rede, My.SSS Employer Portal, EPFO Unified Portal (Employer), Expedia Partner Central, SEACE.
Frequently asked questions
Not for the Manager Portal's own screens. Glovo's Partners API is for POS providers and integrators: it sends orders to your POS and lets you upload menus, update products and close a store temporarily. Access is requested from Glovo's partner integrations team. Order History, Performance and Reviews stay in the portal.
In Order History in the Manager Portal. You can filter past orders by order status, type, payment method and operational issues. With Fous, a method you build can read that list for a store and a date range and return it as JSON.
Yes, in Opening Times, which holds your store's hours, special schedules included. For integrated stores, the Partners API can also close a store temporarily, overriding its regular opening times.
Glovo sets the rate limit at 120 requests per minute, and its documentation asks integrators to respect it. Uploaded menus must match its JSON schema or are rejected, and image URLs must use HTTPS.
No. Fous is an independent product. You use it with your own Manager Portal account, and a method reads and does only what that account can.
Put Glovo Manager 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 nextGrabMerchantGrubhub for RestaurantsiFood Portal do ParceiroBradesco Net EmpresaHow methods workHow workflows run
Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of Glovo Manager Portal (Glovo). 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.