Noon Food All-in-One API avatar

Noon Food All-in-One API

Pricing

Pay per event + usage

Go to Apify Store
Noon Food All-in-One API

Noon Food All-in-One API

Search restaurants and get full menu detail from Noon Food (UAE/KSA/Egypt) via its own guest-session mobile API.

Pricing

Pay per event + usage

Rating

0.0

(0)

Developer

Romy

Romy

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

10 days ago

Last modified

Share

Unofficial, always-on REST API for live Noon Food data: search restaurants near a location and fetch full menu detail. Wraps Noon's own mobile-app API, reverse-engineered from the real app and verified live. No account, login, or device needed for any endpoint here.

Why

Noon Food's website and app are the only way to browse restaurants and menus directly. This Actor talks to the backend API the mobile app itself uses, so results are fast, complete, and structured — full menus with prices and modifiers, not just what's visible in a search snippet.

Endpoints

All endpoints are plain GET requests on the Actor's Standby URL — no need to start a run.

ParamRequiredDescription
lat / lngyesSearch location, e.g. lat=25.0780&lng=55.1534
qnoSearch keywords (restaurant name, cuisine, dish)
countrynoCountry code, e.g. ae (default), sa, eg
searchTokennoPagination token from a previous response's nextSearchToken

Returns { outlets: [...], nextSearchToken: string | null, resolvedArea: string }. Each outlet includes name, cuisines, rating, delivery time, price indicator, and a outletCode for use with /detail.

GET /detail

ParamRequiredDescription
lat / lngyesSame location used for /search (menus and prices vary by delivery zone)
outletCodeyesOutlet code, from a /search result
countrynoSame as above

Returns the full outlet record: name, address, phone, accepting-orders status, and the complete menu tree with items, prices, modifiers, and images.

Pricing

Pay-per-event:

  • restaurant-search — charged per outlet returned from /search
  • menu-detail — charged per /detail call

Known limitations

  • No login-gated data (favorites, past orders, personalized offers) — this Actor only covers public search/menu data.
  • Results are location-scoped: the same restaurant can have different menus/prices at different lat/lng, matching Noon's own delivery-zone pricing.
  • nextSearchToken pagination must be replayed in order — skipping ahead isn't supported by Noon's own API.