Endpoints Overview

An endpoint is like a specific door in the library that takes you to a specific dataset. Each endpoint serves a unique purpose, like showing driver information or safety event history.

The Manifold Data REST API provides multiple endpoints, each designed to serve a specific function within your fleet data management process. The following is a detailed overview of each endpoint:

1. Connections Endpoint

• Purpose: The Connections endpoint allows you to view and manage the connections between your fleet management systems and the Manifold platform. Connections represent the link between your telematics system and Manifold, enabling the aggregation and monitoring of fleet data in real-time.
• Data You Can Access: Retrieve detailed information about all connections in your account, including connection health, provider details, and integration status.
• Use Cases: This endpoint is particularly useful for auditing connected systems, monitoring the health status of integrations, and ensuring uninterrupted data flow from your telematics systems to the Manifold platform.
• Core Features: The ability to track and monitor the health of each connection helps fleet managers identify integration issues early, ensuring data accuracy and timeliness.

2. Drivers Endpoint

• Purpose: The Drivers endpoint enables you to access a comprehensive list of all drivers associated with your fleet. This data is crucial for maintaining up-to-date information about driver assignments, contact information, and license details.
• Data You Can Access: Retrieve driver information such as contact details, license number, and status. This helps with monitoring driver compliance and ensuring operational consistency.
• Use Cases: Fleet managers can use this data for driver management, auditing compliance (e.g., licensing), and maintaining communication with drivers. It is also useful for correlating driver behavior with safety events.
• Core Features: The ability to keep track of each driver’s status and contact information helps ensure that fleet operations are compliant with regulations and that drivers can be quickly reached in case of an incident.

3. Safety Events Endpoint

• Purpose: The Safety Events endpoint is designed to provide insights into risky behaviors and incidents, such as harsh braking, collisions, and speeding events. It enables you to assess the safety of your fleet and take proactive measures to mitigate risks.
• Data You Can Access: Retrieve detailed safety event data, including the type of incident, duration, speed, and timestamps. Events like harsh braking or collisions are logged to give a clear picture of driving behavior.
• Use Cases: This endpoint is vital for fleet safety management, allowing fleet managers to identify high-risk drivers, analyze incidents, and develop training or intervention programs. The data can also be used to provide feedback and coaching for drivers to improve fleet safety.
• Core Features: Detailed safety event tracking enables proactive risk management. The data helps identify patterns of risky driving behaviors, which can be addressed through targeted coaching programs to reduce accidents and improve overall fleet safety.

4. Trips Endpoint

• Purpose: The Trips endpoint allows you to access historical data on vehicle trips, including breadcrumb locations and timestamps. This is essential for understanding vehicle routes, analyzing performance, and verifying compliance with planned routes.
• Data You Can Access: Retrieve breadcrumb locations for each trip, which include GPS coordinates and timestamps. This data helps track historical movement, validate routes, and ensure compliance with schedules.
• Use Cases: Fleet managers can utilize this endpoint to perform detailed route analysis, validate trip efficiency, and ensure compliance with legal or operational requirements. It is also useful for identifying route deviations or inefficiencies, which could lead to improved operational planning.
• Core Features: Detailed trip data provides insights into route efficiency, deviations, and overall fleet performance. Historical data can also be used to optimize routes, reduce fuel consumption, and enhance the timeliness of deliveries.

Each endpoint is crafted with flexibility in mind, allowing you to customize your requests with parameters such as date ranges, specific driver IDs, or vehicle IDs to obtain the exact data you need. Every endpoint description in this documentation includes detailed information on required headers, parameters, example requests, and response fields. This approach ensures that you have everything you need to effectively integrate with the Manifold platform and build robust, data-driven applications for fleet management.