GloriaFood has no “download my menu” button. What it has instead is a documented Fetch Menu API, and it returns everything in one call. This page walks through it start to finish.
These instructions work whether you are moving to us, moving to a competitor, or just want a copy of your own menu for safekeeping. That is deliberate — it is your menu.
Everything below is from GloriaFood’s own integration documentation, checked August 13, 2026.
Step 1: generate the API key
In the Restaurant Admin Panel:
- Open Others — it is the ”…” icon, which is easy to miss.
- Go to 3rd party integrations.
- Open the Enabled integrations menu.
- Select the template “Fetch Menu”.
- Generate the key.
The key is a short secret string. Treat it like a password: it grants read access to your menu.
Running more than one branch? Each key corresponds to one restaurant’s menu, so a nine-branch group means repeating this nine times and keeping nine keys straight. Label them as you go — they look alike, and matching the wrong key to the wrong branch is the classic multi-location migration mistake.
Step 2: make the request
- URL:
https://pos.globalfoodsoft.com/pos/menu - Method: GET
- Headers:
Authorization: <your key>Glf-Api-Version: 2Accept: application/json(orapplication/xmlif you prefer XML)
With curl, that is one line:
curl -H "Authorization: YOUR_KEY_HERE" \
-H "Glf-Api-Version: 2" \
-H "Accept: application/json" \
https://pos.globalfoodsoft.com/pos/menu > gloriafood-menu.jsonThat file is your menu. Keep it somewhere safe and backed up — it is the single most valuable artefact of your GloriaFood setup, and it takes seconds to produce.
If curl means nothing to you: paste the command above to anyone technical, or to any AI assistant, and ask them to run it with your key. It is a read-only request and it changes nothing in your account.
Step 3: know what you actually got
The payload is a complete menu tree. Per GloriaFood’s documentation:
| Object | What it carries |
|---|---|
| Menu | id, restaurant_id, currency, categories, items |
| Category | id, name, items, groups |
| Item | id, name, description, price, sizes, groups, tags, extras |
| Size | id, name, price, default, groups, extras |
| Option group | id, name, required, allow_quantity, force_max, force_min |
| Option | id, name, price, default, extras |
Two details worth understanding, because they are where menus get mangled in migration:
Option groups hang off sizes as well as items. A Size has its own groups array. That is how a 9-inch pizza offers a different set of toppings than a 14-inch one. Any tool that flattens sizes and items into one list loses this, and you end up with every topping showing on every size. If you are evaluating a migration tool, this is the thing to test with your most complicated dish.
force_min and force_max are your rules. They encode “pick exactly one crust” and “up to four toppings”. They are the difference between a menu that takes correct orders and one that lets a customer order a pizza with no base.
What the export does not include
Your dish photos. GloriaFood’s documentation states plainly that item photos are not included in the payload. There is no bulk download for them either — the Menu Editor is the only place to save them, one at a time.
Budget an hour or two if you have 80-plus items. Two things worth knowing while you do it:
- Relaunching with placeholder images is felt in orders during the first week. The photos are worth the effort.
- A fair share of GloriaFood item images are its own stock photography. You may not want to carry those anywhere, which makes this a reasonable moment to photograph the real dishes.
Everything that is not the menu. The Fetch Menu API is documented as returning the menu, and GloriaFood documents no other export endpoint. So your delivery zones, opening hours, prep times, delivery fees, tax rules, payment configuration and promotions are not covered by it. Screenshot those settings pages while the platform is up — they have to be rebuilt by hand wherever you land.
Your customers and orders
Separate from the menu, your client contacts and order history can be exported as CSV from the admin, under Marketing → Customers → Export. Do this too. You will want it for reactivation campaigns and for your own records, and it is not covered by the menu API.
If you would rather not do any of this
Hand us the key and we do the rest. Ontabee takes your Fetch Menu key, pulls the menu across — categories, items, sizes, option groups, the force_min/force_max rules and the availability windows, with size-level option groups kept where they belong — and shows you a preview of exactly what it found before anything is written.
Photos come across only where your account exposes a picture URL, because they are not in the documented payload. The rest we re-upload with you. Delivery zones, hours and fees get set up alongside the import, since nothing exports them.
Most single-location restaurants are live the same day.
→ What transfers and what doesn’t, line by line · See how migration works · What else does not export