Purpose
This guide explains how to obtain Report Web Service credentials from Arvento and how to use them in Logsign USO to ingest Arvento vehicle tracking and location report data for security analytics and forensic purposes.
Arvento is a Turkey-based vehicle tracking and fleet management platform (arvento.com). It is a cloud-hosted service and exposes its report data through a SOAP/HTTP web service rather than syslog, so this API poller is the supported way to bring Arvento data into Logsign USO. There is no on-premises Arvento alternative and no syslog equivalent for this data.
Prerequisites
You need an active Arvento account with Report Web Service access enabled. Arvento's public help documentation does not describe a self-service way to enable this from the standard web panel; it is provisioned by Arvento on request. Contact your Arvento account manager or Arvento support and ask them to enable Report Web Service (SOAP) API access for your account and to issue the Username, PIN1, and PIN2 values described in Step 1.
Use least privilege where possible. Arvento's public documentation does not describe a scoped, read-only, or API-only role comparable to a service account. The Username, PIN1, and PIN2 combination is an account-level credential set for the Report Web Service, and it was not possible to verify whether Arvento can restrict it to read-only report access or to a specific vehicle group at the account level. When you contact Arvento to request these credentials, ask whether they can be limited to read-only reporting and to only the vehicle group this integration needs, rather than reusing a full administrative panel login. This has not been verified against a live Arvento account and should be confirmed directly with Arvento.
Step 1: Obtain Report Web Service Credentials from Arvento
Request the following three values from Arvento support or your account manager:
- Username: the account username tied to your Arvento subscription.
- PIN1 and PIN2: two additional codes Arvento issues alongside the username to authorize calls to the Report Web Service. Their exact distinction is not documented in Arvento's public help center; treat both as secrets and request them together from Arvento.
Copy all three values exactly as Arvento provides them, with no leading or trailing spaces. The web service treats them as literal strings and does not attempt to normalize or trim them before use.
Step 2: Identify the Vehicle Group to Scope Reports To (Optional)
If your Arvento account has vehicles organized into groups, you can ask Arvento to confirm the exact group name to use so Logsign only pulls reports for that group. Leave this blank in Step 3 to pull reports for every vehicle and device visible to the account.
Step 3: Configure the Integration in Logsign USO
Log in to Logsign USO and add a new Arvento data source. You will be asked for:
| Field | Value |
|---|---|
| Username | The account username from Step 1 |
| PIN1 | The first PIN value from Step 1 |
| PIN2 | The second PIN value from Step 1 |
| Group | Optional. The vehicle group name from Step 2, or left blank for all vehicles |
This integration does not ask you for an API host or base URL. The Arvento Report Web Service endpoint is fixed inside the poller and is not configurable per tenant, so there is no regional address to look up and no https:// or trailing-slash format trap to worry about for this integration.
Once configured, Logsign polls Arvento's General Report endpoint on a recurring interval (one hour by default, governed by the data source's Poll Interval setting) and requests location report data for the configured window. Each vehicle location record is normalized into a Logsign event carrying the device number, license plate, speed, address, coordinates, and timestamp reported by Arvento. The integration currently retrieves location and speed report data only; other report categories the same Arvento web service can produce, such as door and ignition alarms, temperature and humidity sensor readings, fuel level, emergency alerts, and driver identification events, are not requested by this poller. If you need those, contact Logsign support to discuss whether they can be added.
Troubleshooting
Arvento's Report Web Service does not return conventional HTTP 401, 403, or 429 status codes for authentication or authorization failures. This was verified directly: sending a report request with placeholder credentials to the live endpoint returned an HTTP 302 redirect to a generic error page, which resolves to an HTTP 200 response containing a plain "Arvento - 500" HTML error page rather than the expected XML report or a machine-readable error code. Because of this, troubleshooting is organized by what you will actually observe in the Logsign poller logs rather than by status code.
| Symptom | Likely cause | What to check |
|---|---|---|
| Log shows "Request data format is wrong" and 0 events are collected | Arvento rejected the request and returned its generic HTML error page instead of an XML report. This happens when Username, PIN1, or PIN2 is wrong, expired, or Report Web Service access was never enabled for the account (verified behavior against the live endpoint with invalid credentials). | Re-confirm all three values with Arvento exactly as issued, with no extra spaces. If they are correct, ask Arvento to confirm Report Web Service access is still active on the account. |
| Log shows "Request error" followed by a message from Arvento | The credentials were accepted, but Arvento returned an application-level Error element inside the XML report, for example because of an invalid Group name or a date range issue. | Read the exact error text in the Logsign poller log. If the cause is not clear from the message, share it with Arvento support along with the approximate request time. |
| Log shows a request exception or timeout, no HTTP response at all | Network connectivity between the Logsign collector and ws.arvento.com is blocked, or Arvento's service is temporarily unavailable. The poller waits up to 180 seconds for a response before giving up. | From the Logsign collector host, confirm outbound access to ws.arvento.com on port 80 is allowed by any firewall or proxy in between. |
| Repeated failures under heavy polling frequency | Arvento does not publish a rate limit for this endpoint, and this behavior has not been observed or verified. If a rate limit exists, it would most likely surface the same way as the two rows above (a generic error page or a timeout) rather than as a distinct 429 response. | If failures line up with a shorter-than-default Poll Interval, try lengthening it and confirm whether the failures stop. |
Notes and Limits
- This integration currently collects location and speed report data only (Arvento's General Report with the location flag set). Arvento's web service also supports door, ignition, temperature, humidity, fuel, emergency, and driver identification report data, none of which this poller requests today.
- Each poll cycle requests one time window, one hour by default, rounded to the top of the hour. There is no pagination within that window. Very large fleets with a high volume of location records in a single hour have not been tested, and no maximum record count for a single Arvento report response was found in public documentation.
- The current poller connects to Arvento over plain HTTP, not HTTPS, even though the same Arvento host was confirmed to also answer over HTTPS. This means the request, including the Username, PIN1, and PIN2 values, is not encrypted in transit for this integration today. This is a property of the current poller implementation, not something configurable from the Logsign data source form, and is noted here for transparency rather than as an action you need to take.
- Every record ingested by this integration is normalized to the same event type (a generic "Vehicle Tracking Information" event). Arvento does not distinguish alarm types in the data this poller currently requests, so no separate event categories exist yet for speed violations, geofence entry and exit, or other alarm conditions.