Back to Developer PortalMaps Servicev1 Planned

Maps Service API Documentation

One canonical reference for directions, matrix, search, autocomplete, reverse geocoding, nearby places, place details, and map matching at api.omysyria.com.

One Maps Service key for every operation

Create an organization-scoped key in the Maps Service dashboard. The full key is shown once and works across every enabled operation in that organization.

Security boundary

Send the key in X-API-Key or Bearer from your trusted server only. Never put it in browser/mobile code, URLs, or logs. Per-service commercial quotas remain planned.

API v1 reference

Eight unified service contracts

Operations remain Planned until their authorized hosted rollout is complete. The examples below are the canonical public contracts.

POST /v1/directionsPlanned

Request example

curl -X POST 'https://api.omysyria.com/v1/directions'
  -H 'X-API-Key: YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  --data '{"origin":{"lat":33.5138,"lng":36.2765},"destination":{"lat":33.5102,"lng":36.2913},"preference":"fastest","costing":"auto"}'

Response shape

{
  "summary": {
    "distance": {
      "meters": 3900,
      "kilometers": 3.9
    },
    "duration": {
      "seconds": 720,
      "minutes": 12
    }
  },
  "geometry": "polyline6…"
}

Shared safe responses

HTTPCodeMeaning
401maps_api_key_requiredThe customer key is missing.
403maps_api_key_invalidThe key is invalid or inactive.
422invalid_inputInput does not match the bounded contract.
429rate_limit_exceededThe current request limit was reached.
503maps_unavailableThe operation is disabled or its dependency is unavailable.