Applies to: Admins · Partner Admins · Operations Manager · Dispatcher
Module: Management > Integrations
Owner: Support
Last reviewed: 2026-06
Connect RoadStar to Alvys to pull real-time location data from your RoadStar-equipped trucks and trailers, giving you visibility on the Asset Map and in dispatch planning.
Overview
RoadStar (also referred to as RoadStar ELD, RoadStar telematics, or BrightRoadStar) is an electronic logging device (ELD) solution that tracks driver hours of service and vehicle locations. This integration allows Alvys to pull real-time location data from your RoadStar-equipped trucks and trailers automatically, so your team can see asset positions on the Asset Map and use that data in dispatch planning.
This is a one-way integration: RoadStar pushes location data to Alvys. No load data or driver hours of service data is written back to RoadStar.
Prerequisites
Before you connect RoadStar to Alvys, you need the following:
An active RoadStar account with permission to generate API tokens.
Access to your Alvys account with Admin or Partner Admin permissions.
Estimated time to complete setup: 20 minutes.
How to connect
Generate your RoadStar API token.
Log into your RoadStar account and navigate to Management > API Tokens.
Click Generate Token.
RoadStar API Tokens screen showing the Generate Token button
Open the Integrations section in Alvys.
Click the profile icon in the bottom left corner of Alvys.
Image showing navigation to the Alvys Integrations page
Image showing navigation to the Alvys Integrations page
Select the subsidiary you want to configure.
Enter your RoadStar API token.
In the Integrations tab, expand the ELD section and click the pencil icon on the RoadStar card.
Image showing ELD tab expanded on the Alvys Integrations page
Image showing ELD tab expanded on the Alvys Integrations page
Enter your RoadStar API Token and click Save.
Image showing the Alvys “Add Integration” form for RoadStar Eld
Map assets for location tracking
You must map each truck or trailer in Alvys to its corresponding RoadStar asset ID. Without this step, location data will not appear even if the integration credentials are valid.
Open the asset in Alvys.
Go to Assets in the left menu and select Trucks or Trailers.
Double-click the asset you want to configure, then scroll down to the ELD Integrations section and click Add Integration.
Find your RoadStar asset ID.
Open the asset in your RoadStar platform and look at the URL in your browser. The asset ID is the number at the end of the URL path. For example, if the URL is app.brightroadstar.com/client/trucks/25236, the asset ID is 25236.
Enter the asset ID and save.
Select RoadStar from the Add Integration dropdown, enter the asset ID in the Integration ID field, and click Save.
Repeat this process for each truck or trailer you want to track with RoadStar.
Image showing “Add Integration” dropdown on asset profile
What syncs
Once the integration is active, Alvys pulls location data from RoadStar for each asset that has been mapped. The following data flows from RoadStar to Alvys:
Real-time asset location (latitude and longitude).
Asset positions visible on the Alvys Asset Map.
After the integration is configured and assets are mapped, Alvys automatically pulls location updates from RoadStar on a recurring basis. No manual action is required after initial setup. Location data appears on the Asset Map as long as the asset has a valid RoadStar asset ID mapped in Alvys.
To confirm the integration is working, open the Asset Map in Alvys after completing setup and mapping at least one asset, then verify the mapped truck or trailer is showing a current location. If the asset is not showing a location, see Troubleshooting below.
📋 Limits and unsupported:
The integration pulls location data only, driver hours of service (HOS) data is not surfaced in Alvys.
The integration is configured per subsidiary; each subsidiary requires its own RoadStar API token.
Each truck or trailer must be mapped individually — there is no bulk asset mapping option.
Only trucks and trailers can be mapped to RoadStar asset IDs.
Troubleshooting
Asset location not appearing on the Asset Map
Confirm the RoadStar API token saved in Integrations is correct. An invalid token will prevent location data from syncing. Navigate to Management > Integrations, expand the ELD section, and verify the RoadStar card shows an active status.
Confirm the asset has a RoadStar asset ID mapped. Open the asset in Alvys (Assets > Trucks or Assets > Trailers), scroll to ELD Integrations, and verify a RoadStar entry with a valid Integration ID is present.
Confirm the asset ID matches the number in the RoadStar platform URL for that asset. A mismatch will cause the location sync to fail silently.
If credentials are valid, the asset ID is correct, and location data is still not appearing, contact Alvys support and provide the asset name and the RoadStar asset ID so the technical team can investigate the sync response.
Invalid API token error on save
Re-generate the API token in your RoadStar account (Management > API Tokens > Generate Token) and copy the new token exactly.
Return to Alvys Integrations, expand the ELD section, click the pencil icon on the RoadStar card, paste the new token, and click Save.
FAQs
Q: Where do I find my RoadStar asset IDs?
A: The easiest way is to look at the URL when viewing or editing an asset in your RoadStar platform. The asset ID is the number at the end of the URL path (for example, app.brightroadstar.com/client/trucks/25236 gives asset ID 25236).
Q: Can I track both trucks and trailers?
A: Yes. You can configure RoadStar tracking for both trucks and trailers by adding the integration to each asset individually.
Q: What happens if I enter an invalid API token?
A: Alvys validates credentials on save. If the token is incorrect, you will see an error immediately and the integration will not activate. Re-generate the token in RoadStar and re-enter it in Alvys.
Q: Does this integration require setup for each subsidiary separately?
A: Yes. The RoadStar API token is configured per subsidiary. If you have multiple subsidiaries, each one needs its own token entered in its own Integrations tab.