entopizo API Reference
GPS tracking for vehicles & fleets

Introduction

The entopizo API is a conventional REST API. Every request (except login) is authenticated with a user_api_hash token passed as a parameter. There are no SDKs to install — any HTTP client works.

Quickstart: your first request in 60 seconds

curl -X POST "https://go.entopizo.gr/api/login" \
  -d "email=user@example.com" \
  -d "password=••••••••"

# → { "status": 1, "user_api_hash": "$2y$10$..." }

curl "https://go.entopizo.gr/api/get_devices?user_api_hash=HASH&lang=en"

Authentication

Authentication uses a static per-user token, the user_api_hash. It is issued once via login and then passed as a parameter on every call. Bearer headers are not used. The token does not expire unless the account password changes.

curl -X POST "https://go.entopizo.gr/api/login" \
  -d "email=user@example.com" \
  -d "password=••••••••"

{
  "status": 1,
  "user_api_hash": "$2y$10$EXAMPLEHASH..."
}

Conventions

Formats used consistently across the API:

Distance and capacity units (km/mi, litres/gallons) follow the account settings — see Account & Setup.

Devices

A device is a GPS tracker installed in a vehicle or asset. Device objects carry the latest known position, motion state and sensor values, so for "where is my fleet right now" questions a single call is enough.

curl "https://go.entopizo.gr/api/get_devices?user_api_hash=HASH&lang=en"

[
  {
    "id": 0,
    "title": "Ungrouped",
    "items": [
      {
        "id": 1042,
        "name": "Truck YZX-1234",
        "online": "online",
        "time": "05-07-2026 14:32:10",
        "speed": 54,
        "course": 118,
        "lat": 37.97552,
        "lng": 23.73481,
        "altitude": 92,
        "address": "132 Gr. Lampraki Ave, Korydallos",
        "protocol": "teltonika",
        "total_distance": 48211.7,
        "stop_duration": "0s",
        "sensors": [
          { "name": "Ignition", "value": "On" },
          { "name": "Battery", "value": "12.6V" }
        ],
        "tail": [
          { "lat": "37.97501", "lng": "23.73390" }
        ]
      }
    ]
  }
]

Other device endpoints

All accept user_api_hash.

Route History

curl "https://go.entopizo.gr/api/get_history?user_api_hash=HASH\
&device_id=1042&from_date=2026-07-04&from_time=00:00\
&to_date=2026-07-04&to_time=23:59"

{
  "distance_sum": "182.4 km",
  "top_speed": "96 kph",
  "items": [
    {
      "status": 1,
      "distance": 42.7,
      "time": "1h 05min",
      "items": [
        { "lat": 37.975, "lng": 23.734,
          "speed": 51, "time": "08:12:04" }
      ]
    },
    {
      "status": 3,
      "time": "38min",
      "location": "Warehouse, Aspropyrgos"
    }
  ]
}

Other history endpoints

Events

Events are occurrences recorded against a device: overspeeding, geofence entry/exit, power cut, towing, SOS and more. Events are generated only when a matching alert rule is active.

{
  "items": {
    "data": [
      {
        "id": 88211,
        "device_id": 1042,
        "type": "overspeed",
        "message": "Speed limit exceeded",
        "speed": 112,
        "latitude": 38.0142,
        "longitude": 23.6650,
        "address": "Athinon Ave, Athens",
        "time": "04-07-2026 16:44:31"
      }
    ],
    "current_page": 1,
    "last_page": 4
  }
}

Other event endpoints

Alert Rules

Alert rules define when events are generated and how the user is notified (push, email, SMS).

curl -X POST "https://go.entopizo.gr/api/add_alert" \
  -d "user_api_hash=HASH" \
  -d "name=Overspeed 100 km/h" \
  -d "type=overspeed" \
  -d "overspeed=100" \
  -d "devices[]=1042" \
  -d "devices[]=1043"

{ "status": 1 }

Other alert endpoints

Geofences & Routes

Geofences are named areas (polygons or circles) used for entry/exit alerts and reporting. Routes are predefined paths a vehicle is expected to follow.

curl -X POST "https://go.entopizo.gr/api/add_geofence" \
  -d "user_api_hash=HASH" \
  -d "name=Warehouse Aspropyrgos" \
  -d 'polygon=[{"lat":38.061,"lng":23.593},
              {"lat":38.062,"lng":23.601},
              {"lat":38.057,"lng":23.600}]'

{ "status": 1 }

Other geofence & route endpoints

Commands

Commands are messages sent to the tracker over GPRS or SMS — for example engine stop/resume on supported installations. Available command types depend on the device protocol.

curl -X POST "https://go.entopizo.gr/api/send_gprs_command" \
  -d "user_api_hash=HASH" \
  -d "device_id=1042" \
  -d "type=custom" \
  -d "data=setdigout 1"

{ "status": 1, "message": "Command sent" }

Other command endpoints

Reports

Generates reports — general, drives & stops, driver behaviour, fuel, overspeeding, geofence activity and more — in HTML, PDF or XLS, or schedules them for automatic delivery.

curl -X POST "https://go.entopizo.gr/api/generate_report" \
  -d "user_api_hash=HASH" \
  -d "title=June mileage" \
  -d "type=1" \
  -d "devices[]=1042" \
  -d "date_from=2026-06-01 00:00" \
  -d "date_to=2026-06-30 23:59" \
  -d "format=html"

{
  "status": 1,
  "url": "https://go.entopizo.gr/report/…"
}

Other report endpoints

Drivers

Drivers can be assigned to devices manually or identified automatically via RFID / iButton. Driver identity then appears in history, events and reports.

Sensors

Sensors translate raw protocol parameters into readable values: ignition, fuel level, temperature, door state, battery voltage and more. Sensor values appear inside get_devices responses.

Maintenance

Maintenance items (services) track recurring vehicle obligations — servicing, oil changes, vehicle inspection, insurance — by odometer, engine hours or calendar days, with expiration warnings.

Tasks

Tasks represent jobs or deliveries assigned to a vehicle, with pickup/delivery details, priority and status tracking.

Account & Setup

Plugin-dependent endpoints

The following endpoints are available only when the corresponding platform plugin is enabled on the server. If a call returns HTTP 404 or an HTML error page, the plugin is not active for your account.

Errors & limits

Successful calls return HTTP 200 with "status": 1. Failures return "status": 0 in the body, or an HTTP error code.

Error example

{
  "status": 0,
  "message": "Wrong email or password"
}

Guidance for AI agents

This section addresses LLM-based agents (Claude, ChatGPT, custom assistants) consuming the API through MCP servers or function calling.

Recommended flow

1. Call get_devices once to map vehicle names to device_id. 2. Use the device_id for history, events, sensors or commands. 3. For current-position questions, get_devices data is sufficient — no second call needed.

Token efficiency

Responses from get_devices and get_history are large. Keep only the fields id, name, online, time, speed, lat, lng, address, and in history the per-segment aggregates (distance, time, status, location) instead of raw GPS points.

Safety & consent

Never store credentials in prompts. Calls to send_gprs_command or any destroy endpoint require explicit user confirmation. Location data is personal data under GDPR — do not expose it to third parties.