The same analysis as an on-prem container in your network
The API is the same analysis engine as in the desktop program, packaged as a container image that you run on-prem, meaning on a server of your own or in your cluster. Your systems send the card files to the container over HTTP and get the analysis back as JSON. The card data is processed in memory, never written to disk and never logged. The container makes no outbound connections, so none of it is transferred to us.
Who it is for
It is meant for fleets with their own TMS or ERP that want to process the analysis there. Telematics providers that collect card data anyway can have it checked directly, and service providers that analyze driver cards for many customers save themselves the detour through a desktop program.
How it works
You receive an activation code from us, exchange it once for a license token and start the container with it on a server in your network. Your systems then hand over the .ddd files over HTTP, one at a time or bundled per driver, and the container merges them exactly the way the desktop program does. Back comes a JSON with the shifts, the violations in both views, the forecasts and the periods that are not assessable, which you can process straight away.
For a whole fleet at once there is a batch endpoint. You upload all files in one request, the container sorts them by driver card itself and works through them in the background. Progress and the per-driver results are fetched through a job id.
Same engine
The desktop program and the API run the same code. What you see in the program, the API delivers as data, with the same results.
Two views
Every analysis carries both violation lists. The reference view is calibrated against the output of established software, the strict view derives each finding from the regulation text and cites the article. A separate endpoint returns the catalogue of all 24 rules with their citations.
Documents
The report from the desktop program is available through the API as well, as HTML, as CSV tables in a zip or as PDF. It comes with a provenance record that states which uploaded file backs which day.
Authenticity
The signatures and certificates of a driver card or a vehicle-unit download can be verified through the API. The answer says what was verified and what cannot be checked at all for older card generations.
Vehicle unit
The download file of the vehicle can be read as well. You see which cards were inserted in a period and which drivers drove with them.
OpenAPI
The interface is described as an OpenAPI 3.1 specification that the container serves itself. The documentation at docs.scernetta.com is generated directly from it and therefore cannot drift from the state of the API.
Licensing
The API is licensed per driver or per vehicle and billed annually. The container verifies the license token offline and never needs to reach us for that. When the license expires it keeps working for 14 days, so a late renewal never stops a fleet. We quote the price on request, because it depends on the size of the fleet.
On-prem
The card data is processed on-prem, inside your network. The only thing that ever leaves the container is a set of counters without names and without card data, and you send those yourself.
The documentation of the interface lives at docs.scernetta.com and is generated from the OpenAPI file. It opens with a guide to getting started, licensing and error handling and describes every endpoint with its parameters.Go to the documentation
If you want to use the API, tell us which systems you would like to connect and how many drivers or vehicles are involved. We will get back to you with access.