Add transport
General Description
The add-transport endpoint allows you to add a new transport to the system. The user can specify all details related to the transport, including the associated vehicle, start and end dates, locations, and additional information such as the associated trailer.
It is subject to the restrictions in Rate Limit
⚠️ All requests to this endpoint must include the
api-version=2.0parameter in the URL.
URL:POST https://api.trackgps.ro/api/eTransport/add-transport?api-version=2.0
Request Parameters
Requests to this endpoint must be of type POST and include the following parameters:
-
Query parameter:
api-version(string, required) – API version. Recommended value:2.0
-
Body (JSON):
{
"vehicleUId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"startDate": "2025-04-09T07:38:24.380Z",
"endDate": "2025-04-09T07:38:24.380Z",
"codeUit": "string",
"notes": "string",
"startLocation": "string",
"endLocation": "string",
"vatNumber": "string",
"validityStartDate": "2025-04-09T07:38:24.380Z",
"validityEndDate": "2025-04-09T07:38:24.380Z",
"trailer1Code": "string",
"trailer2Code": "string"
}| Parameter | Type | Required | Description |
|---|---|---|---|
| vehicleUId | string | Yes | Unique identifier of the vehicle associated with the transport. |
| startDate | string | No | Start date and time for sending GPS data to the ANAF platform (ISO 8601 format, UTC). |
| endDate | string | No | End date and time for sending GPS data to the ANAF platform (ISO 8601 format, UTC). |
| codeUit | string | Yes | UIT code generated by ANAF. |
| notes | string | No | Additional notes about the transport. |
| startLocation | string | No | Start location of the transport. |
| endLocation | string | No | End location of the transport. |
| vatNumber | string | Yes | Carrier’s VAT number (CIF). |
| validityStartDate | string | Yes | Start date of UIT code validity. This date is generated by the ANAF platform (ISO 8601 format, UTC). |
| validityEndDate | string | Yes | End date of UIT code validity. This date is generated by the ANAF platform (ISO 8601 format, UTC). |
| trailer1Code | string | No | Registration number for the first trailer. |
| trailer2Code | string | No | Registration number for the second trailer. |
🕒 Important: All date fields (e.g.
startDate,endDate,validityStartDate,validityEndDate) must be sent in UTC format.
Response Structure
{
"payload": true,
"correlationId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"failureReasons": [
{
"errorCode": "string",
"errorParameters": [
"string"
]
}
],
"isSuccess": true
}Property Description
| Property | Type | Description |
|---|---|---|
| payload | boolean | Indicates whether the transport was successfully added (true or false). |
| correlationId | string | Request identifier for correlating responses. |
| failureReasons | array | List of error reasons (if any), with additional details. |
| isSuccess | boolean | Indicates whether the request was processed successfully (true or false). |
Error Responses
| HTTP Code | Description |
|---|---|
| 400 | Missing parameters or invalid structure. |
| 401 | Incorrect credentials or unauthorized user. |
| 429 | Rate limit exceeded for the user. |