/meituan/areas

POST /api/meituan/areas

Price: 5 credits

Get the restaurant catalogue areas of a Meituan city for one food category: the city total, every district, business area, subway line and subway station with its restaurant count, stations with coordinates

How to use it

Pass the numeric Meituan city id (1 Beijing, 10 Shanghai, 57 Wuhan) and a food category id (1 all food, 17 hotpot, 11 desserts and drinks, 40 buffet, 36 snacks and fast food, 35 Western, 54 barbecue, 20004 grilled fish, 63 seafood). The city total is not the sum of its districts, so do not add district counts to get it. A null `restaurant_count` is unknown, not zero.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• city_id integer required — Meituan city id (examples: 1, 10, 57; min: 1)
• category_id integer — Meituan food category id; 1 is all food (default: 1; examples: 1, 17, 11; min: 1)
• area_type string nullable — Return only areas of this type (one of: "city", "district", "business_area", "subway_line", "subway_station"; examples: "subway_station")
• count integer required — Max number of results (min: 1)

Response

• @type string (default: "MeituanArea")
• area_type string required (one of: "city", "district", "business_area", "subway_line", "subway_station")
• area_id string nullable
• name string required
• parent_id string nullable
• parent_name string nullable
• city_id string required
• category_id string required
• restaurant_count integer nullable
• latitude number nullable
• longitude number nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Unknown city id, or the category has no restaurants in that city Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.