Changelog
Log In
Back to All

Motive Public API Changelog (2024 & earlier)

November 5th, 2024 by Abhay Anumula

API Changelog - 23 Dec 2024

👍

ADDED

Two new endpoints have been added to the documentation

  • Name: Fetch the camera connection events
  • Method: GET
  • URL: https://api.gomotive.com/v1/camera_connections
  • Purpose: This endpoint provides information about camera connection events. It details when a camera came online or went offline, which driver and vehicle were associated, the camera type, and other status information. This data is useful for monitoring camera uptime, diagnosing potential connectivity issues, and ensuring compliance or safety standards are maintained.
  • Name: View all the vehicle gateway disconnect events
  • Method: GET
  • URL: https://api.gomotive.com/v1/eld_disconnects
  • Purpose: This endpoint provides information about Vehicle Gateway disconnect events. It details when a Vehicle Gateway went offline, where the disconnect occurred, which driver and vehicle were involved, and when/if it reconnected. This information can be used for auditing, ensuring Hours of Service (HOS) compliance, and investigating potential connectivity issues.

API Changelog - 18 Dec 2024

📘

UPDATED

Geofence endpoints now support adding or updating the physical address of the geofence

❗️

NOTE

Ensure the character limit for the physical address that you enter is within 200 characters.

API Changelog - 17 Dec 2024

👍

ADDED

New endpoint for identifying a company

  • Name: Identify a company using its access token
  • Method: GET
  • URL: https://api.gomotive.com/v1/companies
  • Purpose: The purpose of this endpoint is to identify a company, by using an access token. To use the access token, you must first generate one.

📘

UPDATED

New query parameter added to the Fetch the documents for a specified time range endpoint

  • Name: v2/documents
  • Method: GET
  • Updates: New Query parameter added to GET/v2/documents endpoint: We have now added a new query parameter "updated_at", that will allow companies to fetch the documents that have been updated at a later point of time.

API Changelog - 2 Dec 2024

📘

UPDATED

Upload vehicles and driver qualification documents using the v2/documents endpoint

API Changelog - 1 Oct 2024

📘

UPDATED

Made the following changes to the vehicles API endpoints

  • Name: v1/vehicles
  • Method: POST
  • Updates: Added the following parameters to the request body. These parameters will also appear in the response of the endpoint:

driver_facing_camera

incab_audio_recording

  • Name: v1/vehicles
  • Method: PUT
  • Updates: Added the following parameters to the request body. These parameters will also appear in the response of the endpoint:

driver_facing_camera

incab_audio_recording

❗️

NOTE

Apart from the above endpoints, these two parameters will also appear in the response of GET/v1/vehicles, GET/v1/vehicles/{ID}.

API Changelog - 17 Sep 2024

📘

UPDATED

Made the following changes to the users API endpoints

  • Name: v1/user
  • Method: POST
  • Updates: Validation added for time_tracking_mode. This parameter is now compatible with the values of eld_mode. Refer to the endpoint documentation for more info (link).
  • Name: v1/user:id
  • Method: PUT
  • Updates: Validation added for time_tracking_mode. This parameter is now compatible with the values of eld_mode. Refer to the endpoint documentation for more info (link).

API Changelog - 17 Apr 2024

👍

ADDED

New API for fetching the vehicle locations added.

  • Name: Fetch the vehicle locations of an organisation.
  • Method: GET
  • URL: https:api.gomotive.com/v3/vehicle_locations
  • Purpose: Allows you to fetch the locations of all the vehicles of your organisation.

📘

UPDATED

Made the following changes to the Create Vehicles API

  • Name: Create Vehicles
  • Method: PUT
  • Updates: Added the parameter group_ids. This has been done to add the vehicle in a particular group of an organisation.

API Changelog - 29 Nov 2022

👍

ADDED

Made the following change to the Company Webhooks API

  • Name: Overview
  • Purpose: The overview section has been added to the Company Webhooks API.

API Changelog - 06 Jan 2022

👍

ADDED

Made the following parameters to the IFTA trips API

  • Name: v1/ifta/trips
  • Method: GET
  • URL: https://api.gomotive.com/v1/ifta/trips
  • Purpose: The response of this endpoint will now contain the following parameters:
    • calibrated_start_odometer
    • calibrated_end_odometer

API Changelog - 27 Dec 2021

👍

ADDED

Added the following APIs to the Motive Public Documentation

  • Name: v2/dispatches
  • Method: GET
  • URL: https://api.gomotive.com/v2/dispatches
  • Purpose: Use this API to fetch a list of all the dispatches with additional info such as the shipper stop and the consignee stop.
    The version 2 of the Dispatches API has now been added. The main difference between v1, and v2 being the ability to add a shipper stop and a consignee stop along with an additional stop. v1 would only allow you to add an additional stop, whereas the v2, will give you more flexibility in terms of your stops while on the way to your destination.
  • Name: v2/dispatches
  • Method: POST
  • URL: https://api.gomotive.com/v2/dispatches
  • Purpose: Use this API to create a dispatch with additional info such as the shipper stop and the consignee stop..
    The version 2 of the Dispatches API has now been added. The main difference between v1, and v2 being the ability to add a shipper stop and a consignee stop along with an additional stop. v1 would only allow you to add an additional stop, whereas the v2, will give you more flexibility in terms of your stops while on the way to your destination.
  • Name: v2/dispatches
  • Method: PUT
  • URL: https://api.gomotive.com/v2/dispatches
  • Purpose: Use this API to edit a l dispatch with additional info such as the shipper stop and the consignee stop.
    The version 2 of the Dispatches API has now been added. The main difference between v1, and v2 being the ability to add a shipper stop and a consignee stop along with an additional stop. v1 would only allow you to add an additional stop, whereas the v2, will give you more flexibility in terms of your stops while on the way to your destination.

API Changelog - 2 Sep 2021

👍

ADDED

The following APIs were added to the Vehicle Locations endpoint

  • Name: v2/vehicle_locations
  • Method: GET
  • URL: https://api.gomotive.com/v2/vehicle_locations
  • Purpose: Use this API to fetch a list of all the company vehicles, and their information such as assigned drivers, their location, fuel type, and etc.
  • Name: v3/vehicle_locations/:id
  • Method: GET
  • URL: <https://api.gomotive.com/v2/vehicle_locations>
  • Purpose: Use this API to fetch the details of a specific vehicle, and its information such as assigned driver, location, fuel type, and etc.

API Changelog - 2 Aug 2021

👍

ADDED

Added the following parameters to the Vehicle APIs

  • Name: All the vehicle APIs.
  • Description: We have now added the created_at, and updated_at timestamps for all the Vehicle endpoints. This critical info will allow the Fleet Managers to be aware of when the vehicle was created and also when it was updated. This will act as a log for all the updates made to the vehicle.

API Changelog - 4 May 2021

👍

ADDED

A new section titled HTTP version has been added to the Guides section.

API Changelog - 4 Jan 2021

👍

ADDED

Made the following endpoint

  • Name: v1/assets
  • Method: POST
  • URL: https://api.gomotive.com/v1/assets
  • Purpose: Use this API to create a new asset for your organisation. The asset can be a Reefer, a Lowboy, or even a Auto hauler. Any piece of equipment that is used along with your vehicle is called an asset.

API Changelog - 19 Oct 2020

📘

UPDATED

Made the following updates to all the Dispatch Locations APIs

  • Name: v1/dispatch_locations
  • Method:POST, GET, PUT
  • Update: The parameter phone, has been added to the request body as well to the response, for all the Dispatch Location APIs.

API Changelog 21 Sep 2020

📘

UPDATED

Made the following update to the Freight Visibility endpoint

  • Name: v1/freight_visibility/vehicle_locations
  • Method: GET
  • Update: Added the parameter current_driver. This will allow you to view the details of the current driver who is assigned the vehicle.

API Changelog - 8 Sep 2020

👍

ADDED

Added the following info

  • Name: v1/driving_periods
  • Method: GET
  • URL: https://api.gomotive.com/v1/driving_periods
  • Purpose: Use this API to fetch a list of the all the driving periods of the company's vehicles. This report includes information on driving hours, start and stop times, rest periods, distances traveled, and compliance with regulations like HOS (Hours of Service).

📘

UPDATED

The Driving Period endpoint has been updated

  • Name: v1/driving_periods
  • Method: GET
  • Update: The response of the API will now include the parameter source. This is the source of a driving period.

API Changlog - 31 Aug 2020

📘

UPDATED

Made the following changes to the Inspection Report APIs

  • Name: v1/inspection_reportsa
  • Update: The response of the Inspection Report APIs will now include log_id. This is the ID of the logs for the endpoint.

API Changelog - 27 Aug 2020

👍

ADDED

Content-Type HTTP Header

  • Update: The request content type header has now been added to all the endpoints.

API Changelog - 29 Jun 2020

👍

ADDED

Added the following endpoints

  • Name: v1/asset_locations
  • Method: GET
  • URL: https://api.gomotive.com/v1/asset_locations
  • Purpose: Use this API to fetch a list of all the company assets and their current location. This API will provide information about the asset such as make, model, year, and others that are crucial.
  • Name: v1/asset_locations/:id
  • Method: GET
  • URL: <https://api.gomotive.com/v1/asset_locations>
  • Purpose: Use this API to fetch a list of all the company assets and their current location. This API will provide information about the asset such as make, model, year, and others that are crucial.

API Changelog - 15 Jun 2020

👍

ADDED

Added a new endpoint to the Inspection Report APIs

  • Name: v1/inspection_reports/lookup_by_external_id
  • Method: GET
  • URL: https://api.gomotive.com/v1/inspection_reports/lookup_by_external_id
  • Purpose: Use this API to find an inspection report as per the external ID. It is important to note that the external ID is associated with an integration and you must specify the correct ID and its corresponding integration name.

API Changelog - 10 Jun 2020

📘

UPDATED

  • Updates: Updated the request payload for the Webhooks.

API Changelog - 18 May 2020

👍

ADDED

Added the following parameters for the Inspection Report endpoints

API Changelog - 11 May 2020

👍

ADDED

Added the following parameters to Dispatches API

  • Name: v1/dispatches
  • Method: GET
  • URL: https://api.gomotive.com/v1/dispatches
  • Purpose: The response to this endpoint will now fetch details such as the vendor_ids and the ids (Dispatch IDs).

API Changelog - 21 Apr 2020

👍

ADDED

The following parameters are added

API Changelog - 13 Apr 2020

📘

UPDATED

  • Update: The Geofences API will now have a maximum page limit of 500.

Added the following parameters

👍

ADDED

API Changelog - 7 Apr 2020

👍

ADDED

Added the following endpoints

  • Name: v1/freight_visibility/vehicle_locations
  • Method: GET
  • URL: https://api.gomotive.com/v1/freight_visibility/vehicle_locations
  • Purpose: Use this API to fetch the location of all the subscribed vehicles. This endpoint will provide important details of the vehicle such as the driver info, the latitude and longitude coordinates of the vehicle, initial stop, final stop. and current location.

  • Name: v1/freight_visibility/companies
  • Method: GET
  • URL: https://api.gomotive.com/v1/freight_visibility/companies
  • Purpose: Usually, a vehicle location or tracking information can be shared with third-parties, brokers, or stakeholders for regular monitoring as well as to provide certain services. This location sharing is done for a limited time period.

  • Name: v1/freight_visibility/subscribe
  • Method:POST
  • URL: https://api.gomotive.com/v1/freight_visibility/subscribe
  • Purpose:Use this API to subscribe to the location of a vehicle or an asset. When you subscribe to the location of an asset or a vehicle, you are essentially tracking the location of that object.

API Changelog - 6 Apr 2020

👍

ADDED

  • Retry intervals for Webhook requests.
  • SLA for responding to webhook requests.
  • Documentation for Public Document creation API's.
  • updated_after query parameter added to GET /v1/fault_codes API.

API Changelog - 11 Nov 2019

👍

ADDED

  • updated_after query parameter to GET /v1/inspection_reports
  • dispatch_ids query parameter to GET /v1/form_entries
  • driver_ids query parameter to GET /v1/form_entries
  • vehicle_ids query parameter to GET /v1/form_entries
  • Documentation for Geofence Public API endpoints.