Prerequisites
Before registering a vehicle, ensure you have:- Valid c.technology API credentials with appropriate permissions
- Vehicle identification information (VIN, registration, etc.)
- IoT device details if you are using an IoT device (IMEI, ICCID, etc.)
- Set up your organization’s vehicle taxonomy and parts, if applicable
If you have purchased IoT devices and SIM cards from c.technology, they are pre-configured to work with the platform. You will only need your device ID to associate the vehicle with your organization.
Registration
Using the API, you can register vehicles programmatically.For single vehicle registrations, it may be more convenient to use the c.technology web application.
organization_vehicle_id
is your internal identifier for the vehicle (e.g., fleet number), and organization_vehicle_type_id
is the ID of the vehicle type as defined in your organization’s taxonomy.
You can optionally provide additional details such as name
, vehicle_identification_number
(VIN), and assign specific vehicle_parts
to the vehicle (as defined in your organization’s parts taxonomy).
Please refer to the API reference for the full list of parameters and their descriptions.
You should receive a HTTP 200 response with the vehicle details:
PUT /organization/{organization_id}/vehicle/{vehicle_id}
endpoint.
Similarly, you can manage vehicle part assignments using the /vehicle/{vehicle_id}/vehicle-part/
endpoints.
Bulk registration
For bulk registrations, you may upload CSV files via the c.technology web app or use the API to register multiple vehicles in a loop.Troubleshooting
This section may help you resolve common issues during vehicle registration.SIM card configuration errors
If you encounter SIM card configuration issues, log into your carrier’s portal (e.g., 1nce, 1ot, emnify, etc.) and verify the SIM card ICCID is correct and the SIM is active.
Device communication issues
If you experience problems with device connectivity, ensure the device is powered on and has a stable cellular connection.
Often, devices may take several minutes to register on the network after initial power-up.
Similarly, GPS modules may take time to acquire a satellite fix, and upon initial startup may not send data before a fix is acquired (due to aquiring a correct timestamp via GPS).
API validation failures
Please check if any of the following common validation errors apply:
- Duplicate VIN: Vehicle already registered in system.
- Invalid device IMEI: IMEI format is wrong (IMEIs are 15 digits long).
- Missing permissions: User lacks vehicle creation permissions.
- Invalid vehicle type: Unsupported or incorrect vehicle classification.