/twogis/places

POST /api/twogis/places

Price: 5 credits

Get a 2GIS place (organization / branch) by its numeric id

How to use it

Get full 2GIS place details by numeric firm/branch id. Returns name, address, coordinates, phone, website, email, social links, working schedule, rubrics (categories), multi-provider rating and review counts, attributes (cuisine, average bill, payment, features), the parent organization with branch count, and nearby metro stations.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• place string required — Numeric 2GIS firm/branch id (from the place URL 2gis.ru/.../firm/{id} or from search) (examples: "70000001035840049"; minLength: 1)
• region_id string nullable — 2GIS region id for output localization

Response

• @type string (default: "TwogisPlace")
• id string required
• name string required
• type string nullable
• address string nullable
• address_comment string nullable
• latitude number nullable
• longitude number nullable
• region_id integer nullable
• city string nullable
• district string nullable
• rating number nullable
• review_count integer nullable
• rating_count integer nullable
• org_rating number nullable
• org_review_count integer nullable
• provider_ratings array (default: [])
  • @type string (default: "TwogisProviderRating")
  • tag string required
  • rating number nullable
  • review_count integer nullable
• phone string nullable
• website string nullable
• email string nullable
• socials object (default: {})
  • * string
• ad_text string nullable
• schedule array (default: [])
  • @type string (default: "TwogisScheduleDay")
  • day string required
  • working_hours array (default: [])
• rubrics array (default: [])
  • @type string (default: "TwogisRubric")
  • id string required
  • name string required
  • alias string nullable
  • kind string nullable
  • parent_id string nullable
• primary_rubric string nullable
• attributes array (default: [])
  • @type string (default: "TwogisAttribute")
  • name string required
  • tag string nullable
• org object nullable
  • @type string (default: "TwogisOrg")
  • id string required
  • name string nullable
  • branch_count integer nullable
• nearest_metro array (default: [])
  • @type string (default: "TwogisNearbyStation")
  • id string required
  • distance integer nullable
• nearest_stations array (default: [])
  • @type string (default: "TwogisNearbyStation")
  • id string required
  • distance integer nullable
• nearest_parking array (default: [])
  • @type string (default: "TwogisNearbyStation")
  • id string required
  • distance integer nullable
• has_photos boolean (default: false)
• created_at string nullable
• updated_at string nullable
• url string 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 — Place not found for the given id 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.