API Changelog

From Idrive
Jump to navigation Jump to search

Version 1.3.4

Story

  • [GA-72] - Integrate vehicle heading in event unified endpoint - add altitude (/event/{uid}/unified)
  • [GA-95] - Redesign live telematics

Version 1.3.3

Bug

  • [GA-73] - Events cannot be played on https addresses (the links from S3 are not correct)

Version 1.3.2

Story

  • [GA-71] - Extend log mechanism to catch all errors

Version 1.3.1

Bug

  • [GA-63] - Events uploading via CC (fw v. 25.4) that have incorrect date (year 1970 or 2028) have the same record date

Story

  • [GA-39] - Re-write Global Notifications react module to use session for authentication insead of hard coded api keys
  • [GA-60] - Add 10 G-forces points per second on vehicle g-forces API call (/event/{uid}/gforces)
  • [GA-61] - Integrate in API call event's length preview (/event/{uid}) - from fw v. 40.7
  • [GA-62] - Correct record_date_local to GMT in events call (/event/{uid})
  • [GA-64] - Add "speed" for each coordinate point (/event/{uid}/coordinates)
  • [GA-69] - Create a logging mechanism for changing settings - all API calls

Version 1.3.0

Story

  • [GA-53] - Add last known position / status / speed / altitude info for Vehicle API Client request (/vehicle/{uid})
  • [GA-56] - Implement new endpoint on vehicle for CarTrack to provide raw GPS data (/vehicle/{uid}/gps-data)
  • [GA-57] - Implement a method to show route data for clients
  • [GA-59] - Create a new endpoint to expose coordinates, gforce and media with Event data (/event/{uid}/unified)

Version 1.2

Story

  • [GA-52] - Create a mechanism for dynamic endpoints

Version 1.1.7

Bug

  • [GA-47] - Speed events are not showing the correct record_date (is not taking into consideration DST)

Story

  • [GA-48] - Handle new events received with no vehicle assigned
  • [GA-49] - When adding event, also check for assigned drivers
  • [GA-51] - Update events for these columns: location_id_download, vehicle_id, person_id, event_status

Version 1.1

Bug

  • [GA-41] - Fetching events from documentation interface does not work

Story

  • [GA-31] - Study Amazon Notification Service (SNS)
  • [GA-33] - Create Lambda functions for push notification
  • [GA-40] - Add CMS entries for Version Release Notification
  • [GA-42] - Extend vehicle api response to include last position and last time
  • [GA-43] - A vehicle name needs to be unique only within company
  • [GA-44] - Create new event endpoint for CVR feature
  • [GA-46] - Move notifications module from Node to API to integrate it with the new event flow

Version 1.0

Epic

  • [GA-2] - Events
  • [GA-3] - Personnel
  • [GA-4] - Companies
  • [GA-5] - Vehicles
  • [GA-12] - API Documentation

Story

  • [GA-6] - Api http/https server
  • [GA-7] - Api list events/events
  • [GA-8] - Api cluster server
  • [GA-9] - Api db-manager
  • [GA-10] - Api list vehicles/vehicle
  • [GA-11] - Api documentation for list events and vehicles
  • [GA-14] - Api authentication
  • [GA-15] - Api list users/users
  • [GA-16] - Api list companies/company
  • [GA-18] - Use basic http authentication for the documentation page (help)
  • [GA-20] - Create a naming layer to standardize data output members
  • [GA-21] - Evaluate all api calls to provide common ground data set for all clients
  • [GA-22] - Global Alerts via API
  • [GA-25] - Create Admin documentation for Global API
  • [GA-26] - Create abstract call management for mySQL bridge
  • [GA-28] - Move API calls to live database
  • [GA-29] - Dynamo DB API calls
  • [GA-30] - Make API calls from within documentation