Update transport
General Description
The update-transport endpoint allows you to modify an existing transport in the system. You can update details such as the period, locations, notes, or trailer information.
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/update-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) – The API version. Recommended value:2.0
-
Body (JSON):
{
"transportUId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"vehicleUId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"startDate": "2025-04-09T07:38:24.380Z",
"endDate": "2025-04-09T07:38:24.380Z",
"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 |
|---|---|---|---|
| transportUId | string | Yes | The identifier of the transport to be updated. |
| vehicleUId | string | Yes | The identifier of the vehicle associated with the transport. |
| startDate | string | No | Start date and time for GPS data transmission to the ANAF platform (ISO 8601, UTC format). |
| endDate | string | No | End date and time for GPS data transmission to the ANAF platform (ISO 8601, UTC format). |
| validityStartDate | string | Yes | Start date of the UIT code validity. Generated by the ANAF platform (ISO 8601, UTC format). |
| validityEndDate | string | Yes | End date of the UIT code validity. Generated by the ANAF platform (ISO 8601, UTC format). |
| notes | string | No | Additional notes. |
| startLocation | string | No | Start location. |
| endLocation | string | No | End location. |
| vatNumber | string | Yes | Carrier’s VAT number (CIF). |
| trailer1Code | string | No | Registration number for the first trailer. |
| trailer2Code | string | No | Registration number for the second trailer. |
🕒 Important: Date fields (
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 Descriptions
| Property | Type | Description |
|---|---|---|
| payload | boolean | Indicates if the transport update was successful. |
| correlationId | string | Unique identifier for the request (for traceability and debugging). |
| failureReasons | array | List of error reasons (if any), with codes and parameters. |
| isSuccess | boolean | Indicates if the request was processed without errors (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. |