Documentation

Start here

Find your role. Each role has one first page and a short list of next pages.

• Fleet manager or dispatcherWatch the fleet, trips, events, and reports.Read the user guide →
• DriverSee your vehicle, your trips, and your events in the mobile app.Read the user guide →
• AdministratorManage users, API keys, webhooks, share links, and ERP connections.Read the ERP overview →
• DeveloperRead fleet data into an ERP, a TMS, or a data warehouse.Go to the quick start →

User documentation

For fleet managers, dispatchers, drivers, and administrators. These pages tell you how to use the dashboard and the mobile apps.

• Guidelines — the user guide: what the system does, sign-in and roles, the fleet map, all dashboard pages, photos and video, mobile apps, known limits, glossary.
• FAQ: short answers to single questions.
• Features: what is available now and what is on the roadmap.
• Connect your own GPS device: use the GPS trackers you already have with Filodos — what works, what we need from you, and the steps.
• Customer share links (managers and administrators): send a customer a read-only, expiring link to one trip or one vehicle day, and revoke it.
• API keys setup (administrators): create scoped read-only keys for your ERP or data warehouse, and revoke them.
• Webhooks setup (administrators): subscribe your systems to trip end, zone arrivals and departures, critical alarms, and the daily report.
• ERP integration overview: what data goes between Filodos and your ERP, and the setup path for each system.
• Connect SoftOne or Entersoft (administrators): add an ENTERSOFTONE ERP connection, test the login, and pause or delete it.
• Connect SAP Business One (administrators): add a Service Layer connection, read customers or warehouses, and write activities into SAP.
• Connect SAP S/4HANA Cloud (administrators): add an OAuth2 OData connection, read business partners, and write notes into S/4HANA.
• Import sites from a CSV file (administrators): import customer and depot sites from any ERP with a CSV file, no login needed.
• ERP sites and zones (managers and administrators): turn ERP customers and depots into zones, sync them, and set the location of sites without coordinates.
• Visit notes in the ERP (managers and administrators): write one note into the ERP each time a vehicle visits an ERP site.

Roles

Role	What the role sees and does
Admin	All data of the organization. Manages users, vehicles, API keys, webhooks, share links, and ERP connections.
Manager	All data of the organization. Creates and revokes customer share links. Edits the workflows of ERP connections. Cannot manage users, keys, webhooks, or the ERP login.
Driver	Only the linked vehicle and the driver's own trips and events.

Each login belongs to one organization. A login never sees the data of a different organization.

Developer documentation

For the people who connect Filodos to an ERP, a TMS, or a data warehouse. Each page covers one function: the request, the answer, the error codes, and examples that you can copy.

Concepts

• API overview: base URLs, versioned paths, the two credentials, organization scoping, timestamps, and error codes.
• Authentication: POST /auth/login and GET /auth/me.

Read data

• Fleet: GET /devices (versioned: /v1/fleet).
• Trips: GET /trips and GET /driver/trips.
• Events: GET /events and GET /driver/events.
• Positions: GET /v1/positions.
• Zone visits: GET /v1/visits.
• Reports: GET /v1/reports/daily, /weekly, and /history, with the cost proxy and its rate parameters.
• BI analytics: flat fleet-wide tables for Power BI, Excel, and Looker Studio. One page for each feed, with an example: daily metrics, trips, events, zone visits, and vehicles.
• Telemetry: GET /telemetry and GET /telemetry/samples.
• Assignments: GET /assignments and GET /driver/assignments.

Manage access and pushes

• API key management: GET, POST, and DELETE /api-keys.
• Webhook management: GET, POST, and DELETE /webhooks, plus POST /webhooks/{id}/test, the deliveries list, and replay.
• ERP connections: /erp/connections with the workflow, test, sync, sites, site locations, and visit notes of ENTERSOFTONE connectors. Sign-in only.
• Webhook events: the event catalog, delivery envelopes, signature verification, and a worked example.
• Testing your integration: how to test without a sandbox, the test ping, error diagnosis, and the go-live checklist.

Photo and clip endpoints stay internal for now. They are not part of this reference.

Developer quick start

Do these steps to read your first trips. You need an administrator login for step 1.

1. Sign in to the dashboard as an administrator. Go to Organization → API keys. Create a key with the scopes devices:read and trips:read. See API keys setup.
2. Copy the key value. It starts with filodos_. The dashboard shows it one time only.
3. Read the fleet list. Find the id of a vehicle.

   curl "https://filodos.gr/filodos-dashboard/api/scoring/v1/fleet" \
     -H "Authorization: Bearer filodos_…"

4. Read the trips of that vehicle.

   curl "https://filodos.gr/filodos-dashboard/api/scoring/v1/trips?device_id=12" \
     -H "Authorization: Bearer filodos_…"

5. Optional: subscribe to trip.ended so that Filodos pushes each new trip to you. Then you do not need to poll. See Webhooks setup.
6. Before you go live, do the checks in Testing your integration.

Keep the key secret. Store it on your server only. Do not put it in a browser page, a mobile app, or a source repository. If a key leaks, revoke it and create a new key.

Endpoint map

All paths start with the base URL https://filodos.gr/filodos-dashboard/api/scoring. Use the /v1/ paths for new feeds. These paths do not change.

Key scopes

An API key carries one or more scopes. Each scope opens one read family. A call outside the key's scopes gets 403. A key can never write.

Scope	Opens
devices:read	The fleet list.
trips:read	Trips of a vehicle and trips of a driver.
events:read	Driving events, zone events, and zone visits.
positions:read	Stored GPS fixes of a vehicle.
reports:read	Daily, weekly, and history summaries, with the cost proxy.
telemetry:read	Black-box burst summaries and their per-second samples.
drivers:read	Driver lists, driver rollups, and assignment history.
scores:read	Stored vehicle score records.

Give each feed only the scopes that it calls. A mileage feed needs devices:read and trips:read. A delivery-confirmation feed also needs events:read.

Webhook events

A webhook sends a signed POST to your HTTPS address when an event occurs. Use webhooks instead of fast polls.

Event	Filodos sends it when
trip.ended	A vehicle completes a trip.
geofence.enter	A vehicle goes into a zone.
geofence.exit	A vehicle goes out of a zone.
alarm.critical	A device reports SOS, a collision, or a rollover.
report.daily	The nightly daily-report e-mails are sent.
webhook.test	An administrator sends a test ping. You cannot subscribe to it.

Each delivery carries an X-Filodos-Signature header and an X-Filodos-Delivery id. Verify the signature before you use the data. If your server does not answer, or answers 429 or 5xx, Filodos tries again after 1 minute, 5 minutes, 30 minutes, 2 hours, and 12 hours. An administrator can replay any stored delivery. See Webhook events.

Conventions

These rules apply to all endpoints. The API overview gives the full detail.

Format

All requests and answers are JSON. Lists sort newest first, unless the page tells you differently.

Credentials

Put a sign-in token or an API key in the Authorization: Bearer header. Use a key for server-to-server feeds.

Organization scoping

Each read shows only the data of the credential's organization. An id from a different organization gets 404.

Timestamps

ISO-8601 with a UTC offset. Day and week parameters use fleet-local dates (Europe/Athens).

Errors

400 bad parameters, 401 bad credential, 403 no permission or scope, 404 unknown id, 422 invalid input, 429 too many requests, 502/503 an upstream failure.

Stability

/v1/ paths do not change. Paths without a version can change.

Recent changes

• 1.0.64: the dashboard and the iOS and Android apps are in English and in Greek. See Sign in and roles — Language.
• 1.0.26: site import from a CSV file for any ERP, and one Export CSV button on the Trips, Events, Drivers, and Daily report pages. See Import sites from a CSV file.
• 1.0.23: the SAP S/4HANA Cloud connector through the OData API with OAuth2. Business partners become zones, and a visit can make a note in S/4HANA. See Connect SAP S/4HANA Cloud.
• 1.0.20: the SAP Business One connector through the Service Layer. Customers or warehouses become zones, and a visit can make an activity in SAP. See Connect SAP Business One.
• 1.0.12 – 1.0.15: ENTERSOFTONE ERP connectors for SoftOne and Entersoft. ERP sites become zones, and a visit can write a note back into the ERP. The Organization → ERP page splits the work: administrators own the connection, managers edit the workflow. See Connect SoftOne or Entersoft and ERP connections. The four ERP pages are also in Greek.
• 1.0.11: the BI analytics pages are now also in Greek. See Αναλύσεις BI.
• 1.0.10: one documentation page for each BI feed, with an example request, answer, and Excel sheet. See BI analytics.
• 1.0.9: four more fleet-wide BI feeds: trips, events, zone visits, and vehicles. The daily feed now has vehicle and driver names. One Excel query reads all feeds. See BI analytics.
• 1.0.8: the own-device service. Filodos connects the GPS trackers that you already have to the dashboard. See Connect your own GPS device.
• 1.0.6: the flat, paginated daily analytics feed for Power BI, Excel, and Looker Studio REST connectors. See BI analytics.
• 1.0.2 – 1.0.3: customer share links. A manager or an administrator sends a customer a read-only link to one trip or one vehicle day. The link expires after 1 to 30 days. The customer does not need an account. See Customer share links.
• 1.0.1: the cost proxy (idle, harsh-event, and night-driving costs) is on the daily and weekly reports. Optional rate parameters change the rates. See Reports.
• 1.0.0: the complete /v1/ read API, with positions, zone visits, and reports.
• 0.2.104: webhook retries, the deliveries list, and replay.