This is release 1.0 of the Open Telematics API. A project to enable business resiliency for motor freight carriers with tight integrations into Telematics Service Providers (TSPs).
The nmfta-opentelematics-api-v1.0.zip attached to this github release contains:
apiary.apib-- API Blueprint specificationotapi.html-- standalone documentation rendering of the aboveOpen Telematics Supported Use Cases Questionnaire.xlsx-- a questionnaire for use by motor freight carriers in assessing the degree to which a TSP provides OTAPI support
This release is also published at apimatic.io/.../nmfta-opentelematics-api/v/1_0 which provides:
- Exportable API specifications in multiple formats including: Open API 3.0, RAML 1.0, and Swagger 2.0
- Downloadable (client) SDKs in .NET, Java, and Python
Contributors
This release is the result of a group effort benefiting from collaboration across the heavy vehicle industry. Though some of our contributors wish to remain anonymous, we are deeply grateful to everyone who has given
their time and energy to make this a reality.
| Fleet Managers | Telematics Providers | Independents |
|---|---|---|
| Bill Brown, SEFL | Samsara Networks, Inc. | Altaz Valani, Security Compass |
| Penske Truck Leasing | Geotab | Andrew Smith, ISE Inc. |
| Old Dominion Freight Lines | Omnitracs | Dr. Jeremy Daily, UTulsa |
| Derek Held, Zonar Systems |
