AMap (Gaode / 高德地图) Directions API | China Driving, Transit & Route Planner (2026)

Point-to-point routes anywhere in China: driving, transit, walking, cycling and e-bike directions with distance, travel time, tolls, live traffic, turn-by-turn steps and route geometry, as structured JSON. No AMap key or login.

Zen Studio Maps Suite   •  Places, reviews, and routes across every major map provider
AMap Directions ➤ You are here	AMap Places Places, contacts, reviews	AMap Gas Prices Discount fuel prices	Baidu Maps China POI, deals, reviews	Google Maps Places, reviews, times

Key Features

• Five travel modes: driving, public transit, walking, cycling, and e-bike routing, each with its own fields and turn-by-turn steps.
• Live traffic driving routes: every driving route carries per-step traffic status (clear, slow, congested), toll cost, traffic-light count, and up to 3 route alternatives to compare.
• Full public transit plans: subway, bus and intercity-rail segments with line names, boarding and alighting stops, every via-stop, first/last service times, fare, walking legs, and station entrances and exits.
• Names, addresses, or coordinates: enter a place name (北京西站), a nickname (鸟巢), a full address, or longitude,latitude coordinates. Everything is resolved automatically.
• Batch routing: compute up to 10 routes in one run from a single list of origin/destination pairs, calculated in parallel.
• No AMap key, no login: enter two points and run. No AMap developer key, Chinese phone number, or sign-in.

Copy to your AI assistant

zen-studio/amap-directions-api on Apify. AMap (Gaode / 高德地图) China directions: driving/walking/bicycling/electrobike/transit routes with distance, duration, tolls, live traffic, turn-by-turn steps, route geometry, and transit segments (subway/bus/rail). Call ApifyClient("TOKEN").actor("zen-studio/amap-directions-api").call(run_input={...}), then client.dataset(run["defaultDatasetId"]).list_items().items. Provide origin+destination (place name, address, or "lng,lat") + travelMode, OR routePairs[] for batch routing. Full spec: GET https://api.apify.com/v2/acts/zen-studio~amap-directions-api/builds/default (Bearer TOKEN) -> inputSchema, actorDefinition.storages.dataset, readme. Token: https://console.apify.com/account/integrations

How to Get Directions from AMap (Gaode)

Basic: a driving route between two points

{
  "origin": "北京西站",
  "destination": "望京SOHO",
  "travelMode": "driving"
}

Origin and destination each accept a place name, a nickname, a full address, or longitude,latitude coordinates (AMap's native order, GCJ-02). Names and nicknames are resolved automatically, so 鸟巢 and 国家体育场 both work.

Public transit, including cross-city

{
  "origin": "北京南站",
  "destination": "天津站",
  "travelMode": "transit"
}

Transit returns every plan the app would show, broken down into walking, subway, bus and intercity-rail segments with line names, stops, fares and service times.

Avoid tolls or motorways (driving)

{
  "origin": "上海虹桥站",
  "destination": "杭州东站",
  "travelMode": "driving",
  "avoidTolls": true
}

Multi-stop driving route with waypoints

{
  "origin": "天安门",
  "destination": "北京首都国际机场",
  "waypoints": ["鸟巢", "望京SOHO"],
  "travelMode": "driving"
}

Batch: many routes in one run

{
  "travelMode": "driving",
  "routePairs": [
    { "origin": "北京西站", "destination": "望京SOHO" },
    { "origin": "上海虹桥站", "destination": "外滩" },
    { "origin": "116.481,39.990", "destination": "116.434,39.908" }
  ]
}

When routePairs is filled, the single origin/destination is ignored and the travel mode and preferences apply to every route.

Input Parameters

Parameter	Type	Default	Description
origin	string	北京西站	Route start: place name, address, or lng,lat coordinates.
destination	string	首都国际机场T3	Route end. Same formats as origin.
waypoints	array	[]	Intermediate stops, in order. Driving mode only, up to 16.
city	string	""	Optional region hint to disambiguate a place name shared by several cities.
travelMode	select	driving	driving, walking, bicycling, electrobike, or transit.
avoidTolls	boolean	false	Prefer routes that avoid toll roads (driving).
avoidHighways	boolean	false	Prefer routes that avoid motorways (driving).
nightBus	boolean	false	Prefer night-bus lines (transit).
routeDetail	select	full	full (steps + traffic + geometry), overview (steps, no polylines), or summary (trip totals only).
includeAlternatives	boolean	true	Keep all route options, or set false for the best route/plan only.
routePairs	array	[]	Batch mode: up to 10 {origin, destination, waypoints} objects, one route each, computed in parallel.

Coordinates use AMap's native longitude,latitude order in the GCJ-02 system (the China grid AMap and WeChat use); distances are in metres and durations in seconds, with a human-readable distanceText/durationText alongside.

What Data Can You Extract from AMap Directions?

Every route record includes:

• Trip summary: travel mode, resolved origin and destination (query, coordinates, city, admin code), waypoints, total distance and duration (metres/seconds plus readable text), estimated taxi cost, and the number of route options.
• Driving / walking / cycling / e-bike routes: for each alternative — distance, duration, toll cost, toll distance, traffic-light count, driving restrictions, the cities and districts the route crosses, the full route polyline, and turn-by-turn steps.
• Steps: instruction text, road name, orientation, distance, duration, action and assistant action, per-step tolls, and per-step live traffic status with its own geometry.
• Transit plans: for each plan — duration, fare, total and walking distance, night-bus flag, and ordered segments.
• Transit segments: walking legs with steps, station entrances and exits, and bus/subway/rail lines with names, types, departure and arrival stops, every via-stop, distances, durations, first and last service times (line-wide and at your boarding stop), and line geometry. Intercity rail carries its train number, scheduled departure and arrival times, seat classes with prices, and alternative trains; and where public transit doesn't reach, a taxi leg is included with its own distance, duration and endpoints.

Output example — driving

{
  "travelMode": "driving",
  "origin": { "query": "北京西站", "latitude": 39.894912, "longitude": 116.322033, "matchedCity": "北京市", "adcode": "110106" },
  "destination": { "query": "望京SOHO", "latitude": 39.996743, "longitude": 116.481075, "matchedCity": "北京市", "adcode": "110105" },
  "waypoints": [],
  "distanceMeters": 23630,
  "durationSeconds": 2937,
  "distanceText": "23.6 km",
  "durationText": "48 min",
  "taxiCostYuan": 70.0,
  "routeCount": 3,
  "routes": [
    {
      "distanceMeters": 23630,
      "durationSeconds": 2937,
      "tolls": 0.0,
      "tollDistanceMeters": 0,
      "trafficLights": 5,
      "restriction": 0,
      "polyline": "116.322119,39.896235;116.322174,39.896233; ...",
      "steps": [
        {
          "instruction": "向东北行驶224米右转",
          "road": null,
          "orientation": "东北",
          "distanceMeters": 224,
          "durationSeconds": 181,
          "action": "右转",
          "assistantAction": null,
          "tolls": 0.0,
          "tollDistanceMeters": 0,
          "trafficLights": 0,
          "polyline": "116.322174,39.896233;116.322276,39.896230; ...",
          "traffic": [
            { "status": "拥堵", "distanceMeters": 17, "polyline": "116.322174,39.896233; ..." }
          ]
        },
        "... +19 more steps"
      ]
    },
    "... +2 more route alternatives"
  ]
}

Output example — transit

{
  "travelMode": "transit",
  "origin": { "query": "北京南站", "latitude": 39.865246, "longitude": 116.378517, "matchedCity": "北京市", "adcode": "110106" },
  "destination": { "query": "天津站", "latitude": 39.135951, "longitude": 117.210089, "matchedCity": "天津市", "adcode": "120105" },
  "waypoints": [],
  "distanceMeters": 156913,
  "durationSeconds": 16196,
  "distanceText": "156.9 km",
  "durationText": "4 h 29 min",
  "taxiCostYuan": 1.0,
  "routeCount": 4,
  "routes": [
    {
      "durationSeconds": 16196,
      "costYuan": 37.0,
      "distanceMeters": 156913,
      "walkingDistanceMeters": 1429,
      "nightBus": false,
      "segments": [
        {
          "walking": { "distanceMeters": 160, "durationSeconds": 137, "steps": ["... 5 steps"] },
          "entrance": { "name": "D西入口", "latitude": 39.86483, "longitude": 116.378708 },
          "exit": null,
          "buslines": [
            {
              "name": "地铁14号线(张郭庄--善各庄)",
              "type": "地铁线路",
              "lineId": "900000028908",
              "departureStop": { "name": "北京南站", "stopId": "900000028908013", "latitude": 39.865029, "longitude": 116.378963 },
              "arrivalStop": { "name": "九龙山", "stopId": "900000028908023", "latitude": 39.893395, "longitude": 116.477492 },
              "distanceMeters": 11650,
              "durationSeconds": 1530,
              "firstServiceTime": "0455",
              "lastServiceTime": "2242",
              "viaStopCount": 7,
              "viaStops": [{ "name": "永定门外", "stopId": "900000028908015", "latitude": 39.867686, "longitude": 116.399253 }, "... +6"],
              "polyline": "116.378963,39.865029; ..."
            }
          ],
          "railway": null
        },
        "... +3 more segments"
      ]
    },
    "... +3 more transit plans"
  ]
}

No key is ever dropped: fields that do not apply to a mode (tolls on a walking route, railway on a subway segment) stay present as null.

Advanced Usage

Ready-made configurations for logistics, travel time matrices, and multi-modal comparison.

Travel-time matrix: one origin to many destinations, lean output

Route geometry (polylines) is over half of a driving result, so a matrix that only needs distance and time can shrink each record from ~100 KB to ~1 KB with routeDetail: "summary".

{
  "travelMode": "driving",
  "routeDetail": "summary",
  "includeAlternatives": false,
  "routePairs": [
    { "origin": "上海虹桥站", "destination": "外滩" },
    { "origin": "上海虹桥站", "destination": "上海迪士尼" },
    { "origin": "上海虹桥站", "destination": "浦东国际机场" }
  ]
}

Use routeDetail: "overview" instead when you want turn-by-turn steps and live traffic but not the coordinate geometry.

Compare driving vs transit for the same trip

Run the actor twice with the same origin and destination, switching travelMode between driving and transit, then compare durationSeconds and cost.

Cycling and e-bike routes for last-mile delivery

{
  "origin": "望京SOHO",
  "destination": "798艺术区",
  "travelMode": "electrobike"
}

Coordinates in, for precise pick-up and drop-off

{
  "origin": "116.481,39.990",
  "destination": "116.434,39.908",
  "travelMode": "driving"
}

Pricing

Pay per route, with volume discounts as your Apify plan tier rises. You are billed once for each route that returns a result: a failed lookup or an unroutable pair is free, and all route alternatives for a trip are included at no extra cost. One route is one origin-to-destination computation in one travel mode. The current per-route price and tier discounts are shown on this Actor's page.

A batch run bills one route per origin/destination pair (up to 10 per run).

FAQ

What is AMap (Gaode / Autonavi / 高德地图)? AMap, also written Gaode, Autonavi, or 高德地图, is China's most-used mapping and navigation platform, owned by Alibaba. Its routing engine has the deep road, traffic and public-transit coverage of mainland China that Google Maps lacks. This actor turns AMap route planning into structured JSON.

Do I need an AMap API key or a Chinese account? No. You enter an origin and a destination and run. There is no AMap developer key, Chinese phone number, or sign-in involved. Official AMap keys are hard to obtain outside China and rate-limited, which is why this is the practical route to China routing data.

Which travel modes are supported? Driving, public transit, walking, cycling, and e-bike (电动车). Driving returns up to three alternatives with live traffic; transit returns full multi-segment plans with subway, bus and intercity-rail legs.

Does it include live traffic? Yes. Every driving route carries per-step traffic status (clear, slow, congested) and a traffic-light count, so the duration reflects current conditions.

Can I enter place names, or only coordinates? Both. Place names, nicknames (鸟巢), and full addresses are resolved automatically. You can also pass longitude,latitude coordinates directly for exact pick-up and drop-off points.

What coordinate system does it use? AMap uses GCJ-02, the offset grid shared by AMap and WeChat inside China. Coordinates are returned exactly as AMap provides them, in longitude,latitude order. If you pass raw GPS (WGS-84) coordinates they will be slightly offset, so use GCJ-02 or a place name for best accuracy.

Can I compute many routes at once? Yes. Use routePairs to pass a list of origin/destination pairs and the actor computes them all in one run, billing one route each. This is the way to build a travel-time or distance matrix.

Does transit cover high-speed rail and cross-city trips? Yes. Give two points in different cities and transit returns plans that include intercity rail and long-distance segments, with line names, stops, and service times.

Why AMap instead of Google Maps for China? Google Maps routing inside mainland China is thin and often out of date, and Google's road and transit data for China is limited. AMap and Baidu are where accurate Chinese routing, traffic and transit data live.

Can I schedule runs or push results to Google Sheets? Yes. Schedule this actor on any cadence from the Apify console, and connect the output to Google Sheets, Make, Zapier, or your own server via webhooks and the Apify API.

How do I export the data? Download JSON, CSV, Excel, XML, or HTML from the run's Storage tab, or pull it through the Apify API. JSON preserves the nested fields (routes, steps, transit segments) best.

Is it legal to use AMap (Gaode) directions data? This actor computes publicly available routing information. You are responsible for how you use it, including compliance with AMap's terms and applicable law. Review the terms for your use case before deploying at scale.

More Zen Studio scrapers for maps & local data

• AMap 高德地图
  • AMap Places Scraper
  • AMap Gas Prices Scraper
• Baidu Maps 百度地图
  • Baidu Maps Scraper
• Google Maps
  • Google Maps Scraper
  • Google Maps Directions & Routes API
• Apple Maps
  • Apple Maps Scraper
  • Apple Maps Directions & Route API
• Yandex Maps Яндекс Карты
  • Yandex Maps Scraper
  • Yandex Maps Reviews Scraper
• 2GIS 2ГИС
  • 2GIS Places Scraper
  • 2GIS Reviews Scraper

Support

• Bugs: Issues tab
• Features: Issues tab

Legal Compliance

Uses publicly available routing information. Users must comply with AMap (Gaode / 高德地图) terms and applicable data protection regulations, including GDPR, CCPA, and China's PIPL.

---

Get driving, transit, walking, cycling and e-bike directions from AMap (Gaode / 高德地图) for anywhere in China: distance, travel time, tolls, live traffic, turn-by-turn steps and route geometry as structured JSON.