Quick start

The ZPP external API lets third-party platforms query sections (parking zones), register clients and vehicles, create and pay reservations, and query or pay sanctions.

Servers

Environment	Base URL
Development	https://api-dev.zonaparqueo.com
Production	https://api.zonaparqueo.com

Every endpoint lives under the /external prefix.

The three steps

1. Authenticate. POST /external/login returns a session token, which you use to generate a permanent API token. See Authentication.
2. Send the token on every request, in the Authorization: Token {token_id}:{token_secret} header.
3. Call the endpoint you need. The reference documents each one.

Your first request

curl -X GET "https://api-dev.zonaparqueo.com/external/tramos" \
  -H "Authorization: Token YOUR_TOKEN_ID:YOUR_TOKEN_SECRET"

The response carries the full section catalog (around 414, of which roughly 359 are active), with coordinates, operating hours and availability counters.

Two things about the catalog

It is around 654 KB and takes about 10 s, so cache it rather than requesting it on every call. And its availability counters arrive stale: to know whether a section has space, query it with GET /external/tramo/{tramo_id}. See integration notes.

Response shape

Every response uses the same envelope:

{ "estado": "ok", "data": { } }

On error, estado is fail and an error field carries the message:

{ "estado": "fail", "error": "La placa no existe" }

Read the integration notes

Several endpoints do not behave the way their name suggests: some use a path parameter instead of a query string, and one reads a JSON body on a GET. Before writing code, read the integration notes.

Onboarding a vehicle

Registering a vehicle takes two calls, in this order:

1. POST /external/placa — registers the plate in the system.
2. POST /external/vehiculo — creates the vehicle, linking that plate to a client.

Skipping the first step makes the second one fail.