SpideyDataAPI Reference
Web Data APIGoogle Maps

Google Maps API

Search Google Maps places and resolve normalized place details.

Quick start

Send a bounded synchronous place search, then use a returned opaque data_id for one explicit details lookup.

API base https://kieapi.com
curl -X POST "https://kieapi.com/v1/google-maps/search" \
  -H "Authorization: Bearer $SPIDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "keyword": "coffee",
    "latitude": 22.3,
    "longitude": 114.2,
    "viewport_span": 10000,
    "page_size": 20,
    "max_pages": 2
  }'

Authentication

Use a bearer token.

Team administrators manage API keys in Team Settings. Each key keeps its Team and billing scope when its creator leaves or switches Teams. Keys cannot manage members, billing or other keys.

Response shape

Places

Normalized name, category, address, coordinates, rating, contact fields, and opaque data_id.

Page proof

Offsets, response sizes, result counts, and overlap counts for each bounded page request.

Termination

short_page or page_budget_exhausted states the exact bounded stopping reason.

Reference

Endpoint reference

OpenAPI-backed details for Google Maps search, place details, bounds, and errors.

OpenAPI endpoint details

Interactive schemas, request bodies, response objects, and public error contracts load here.