GTT: Get Line Percorsi
GTT via Parse · maps_geo
Get a line's metadata and all available routes/variants (percorsi) including route codes, directions, stop lists, polylines, and service days. Upstream response times may vary (up to 60s for some lines). The percorsi array contains codice/verso pairs needed for get_percorso and get_percorso_schedule calls. APIs to enumerate GTT lines and extract full-day scheduled departure times at each stop using GTT's public das_ws service. Also includes stop search and real-time arrivals per stop. Fulfilled by Parse from gtt.to.it.
- government-public
- gtt
- gtt-to-it
- maps-geo
- parse
- platform-key
- travel
Price and execution
- Price
- $0.02 USD credits / call
- Trust tier
- Verified
- Execution
- Managed call
- Capability group
- maps_geo
Interface snapshot
- Protocol
- HTTP operation
- Operation
- GET /scraper/559cc6d3-d8a1-4547-9bea-ee0e78b2dcae/get_line_percorsi
- Interface artifact
- sha256:33575b4c945d80930ba6cb420edda6be22f2e3b1a10d345b576a46a7a7fc0058
- Manifest digest
- sha256:6ad40a144356147a38d48a1fd1429ef487acb187ea6ad8329e1d25dc9d738047
Request fields
- linea (string, required): Line code (e.g. 3, 1068, METRO). Obtain from list_lines endpoint.
- bacino (string): Service basin code.: Allowed values: U, E
Example queries
- {"linea":"2","bacino":"U"}