Use the Geotab MyGeotab SDK to subscribe to exceptions and retrieve driver trip history via GetFeed

Steps

1. Authenticate to the MyGeotab API using the Authenticate method with your database name, username, and API key to receive a session credentials object
2. Use the Get method with the ExceptionEvent entity type to retrieve historical exception records for a date range, filtered by device or driver as required
3. Switch to the GetFeed method for ongoing exception monitoring: GetFeed returns a fromVersion token on the first call which you pass on subsequent calls to receive only new records since the last poll
4. Similarly use GetFeed with the Trip entity type to efficiently stream new completed trip records, capturing distance, start/end times, driver, and device fields
5. Handle the version token carefully: store it persistently so that a service restart resumes polling from where it left off rather than reprocessing the entire history
6. Respect MyGeotab API best practices including limiting result set sizes, avoiding broad date ranges on Get calls, and using server-side filtering rather than client-side filtering for performance