Vehicle Live Data API
Table Of Contents
| Provider Details |
|
2 |
| Revision History |
|
2 |
| Requester Details |
|
2 |
| Introduction |
|
3 |
| Base URLs |
|
3 |
| Status Codes |
|
3 |
| API URL |
|
3 |
| Response Format |
|
3 |
Provider Details
| Company Name |
{{ $companyName }} |
| Product |
Vehicle Live Data API |
| API Version |
{{ $documentVersion }} |
| Website |
{{ $providerWebsite }} |
| Production Base URL |
{{ $baseUrl }} |
| Address |
{!! nl2br(e($providerAddress)) !!} |
| Email |
{{ $providerEmail }} |
| Phone |
{{ $providerPhone }} |
Revision History
| Date |
Version |
Changes |
| {{ $documentDate }} |
{{ $documentVersion }} |
Vehicle Live Data API Documentation |
Requester Details
| Name |
{{ $requester->name }} |
| Mobile |
{{ $requester->phone }} |
| API Token |
{{ $requester->unique_token }} |
Introduction
- Vehicle Live Data API Version {{ $documentVersion }} is designed for backend systems and third-party integrations.
- You need to obtain an API token to authenticate into the API.
- Use the API token provided in the Requester Details section in every API request.
- Requests without a valid token will return an authentication error.
- The keyword parameter accepts either vehicle registration number or device IMEI.
- If keyword contains only numbers, it is treated as IMEI; otherwise it is treated as vehicle number.
Base URLs
| System |
Base URL |
| Production |
{{ $baseUrl }} |
Status Codes
| HTTP Status Code |
Status |
| 200 |
Success |
| 400 |
Error |
API URL
{{ $apiUrl }}
Replace {vehicle_no_or_imei} with the vehicle registration number or device IMEI.
Response Format
Success Response
{"status":"success","code":200,"data":{"vehicle_registration":"KL21S7778","imei_no":"862493054867381","latitude":"008.642861","ignition":"OFF","speed":0.0,"longitude":"076.842773","source_date":"11-09-2025 01:00:45 PM"}}
Error Response
{"status":"failure","code":400,"error":"Invalid User"}