Send GPS positions from any tracker

Solmex accepts machine positions from any GPS tracker, through a simple web request. This page is for whoever builds the connection: your tracker supplier, your IT team, or a small script on your own server that reads positions from the tracker platform and passes them on.

To create the key and bind devices to machines in the app, follow Connect GPS trackers. If your trackers are on Wialon Hosting, you do not need this page: see Connect Wialon.

#Before you start

• Live Map is switched on per company, not by plan. Without it, the feed answers that your plan does not include it.
• An administrator with Settings: Edit creates a feed on the GPS feed tab of Settings and hands you its key. The key is shown once.
• The Location the machines work on needs a map plan, or positions cannot be placed in a Sublocation. See Create a site plan.

#The request

Send an HTTPS POST to your company's Solmex address followed by /api/telematics/positions. The GPS feed tab of Settings shows the full address for your company, ready to copy. For a company at yourcompany.getsolmex.com, that is:

POST https://yourcompany.getsolmex.com/api/telematics/positions
Authorization: Bearer <the feed's key>
Content-Type: application/json

{"positions": [
  {"device_id": "860123456789012", "at": "2026-10-12T09:41:12Z", "lat": -6.1659, "lng": 39.2026, "accuracy_m": 8, "speed_kph": 12.5, "heading_deg": 270}
]}

There is no login and no session: the key in the Authorization header is the whole credential. Keep it out of code repositories and logs.

#The fields of a position

Send positions in batches of up to 1,000, in a body of no more than 1 MB.

#The answer

A successful request returns counts for that batch:

Sending the same position twice is safe: it is counted as a duplicate, never stored twice. So if a request fails or times out, send the batch again.

#What Solmex does with a position

Every accepted position is kept for 30 days, which is what draws a machine's day track. A position becomes an entry in the machine's location history only when it says something new: the machine changed Sublocation, or an hour has passed since its last GPS entry. A position is never moved to the nearest Sublocation. These rules are explained in Connect GPS trackers.

#Limits

#Errors

Reasons you may see in rejected:

• "A device id is required."
• "That coordinate is not on the earth." Check you have not swapped latitude and longitude, or sent zeros.
• "That fix is dated in the future." The sending computer's clock is wrong, or the time zone is missing.
• A message that the feed already has 200 devices with no machine bound. Bind the real ones on the GPS feed tab before more can report.

#Troubleshooting