Introduction

Ghubee is a robust integration platform designed to facilitate the search and processing of data across multiple vendors (suppliers).

Our mission is to abstract the complexity of connecting to different sources. We perform data extraction, adjustment, and processing, returning standardized responses in our APIs, regardless of the information's origin.

Available Services
Through the Ghubee interface, you can access a unified suite of services to manage fleet data efficiently:

Drivers: Retrieves information about drivers and their profiles.
Fleet Rock: Retrieval of Repair Orders.
Geofences: Provides data regarding the vehicle's traveled perimeter and location boundaries.
MapBox: Provides interactive map rendering with multiple points, custom marker visualization, route display, and geocoding search capabilities for location-based services.
Quickbooks: It enables comprehensive financial data management including accounts retrieval, purchase transaction management, and vendor management operations.
Safety Driver: Focuses on vehicle and driver safety, allowing for the monitoring and analysis of non-standard behaviors (acceleration, braking, cornering) and distractions (cellphone use, eating while driving).
Safety Forward: It enables company creation, driver creation, driver enrollment, driver status updates, and access to training courses and assigned driver courses.
Utilizations: Offers access to vehicle and driver usage metrics, reinforcing the analysis of driving behaviors and events.
Vehicles: Facilitates integration to retrieve detailed vehicle information based on input data.
Vehicle History Positions: Provides vehicle tracking information to assist with efficient route planning.

Prerequisites and Authentication
To consume data through our standardized endpoints, please ensure your environment meets the following requirements:

Network Access (VPN Required): For security reasons, our API environment is restricted and not publicly accessible from the open internet.
1. You must be connected to the VPN to perform tests or consume the endpoints.
2. Attempts to access the API without an active VPN connection will result in connection errors or timeouts.
Ghubee Account: To consume data through our standardized endpoints, the main requirement is to have an active account on the Ghubee platform.
Access Token: All calls must be authenticated using a valid Token, which is generated directly within the Ghubee administrative panel.

Supported Vendors and Specific Headers Currently, Ghubee offers data integration, processing, and standardization for the following vendors:

Geotab
Multiportal
Motive
Truckspy

Headers per Vendor

In addition to the Ghubee authentication Token, each vendor requires a specific standard header for the request to be processed correctly.

Technical Note: When consulting the specific documentation for each endpoint below, check which header must be sent together with the main token for the desired vendor (client-key, username, password etc.).

⚠️ Important: Standardization vs. Data Availability

Although Ghubee has active integrations with all the vendors listed above, it is fundamental to understand how we handle information returns:

Standardization: We guarantee that the response JSON structure is always the same, facilitating your implementation.
Source Availability: Not all source APIs possess all the data that our standardized structure supports.

How does the system behave? If the source does not possess the requested information (due to limitations of the supplier itself or lack of registration), Ghubee will not return an error. Instead, we will return the standardized fields with null or empty values.

This ensures that the application never breaks due to contract changes, always receiving the expected structure, even if the data does not exist at the source.

Our APIs can all be accessed through HTTPS requests to URLs like:

https://hml.ghubee.com/api/{eld}/<endpoint>