{"id":13868,"date":"2025-05-07T15:27:19","date_gmt":"2025-05-07T12:27:19","guid":{"rendered":"https:\/\/www.fmsdocumentation.com\/api-per-lanalisi-dei-tempi-di-guida\/"},"modified":"2025-05-08T09:35:05","modified_gmt":"2025-05-08T06:35:05","slug":"api-per-lanalisi-dei-tempi-di-guida","status":"publish","type":"page","link":"https:\/\/www.fmsdocumentation.com\/it\/api\/api-per-lanalisi-dei-tempi-di-guida\/","title":{"rendered":"API per l’analisi dei tempi di guida"},"content":{"rendered":"\n

Lo scopo principale dell’API Driver Time Analysis \u00e8 quello di produrre i dati relativi ai tempi di lavoro e di riposo dei conducenti per uno specifico autista. I dati forniti si basano sulla funzionalit\u00e0 di analisi del tempo<\/a>. <\/p>\n\n

Esempio di richiesta API per un driver specifico:<\/p>\n\n

GET \/drivers\/{driverId}\/current-time-analysis?version=1&api_key=<...>HOST:api.fm-track.comContent-Type:application\/json;charset=UTF-8<\/p>\n\n

Affinch\u00e9 questa API funzioni, i seguenti parametri sono obbligatori:<\/p>\n\n\n\n\n\t\n\n\t\n\t\n\t
Parameter<\/th>Type<\/th>Description<\/th>\n<\/tr>\n<\/thead>\n
driverId<\/td>String<\/td>Driver identifier (This ID can be acquired by sending a request to the Drivers API)<\/td>\n<\/tr>\n
version<\/td>String<\/td>Version of the API, currently only version=1 is available<\/td>\n<\/tr>\n
api_key<\/td>String<\/td>User identification key<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n\n

Di seguito \u00e8 riportato un esempio di risposta:<\/p>\n\n

{\n  \"type\": \"PRIMARY\",\n  \"calculated_until\": \"2018-05-31T14:47:47.000Z\",\n  \"state\": {\n    \"activity\": \"UNKNOWN\",\n    \"started_at\": \"2018-05-24T11:10:00.000Z\",\n    \"duration\": 617820\n  }, \n  \"current_day\": {\n    \"driving_status\": \"SINGLE\",\n    \"driving\": {\n      \"regular\": {\n        \"duration\": 0,\n        \"duration_limit\": 32400\n\t\t},\n      \"extra\": {\n        \"duration\": 0,\n        \"duration_limit\": 3600\n\t\t}\n    },\n    \"working\": {\n      \"duration\": 0\n    },\n    \"resting\": {\n      \"rest_in_progress\": false,\n      \"next_rest\": null\n    }\n  },\n  \"current_week\": {\n    \"driving\": {\n      \"duration\": 0,\n      \"duration_limit\": 201600,\n      \"extended_daily_driving_periods\": {\n        \"used\": 0,\n        \"usage_limit\": 2\n      }\n    },\n    \"working\": {\n      \"duration\": 0\n    },\n    \"resting\": {\n      \"rest_in_progress\": false,\n      \"next_rest\": null,\n      \"reduced_daily_rests\": {\n        \"used\":0,\n        \"usage_limit\": 3\n      }\n    }\n  },\n  \"previous_week\": {\n    \"driving\": {\n      \"duration\": 0,\n      \"duration_limit\": 201600\n    },\n    \"resting\": {\n      \"duration\": 0\n      }\n  },\n  \"infringements\": {\n  \"daily_driving_limit_exceeded\": {\n    \"duration\": 0\n  },\n  \t\"weekly_driving_limit_exceeded\": {\n  \t\t\"duration\": 0\n    }\n  },\n  \"data_gap_duration\": {\n\t\"duration\": 0\n  }\n }<\/pre><\/div>\n
Se un parametro o la chiave API_ non sono stati inseriti correttamente, il sistema risponder\u00e0 con un codice di errore; tutti i possibili codici di errore sono descritti nella sezione API<\/a>.<\/p>\n
Tutti i campi di risposta che possono essere ricevuti con ogni tipo di parametro sono descritti nella tabella successiva:<\/p>\n\n\n\n\n\t\n\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t
Name<\/th>Type<\/th>Description<\/th>Units<\/th>\n<\/tr>\n<\/thead>\n
type<\/td>String<\/td>Indicates whether the driver is primary or secondary, that is, whether the driver card is inserted into the first or second card slot in the tachograph<\/td>Text<\/td>\n<\/tr>\n
calculated_until<\/td>Date<\/td>Date and time when the request was made
\nFormat: \"yyyy-mm-ddThh:mm:ss.sssZ\"
\n<\/td>		According to ISO8601<\/td>\n<\/tr>\n
state<\/td>Array<\/td>Contains all driver state parameters<\/td><\/td>\n<\/tr>\n
activity<\/td>String<\/td>The driver state when the request was made<\/td>Text<\/td>\n<\/tr>\n
started_at<\/td>Date<\/td>Date and time when the driver entered a state
\nFormat: \"yyyy-mm-ddThh:mm:ss.sssZ\"
\n<\/td>		According to ISO8601<\/td>\n<\/tr>\n
duration<\/td>Integer<\/td>Total time the driver was in a state<\/td>Seconds<\/td>\n<\/tr>\n
current_day<\/td>Array<\/td>Contains all current day parameters<\/td><\/td>\n<\/tr>\n
driving_status<\/td>String<\/td>Indicates whether there is a single driver or a crew<\/td>Text<\/td>\n<\/tr>\n
driving<\/td>Array<\/td>Contains all driving parameters<\/td><\/td>\n<\/tr>\n
regular<\/td>Array<\/td>Contains all regular driving parameters<\/td><\/td>\n<\/tr>\n
duration<\/td>Integer<\/td>Total regular driving duration<\/td>Seconds<\/td>\n<\/tr>\n
duration_limit<\/td>Integer<\/td>The maximum allowed regular driving duration<\/td>Seconds<\/td>\n<\/tr>\n
extra<\/td>Array<\/td>Contains extra driving parameters<\/td><\/td>\n<\/tr>\n
duration<\/td>Integer<\/td>Total extra driving duration<\/td>Seconds<\/td>\n<\/tr>\n
duration_limit<\/td>Integer<\/td>The maximum allowed extra driving duration<\/td>Seconds<\/td>\n<\/tr>\n
working<\/td>Array<\/td>Contains all daily working parameters<\/td><\/td>\n<\/tr>\n
duration<\/td>Integer<\/td>Total daily working duration<\/td>Seconds<\/td>\n<\/tr>\n
resting<\/td>Array<\/td>Contains all daily rest parameters<\/td><\/td>\n<\/tr>\n
rest_in_progress<\/td>Boolean<\/td>Indicates if the driver was resting when the request was made<\/td>True - False<\/td>\n<\/tr>\n
next_rest<\/td>Date<\/td>Date and time of the next daily rest
\nFormat: \"yyyy-mm-ddThh:mm:ss.sssZ\"
\n<\/td>		According to ISO8601<\/td>\n<\/tr>\n
current_week<\/td>Array<\/td>Contains all current week parameters<\/td><\/td>\n<\/tr>\n
driving<\/td>Array<\/td>Contains all driving parameters<\/td><\/td>\n<\/tr>\n
duration<\/td>Integer<\/td>Total weekly driving duration<\/td>Seconds<\/td>\n<\/tr>\n
duration_limit<\/td>Integer<\/td>The maximum allowed weekly driving duration<\/td>Seconds<\/td>\n<\/tr>\n
extended_daily_driving_periods<\/td>Array<\/td>Contains all extended daily driving period parameters<\/td><\/td>\n<\/tr>\n
used<\/td>Integer<\/td>The amount of used extended driving periods<\/td>Number<\/td>\n<\/tr>\n
usage_limit<\/td>Integer<\/td>The maximum amount of extended driving periods<\/td>Number<\/td>\n<\/tr>\n
working<\/td>Array<\/td>Contains all weekly working parameters<\/td><\/td>\n<\/tr>\n
duration<\/td>Integer<\/td>Total weekly working duration<\/td>Seconds<\/td>\n<\/tr>\n
resting<\/td>Array<\/td>Contains all weekly rest parameters<\/td><\/td>\n<\/tr>\n
rest_in_progress<\/td>Boolean<\/td>Indicates if the driver was resting when the request was made<\/td>True - False<\/td>\n<\/tr>\n
next_rest<\/td>Date<\/td>Date and time of the next weekly rest
\nFormat: \"yyyy-mm-ddThh:mm:ss.sssZ\"
\n<\/td>		According to ISO8601<\/td>\n<\/tr>\n
reduced_daily_rests<\/td>Array<\/td>Contains all reduced daily rest parameters<\/td><\/td>\n<\/tr>\n
used<\/td>Integer<\/td>The amount of used reduced daily rest periods<\/td>Number<\/td>\n<\/tr>\n
usage_limit<\/td>Integer<\/td>The maximum amount of reduced daily rest periods<\/td>Number<\/td>\n<\/tr>\n
previous_week<\/td>Array<\/td>Contains all previous week parameters <\/td><\/td>\n<\/tr>\n
driving<\/td>Array<\/td>Contains all driving parameters<\/td><\/td>\n<\/tr>\n
duration<\/td>Integer<\/td>Total driving duration the previous week<\/td>Seconds<\/td>\n<\/tr>\n
duration_limit<\/td>Integer<\/td>The maximum allowed weekly driving duration<\/td>Seconds<\/td>\n<\/tr>\n
resting<\/td>Array<\/td>Contains all resting parameters for the previous week<\/td><\/td>\n<\/tr>\n
duration<\/td>Integer<\/td>Total resting duration the previous week<\/td>Seconds<\/td>\n<\/tr>\n
infringements<\/td>Array<\/td>Contains all infringement parameters<\/td><\/td>\n<\/tr>\n
daily_driving_limit_exceeded<\/td>Array<\/td>Contains all excessive daily driving parameters<\/td><\/td>\n<\/tr>\n
duration<\/td>Integer<\/td>Total driving duration driven over the daily driving limit<\/td>Seconds<\/td>\n<\/tr>\n
weekly_driving_limit_exceeded<\/td>Array<\/td>Contains all excessive weekly driving parameters<\/td><\/td>\n<\/tr>\n
duration<\/td>Integer<\/td>Total driving duration driven over the weekly driving limit<\/td>Seconds<\/td>\n<\/tr>\n
data_gap_duration<\/td>Array<\/td>Contains all data gap duration parameters<\/td><\/td>\n<\/tr>\n
duration<\/td>Integer<\/td>Total duration for which no data was received<\/td>Seconds<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n
Gli endpoint API, i parametri di richiesta e le risposte possono essere visualizzati in anteprima in “Swagger” attraverso questo link: https:\/\/api.fm-track.com<\/a><\/p>\n
\n
\u2039   <\/span> API Viaggi <\/a><\/div> 
API del driver   \u203a <\/span> <\/a><\/div><\/p>\n","protected":false},"excerpt":{"rendered":"
Lo scopo principale dell’API Driver Time Analysis \u00e8 quello di produrre i dati relativi ai tempi di lavoro e di riposo dei conducenti per uno specifico autista. I dati forniti si basano sulla funzionalit\u00e0 di analisi del tempo. Esempio di richiesta API per un driver specifico: GET \/drivers\/{driverId}\/current-time-analysis?version=1&api_key=HOST:api.fm-track.comContent-Type:application\/json;charset=UTF-8 Affinch\u00e9 questa API funzioni, i seguenti parametri … Continua a leggere API per l’analisi dei tempi di guida<\/span><\/a><\/p>\n","protected":false},"author":5,"featured_media":0,"parent":14003,"menu_order":7,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-13868","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.fmsdocumentation.com\/it\/wp-json\/wp\/v2\/pages\/13868","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.fmsdocumentation.com\/it\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.fmsdocumentation.com\/it\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.fmsdocumentation.com\/it\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/www.fmsdocumentation.com\/it\/wp-json\/wp\/v2\/comments?post=13868"}],"version-history":[{"count":2,"href":"https:\/\/www.fmsdocumentation.com\/it\/wp-json\/wp\/v2\/pages\/13868\/revisions"}],"predecessor-version":[{"id":14015,"href":"https:\/\/www.fmsdocumentation.com\/it\/wp-json\/wp\/v2\/pages\/13868\/revisions\/14015"}],"up":[{"embeddable":true,"href":"https:\/\/www.fmsdocumentation.com\/it\/wp-json\/wp\/v2\/pages\/14003"}],"wp:attachment":[{"href":"https:\/\/www.fmsdocumentation.com\/it\/wp-json\/wp\/v2\/media?parent=13868"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}