e-Transport

At this time, the API provided by AROBS TrackGPS allows the use of 7 endpoints to manage transports in the company’s account:

Method URL Description
POST https://api.trackgps.ro/api/eTransport/add-transport?api-version=2.0 Add transport
POST https://api.trackgps.ro/api/eTransport/update-transport?api-version=2.0 Update transport
POST https://api.trackgps.ro/api/eTransport/load-transports?api-version=2.0 List transports
POST https://api.trackgps.ro/api/eTransport/remove-transports?api-version=2.0 Remove transports
POST https://api.trackgps.ro/api/eTransport/start-transports?api-version=2.0 Start transports
POST https://api.trackgps.ro/api/eTransport/end-transports?api-version=2.0 End transports
POST https://api.trackgps.ro/api/eTransport/pause-transports?api-version=2.0 Pause transports

The minimum interval between two consecutive requests is 30 seconds.

Subsections of e-Transport

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.0 parameter 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.

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.0 parameter 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.

Transport List

General Description

The load-transports endpoint is used to retrieve the list of available transports in a user’s account, based on their vehicle access rights. The user can specify parameters to filter transports, such as their status or a specific search value.

This endpoint is subject to Rate Limit restrictions.

⚠️ All transport date/time fields in the response are recorded in the company’s time zone, not UTC. Ensure that transports are managed according to the company’s time zone settings when retrieved from the system.

⚠️ All requests to this endpoint must include the api-version=2.0 parameter in the URL.
URL: POST https://api.trackgps.ro/api/eTransport/load-transports?api-version=2.0

⚠️ Transports with the status “Error” shown in the mobile and web applications are not returned by this endpoint.

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):

{
  "pageSize": 0,
  "pageIndex": 0,
  "statusIds": [
  1
  ],
  "searchValue": "string"
}
Parameter Type Required Description
pageSize number No Number of items returned per page.
pageIndex number No Page index for the request.
statusIds array Yes List of transport status IDs to filter by.
searchValue string No Word or phrase to search in the transport list.

Transport Status List

Id Description
1 Pending
2 In Progress
3 Completed
4 Auto Completed
5 Error
6 Paused

Response Structure

{
  "payload": {
  "totalRecords": 0,
  "transports": [
    {
    "uId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
    "carrierCode": "string",
    "carrierName": "string",
    "carrierUId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
    "trailer1Code": "string",
    "trailer2Code": "string",
    "codeUit": "string",
    "statusId": 0,
    "startDate": "2025-05-16T14:35:04.862Z",
    "endDate": "2025-05-16T14:35:04.862Z",
    "validityStartDate": "2025-05-16T14:35:04.862Z",
    "validityEndDate": "2025-05-16T14:35:04.862Z",
    "notes": "string",
    "startLocation": "string",
    "endLocation": "string",
    "externalId": 0,
    "externalResponse": "string",
    "lastSyncDate": "2025-05-16T14:35:04.862Z",
    "transmissionStatusCode": "string",
    "transmissionStatusErrorDescription": "string",
    "lastTransmissionDate": "2025-05-16T14:35:04.862Z",
    "lastGpsDate": "2025-05-16T14:35:04.862Z",
    "changeRequestMessage": "string",
    "changeRequestStatusCode": "string",
    "changeRequestCreatedAt": "2025-05-16T14:35:04.862Z",
    "changeRequestDate": "2025-05-16T14:35:04.862Z",
    "changeRequestAnafStatus": "string",
    "changeRequestAnafMessage": "string",
    "changeRequestAnafDate": "2025-05-16T14:35:04.862Z"
    }
  ]
  },
  "correlationId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "failureReasons": [
  {
    "errorCode": "string",
    "errorParameters": [
    "string"
    ]
  }
  ],
  "isSuccess": true
}

Property Descriptions

Property Type Description
payload object Object containing the returned transports and other relevant information.
totalRecords number Total number of available transports.
transports array List of available transports, each with specific details.
uId string Unique identifier of the transport.
carrierCode string Vehicle registration number used for transmitting location data to ANAF.
carrierName string Name of the vehicle used for transmitting location data to ANAF.
carrierUId string Unique identifier of the vehicle.
trailer1Code string Registration number for the first trailer.
trailer2Code string Registration number for the second trailer.
codeUit string UIT code generated by ANAF.
statusId number Transport status.
startDate string Start date and time of GPS data transmission to the ANAF platform.
endDate string End date and time of GPS data transmission to the ANAF platform.
validityStartDate string Start date of UIT code validity. This date is generated by the ANAF platform.
validityEndDate string End date of UIT code validity. This date is generated by the ANAF platform.
notes string Additional notes about the transport.
startLocation string Start location of the transport.
endLocation string End location of the transport.
externalId number Transport response identifier from the ANAF platform.
externalResponse string Response message from the ANAF platform for the transport.
lastSyncDate string Date when the transport was retrieved from the ANAF platform.
transmissionStatusCode string GPS data transmission status to the ANAF platform.
transmissionStatusErrorDescription string Error status description for GPS data transmission to the ANAF platform.
lastTransmissionDate string Date of the last GPS coordinate sent to the ANAF platform.
lastGpsDate string Date of the last GPS coordinate received from the vehicle.
changeRequestMessage string Response message for creating the transport data change request.
changeRequestStatusCode string Status of the transport data change request.
changeRequestCreatedAt string Date when the transport data change request was created.
changeRequestDate string Date when the response from the ANAF platform for the change request was received.
changeRequestAnafStatus string Status of the transport data change request received from the ANAF platform.
changeRequestAnafMessage string Response message for processing the transport data change request received from the ANAF platform.
changeRequestAnafDate string Date when the response from the ANAF platform for processing the change request was received.
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 not (false).

GPS Data Transmission Status List in the ANAF Platform

Code Description
Active Active transmission
Finalized Transmission finalized
NotInRomania Not on Romanian territory
NotStarted Transmission pending
Error Transmission error
MissingETransportConfiguration e-Transport configuration error, please contact support
OldData Data older than 6 hours
NoGPSCoordinates No GPS signal
WithoutTransmission No active GPS transmission

Status List for Transport Data Change Requests

Code Description
RequestCreated Request created
RequestSent Request sent successfully
RequestErrorSent Error sending request
ResponseSuccess Request completed successfully
ResponseError Request completed with error

Error Responses

HTTP Code Description
400 Missing parameters or invalid structure.
401 Incorrect credentials or unauthorized user.
429 Rate limit exceeded for the user.

Remove transports

General Description

The remove-transports endpoint allows you to delete one or more transports from the system, based on their unique identifiers (transportUId). This action is irreversible and requires appropriate access rights for the targeted transports.

It is subject to the restrictions described in Rate Limit

⚠️ All requests to this endpoint must include the api-version=2.0 parameter in the URL.
URL: POST https://api.trackgps.ro/api/eTransport/remove-transports?api-version=2.0

Request Parameters

Requests to this endpoint must use the POST method and include the following parameters:

  • Query parameter:

    • api-version (string, required) – The API version. Recommended value: 2.0

  • Body (JSON):

{
  "transportsUids": [
  "3fa85f64-5717-4562-b3fc-2c963f66afa6"
  ]
}
Parameter Type Required Description
transportsUids array Yes List of unique identifiers (GUID) of the transports to be deleted.

Response Structure

{
  "payload": true,
  "correlationId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "failureReasons": [
  {
    "errorCode": "string",
    "errorParameters": [
    "string"
    ]
  }
  ],
  "isSuccess": true
}

Property Descriptions

Property Type Description
payload boolean The result of the delete operation (true if successful).
correlationId string Unique identifier for the request, useful for traceability.
failureReasons array List of errors (if any), each with a code and parameters.
isSuccess boolean Indicates if the request was processed successfully (true or false).

Error Responses

HTTP Code Description
400 Missing, invalid, or incorrectly formatted parameters.
401 Unauthenticated user or insufficient permissions.
429 Rate limit exceeded for the user.

Start data session

General Description

The start-transports endpoint allows you to start (activate) one or more already created transports. This action sets the start date of the transport and marks it as active in the system.

It is subject to the restrictions described in Rate Limit

⚠️ All requests to this endpoint must include the api-version=2.0 parameter in the URL.
URL: POST https://api.trackgps.ro/api/eTransport/start-transports?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):

{
  "transports": [
    {
      "codeUit": "string"
    }
  ]
}
Parameter Type Required Description
transports array Yes List of transports to be started.
codeUit string Yes Unique UIT identifier code of the transport.

🕒 Important: All dates (startDate) must be sent in UTC format.

Response Structure

{
  "payload": {
    "codeUit": "string",
    "isSuccess": true,
    "errors": [
      "string"
    ]
  },
  "correlationId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "failureReasons": [
    {
      "errorCode": "string",
      "errorParameters": [
        "string"
      ]
    }
  ],
  "isSuccess": true
}

Property Descriptions

Property Type Description
payload boolean Result of the start operation (true if successful).
correlationId string Unique request identifier, useful for traceability.
failureReasons array List of errors (if any), each with code and parameters.
isSuccess boolean Indicates if the request was processed successfully (true or false).

Error Responses

HTTP Code Description
400 Missing, invalid, or incorrectly formatted parameters.
401 Unauthenticated user or insufficient permissions.
429 Rate limit exceeded for the user.

Stop data session

General Description

The end-transports endpoint allows stopping one or more active transports based on the UIT code. By performing this action, the transports are marked as finished in the system and can no longer be modified.

It is subject to the restrictions from Rate Limit

⚠️ All requests to this endpoint must include the api-version=2.0 parameter in the URL.
URL: POST https://api.trackgps.ro/api/eTransport/end-transports?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):

{
  "transports": [
    {
      "codeUit": "string"
    }
  ]
}
Parameter Type Required Description
transports array Yes List of transports to be stopped.
codeUit string Yes Unique UIT identification code of the transport.

🕒 Important: All dates (endDate) must be sent in UTC format.

Response Structure

{
  "payload": {
    "codeUit": "string",
    "isSuccess": true,
    "errors": [
      "string"
    ]
  },
  "correlationId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "failureReasons": [
    {
      "errorCode": "string",
      "errorParameters": [
        "string"
      ]
    }
  ],
  "isSuccess": true
}

Property Descriptions

Property Type Description
payload boolean The result of the stop operation (true if successful).
correlationId string Unique request identifier, useful for traceability.
failureReasons array List of errors (if any), each with a code and parameters.
isSuccess boolean Indicates if the request was processed successfully (true or false).

Error Responses

HTTP Code Description
400 Missing, invalid, or incorrectly formatted parameters.
401 Unauthenticated user or insufficient permissions.
429 Rate limit exceeded for the user.

Pause data session

General Description

The pause-transports endpoint allows pausing the position transmission of an active transport, based on the UIT code. Similar to start and stop, transports are temporarily paused.

It is subject to the restrictions described in Rate Limit.

⚠️ All requests to this endpoint must include the api-version=2.0 parameter in the URL.
URL: POST https://api.trackgps.ro/api/eTransport/pause-transports?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):

{
  "transports": [
    {
      "codeUit": "string"
    }
  ]
}
Parameter Type Required Description
transports array Yes List of transports to be paused.
codeUit string Yes Unique UIT identification code of the transport.

Response Structure

{
  "payload": true,
  "correlationId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "failureReasons": [
    {
      "errorCode": "string",
      "errorParameters": [
        "string"
      ]
    }
  ],
  "isSuccess": true
}

Property Descriptions

Property Type Description
payload boolean Result of the pause operation (true if successful).
correlationId string Unique request identifier, useful for traceability.
failureReasons array List of errors (if any), each with code and parameters.
isSuccess boolean Indicates if the request was processed successfully (true or false).

Error Responses

HTTP Code Description
400 Missing, invalid, or incorrectly formatted parameters.
401 Unauthenticated user or insufficient permissions.
429 Rate limit exceeded for the user.