/google/maps/users

POST /api/google/maps/users

Price: 3 credits

Get a Google Maps contributor profile by contributor ID.

How to use it

Get a Google Maps contributor (local guide) profile by its numeric contributor ID. Returns name, profile photo, bio, Local Guide level and points, and contribution counts (reviews, photos, videos, answers, ratings, edits, captions, places added, roads added, facts checked, Q&A, reported incorrect).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• user string required — Google Maps contributor ID (numeric) (examples: "116272387233618717065"; minLength: 1)

Response

• @type string (default: "GoogleUser")
• id string required
• name string nullable
• image string nullable
• bio string nullable
• points integer nullable
• local_guide_level integer nullable
• is_local_guide boolean (default: false)
• review_count integer nullable
• photo_count integer nullable
• video_count integer nullable
• answer_count integer nullable
• rating_count integer nullable
• edit_count integer nullable
• caption_count integer nullable
• reported_incorrect_count integer nullable
• place_added_count integer nullable
• road_added_count integer nullable
• fact_checked_count integer nullable
• qa_count integer 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 — Contributor 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.