VEZOO Public API v1

API VEZOO per percorsi e logistica

Integra percorsi stradali, autocomplete, geocodifica e punti di interesse lungo il tragitto in siti, CRM, ERP e consegne.

Copertura attuale: Russia, CSI, Europa, Nord e Sud America, Medio Oriente ed Egitto.

OpenAPI 3.1 include parametri, request body, header, errori, scopes ed esempi.

Accesso di prova

Dopo la registrazione, invia una richiesta di accesso API dal tuo account sviluppatore. L’amministratore verifica utilizzo, scopes e carico prima che la chiave compaia nel tuo account.

Autenticazione

Invia Authorization: Bearer <api-key>. Le chiavi possono essere disattivate o ruotate.

Accesso commerciale

Piano, scopes, RPM, quota, scadenza e browser origins sono configurabili per cliente.

Avvio rapido

Ottieni una chiave, calcola un percorso e usa route.polyline per POI e soste intelligenti.

1
Richiedi accesso
Authorization: Bearer <api-key>
2
POST /route
from + to + optional vias
3
route.polyline
Use the returned encoded polyline
4
POI / insights
Pass polyline to trip endpoints

Come si collegano i metodi

Il percorso è la base. La sua polyline viene passata a /places/along-route e /trip-insights.

STEP 1
POST /route

Returns distance, duration, segments and route.polyline.

STEP 2
POST /places/along-route

Use the polyline to fetch roadside objects by category.

STEP 3
POST /trip-insights

Use the same polyline for stop suggestions and smart trip planning.

Metodi API

GET/citiesscope: cities≤ 120 RPM

Autocomplete / location search

Parametri
q: string (2–80, required) · limit: integer (1–20, default 10)
GET/geocodescope: geocode≤ 30 RPM

Forward and reverse geocoding

Parametri
q: string OR lat + lon
GET | POST/routescope: route≤ 60 RPM

Road route with up to 12 via points and exclusions

Parametri
from, to · vias[] / v · exclude: toll,motorway,ferry
POST/places/along-routescope: places≤ 20 RPM

Fuel, food, lodging, service, tyres, parking and charging

Parametri
polyline · categories[] (optional)
POST/trip-insightsscope: insights≤ 12 RPM

Suggested stops and automatic trip plan

Parametri
polyline

Limiti

Vale il limite più basso tra client ed endpoint. Il superamento restituisce HTTP 429.

cities 120 · route 60 · geocode 30 · places 20 · insights 12 RPM

Scopes

Ogni chiave può essere limitata ai soli metodi necessari.

citiesroutegeocodeplacesinsights

Browser origins

Le richieste browser possono essere limitate a Origin autorizzati.

Esempi pronti

cURL · route
curl -G 'https://vezoo.ru/api/v1/route' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  --data-urlencode 'from=Москва' \
  --data-urlencode 'to=Казань' \
  --data-urlencode 'v=Владимир' \
  --data-urlencode 'exclude=ferry'
JavaScript · route
const response = await fetch('https://vezoo.ru/api/v1/route', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer YOUR_API_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    from: 'Москва',
    to: 'Казань',
    vias: ['Владимир'],
    exclude: ['ferry'],
  }),
});
const data = await response.json();
console.log(data.route.polyline);
cURL · places along route
curl -X POST 'https://vezoo.ru/api/v1/places/along-route' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "polyline":"ENCODED_POLYLINE_FROM_ROUTE",
    "categories":["fuel","food","lodging","parking","charging"]
  }'
PHP · route
$payload = json_encode([
    'from' => 'Москва',
    'to' => 'Казань',
]);
$ch = curl_init('https://vezoo.ru/api/v1/route');
curl_setopt_array($ch, [
    CURLOPT_POST => true,
    CURLOPT_HTTPHEADER => [
        'Authorization: Bearer YOUR_API_KEY',
        'Content-Type: application/json',
    ],
    CURLOPT_POSTFIELDS => $payload,
    CURLOPT_RETURNTRANSFER => true,
]);
$data = json_decode(curl_exec($ch), true);
JSON · route response
{
  "success": true,
  "from": "Москва",
  "to": "Казань",
  "via": [],
  "exclude": [],
  "route": {
    "kilometers": 817.4,
    "minutes": 667,
    "polyline": "...",
    "segments": [...]
  }
}

Errori

Gli errori di autenticazione e quota usano error_code stabili. La validazione restituisce HTTP 422.

HTTPerror_codeMeaning
401invalid_api_keyMissing or invalid key
401api_key_disabledKey was disabled
401api_key_expiredKey expired
403scope_forbiddenScope is not allowed
403origin_forbiddenBrowser Origin is not allowed
404not_found / unknown_location / no_routeLocation or route was not found
422validation errorRequest parameters are invalid
429rate_limit_exceededPer-minute limit exceeded
429quota_exceededTotal key quota exhausted
503api_disabled / api_not_configuredPublic API unavailable
503service_unavailableRequired routing service unavailable

Header di risposta

Usa X-Request-Id per il supporto e X-RateLimit-* per gestire il traffico.

X-API-Version

API version used for the response

X-Request-Id

Unique request identifier for diagnostics

X-RateLimit-Limit

Effective requests-per-minute limit

X-RateLimit-Remaining

Requests remaining in the current minute

X-Quota-Limit

Total quota when configured for this key

X-Quota-Remaining

Remaining total quota

Retry-After

Seconds before retrying after HTTP 429

Base URL

https://vezoo.ru/api/v1

Authentication: Authorization: Bearer YOUR_API_KEY