Get Parking Sections / Obtener Tramos

GET

/external/tramos

const url = 'https://api-dev.zonaparqueo.com/external/tramos';
const options = {method: 'GET', headers: {Authorization: '<Authorization>'}};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request GET \
  --url https://api-dev.zonaparqueo.com/external/tramos \
  --header 'Authorization: <Authorization>'

Gets parking sections information based on filters. Returns a paginated list with full detail. With no filters it returns the complete catalog (~414 sections, ~359 of them with activado=1).

Each section includes, among others: activado, latitud_inicio / longitud_inicio, inicio_garantizado / fin_garantizado (operating hours), activo_domingo, and the availability counters libres / librescoche / libresmoto.

id does not work as a filter. GET /external/tramos?id=474 silently ignores the parameter and returns the full catalog, with a 200 status. Measured on 2026-09-28 (5 samples): a median of 10.25 s with the parameter versus 10.55 s without it — the same request. To query a single section use GET /external/tramo/{tramo_id} or GET /external/tramo?id={tramo_id}.

The catalog’s availability counters arrive stale. In a measurement on 2026-09-28, for section 474 and at the same instant, the catalog reported libres: 7 / librescoche: 7 while the single-section query for that same section reported libres: 22 / librescoche: 22. The catalog’s libres / librescoche / libresmoto fields are indicative only: to decide whether there is space, query the section individually.

Performance: the catalog is around 654 KB and takes about 10 s (measured 2026-09-28). Cache it (e.g. 5 minutes) for geometry, names and operating hours, which change rarely, but not for availability. The provider is evaluating paginating the catalog to bring that time down.

Authorizations

ApiToken

Parameters

Query Parameters

latitud_inicio

number format: float

Start latitude

latitud_fin

number format: float

End latitude

longitud_inicio

number format: float

Start longitude

longitud_fin

number format: float

End longitude

nombre

string

Section name

direccion

string

Section address

nivel

integer

Section level

Responses

200

Paginated list of sections

application/json

object

estado

string

Allowed values: ok

data

Array<object>

object

total

Total records

integer

per_page

Records per page

integer

current_page

Current page

integer

last_page

Last page

integer

Example

{
  "estado": "ok"
}