
Mapon and RMPD: how to connect a Mapon tracker to trip tracking with an API key
Mapon and RMPD are linked through an API key: the Mapon account administrator creates the key and picks the vehicles, and their coordinates appear on the “Fleet map” and in trip tracking in your Moisa Logistics account. The Mapon tracker does not become a locator for RMPD or SENT. Below: four steps in Mapon, what you will see in the account and the usual mistakes.
Key figures
In short: Mapon and RMPD tracking
A Mapon tracker connects to your Moisa Logistics account with an API key. The Mapon account administrator creates the key under Settings → API keys, picks the vehicles Moisa will see and pastes the key into the “Access key” field in our account. We only see those vehicles and their coordinates and change nothing in Mapon. In the account this system is labelled “Mapon and its partners”: if a partner on the Mapon platform services your tracker, the key is created the same way.
The Mapon key does not give you a number for the RMPD. The notification needs a locator: the e-TOLL PL app, an OBU or a ZSL device of an operator registered in e-TOLL.
- Where Mapon shows up: the “Fleet map” - every vehicle in the key, on a trip or not; an order with an RMPD - the dashed tracker line next to the PUESC line.
- What it gives you: the account tells a stop from a signal loss and warns you when the truck is moving while PUESC gets no positions.
- Who connects it: in Mapon, the account administrator creates the key; in the Moisa Logistics account, the company owner connects it.
Mapon and RMPD: tracker or locator
Mapon describes itself on its website as a fleet management platform: GPS tracking, tachographs, fuel, video. For a Polish RMPD something else matters - where PUESC gets the positions from. A locator or device number is mandatory in an RMPD (Art. 28b(3)(12) of the Polish Road Transport Act), and positions from it must reach PUESC along the whole Polish stretch (Art. 28b(5)). The SENT Act accepts a locator - in practice the e-TOLL PL app on the driver’s phone - or an external location system (ZSL) that a ZSL operator fits permanently in the vehicle; there is also the portable OBU. Only the operator registers a device in PUESC - for e-TOLL, for SENT or for both (PUESC FAQ 07.05).
The API key opens Mapon coordinates to our account, not to PUESC. So before the trip, check:
- Whether your provider is a ZSL operator - ask them, or find them on the official list of OBU/ZSL operators and devices admitted to e-TOLL at etoll.gov.pl (the “OBU and ELS on-board devices” section, version of 06.11.2026).
- Whether the device is registered for SENT specifically: a device registered only for e-TOLL pays the tolls but gives no positions in RMPD 406 (FAQ 07.15). An operator device number starts with Z or U.
- What is entered in the RMPD while there is no ZSL number: as the main locator - e-TOLL PL on the driver’s phone.
What the number looks like and how to set up a main and a backup locator is in the article GPS locator for RMPD and SENT. What happens when an RMPD carries a tracker that is not in SENT is in the article car transporters and GPS fines in Poland. Which other systems connect to the account and how a fleet tracker differs from a locator is covered in the overview GPS tracker for RMPD and SENT.
What Mapon shows in your Moisa Logistics account
For RMPD tracking the account takes positions from PUESC, and Mapon data comes in as a second source, so you understand what is happening to the truck:
| Situation | What the account shows |
|---|---|
| The truck is not on a trip | “Fleet map”: “Not on a trip - location from tracker” and the time of the last point |
| The truck is on a trip with an RMPD | “Fleet map”: the order number and the route driven; in the order - the PUESC line and the dashed Mapon tracker line for the order’s time |
| PUESC is silent, Mapon shows a stop | “Stopped · per tracker”: a pause, not a signal loss, so we send no alert; when it moves, we check again |
| PUESC is silent, Mapon shows movement | “Fine risk” and an alert: check the locator or the driver’s app |
| There is a dashed Mapon line but no PUESC line | The truck was moving while the PUESC locator was silent - you see on which stretch |
Tracker data refreshes every 5 minutes. We are not a government service and only show tracking data from PUESC: when the connection drops, the cause - the locator, the driver’s app or the mobile operator - is found on the spot. The plan of action is in the article RMPD 406: GPS signal lost.
Mapon API key: how to create a key for Moisa Logistics
Only account administrators or users with unlimited permissions can manage API keys in Mapon, and Mapon support does not create a key for the client. Mapon advises a separate key for each third-party platform - so create one just for Moisa.
- Sign in to Mapon as the account administrator.
- Settings → API keys → CREATE API KEY - the button in the top-right corner of the API keys section.
- Select the vehicles Moisa will see - all of them or a limited list, single vehicles or a group - and click SAVE. The new key appears in the API keys section.
- Copy the key.
Then, in your Moisa Logistics account:
- Profile → the “Integrations” tab → the “GPS trackers” section.
- Pick the Mapon tile among the GPS providers, or the system directly - “Mapon and its partners”. The “Step-by-step guide” button shows these same steps.
- Paste the key into the “Access key” field and click “Check and connect”.
The “GPS trackers” section (Profile → “Integrations”) is in every company’s account, and the company owner does the connecting.
New vehicles, matching and disconnecting
Vehicles in the key are matched to the fleet by licence plate on their own; the connection card shows “Trackers: N, matched to vehicles: M”. Whatever was not matched, pick in the tracker list under the card - a vehicle from the fleet or “Not from the fleet”.
Add new vehicles to this key in Mapon - otherwise we will not see them. The key is edited in the same API keys section. To disconnect, click “Disconnect”: we delete the access on our side, and the trackers disappear from the fleet map. Cancel the key itself in Mapon, in the API keys section.
Example: Krakovets - Korczowa, three trucks
A carrier has connected Mapon; the key holds the whole fleet except a new tractor unit (the example is made up).
- A truck without an RMPD waits for loading near Lviv: the “Fleet map” shows “Not on a trip - location from tracker” with the time of the last point.
- A truck with an RMPD has crossed Krakovets - Korczowa: the order shows the PUESC line and the dashed Mapon line. At a night stop near Rzeszów, PUESC is silent for a while and Mapon shows the truck parked - status “Stopped · per tracker”, no alert.
- The new truck is not on the map: it was not added to the key. The administrator adds it to the key in Mapon, and it appears with the next refresh.
If PUESC is silent while Mapon sees movement, the account sets “Fine risk” and sends an alert. After more than an hour without a locator the driver must stop at the nearest parking place (Art. 10c of the SENT Act), and the carrier faces 10,000 zł for missing geolocation in the RMPD.
Common mistakes with the Mapon API key
| What you see | What to check |
|---|---|
| Mapon shows no API keys section or no CREATE API KEY button | You are not signed in as an administrator: only account administrators or users with unlimited permissions manage API keys |
| “The GPS system returned no vehicles” | Whether vehicles were selected in the Mapon key |
| A new truck does not appear on the map | Whether it was added to this key in Mapon |
| “The system does not accept this key” | Whether the key was copied in full and whether its access was cancelled in the API keys section |
| The account is already connected to another company | This Mapon account is already connected to another company in Moisa Logistics - write to support |
| The tracker is on the map, but RMPD 406 shows no positions | The tracker is not registered in SENT, or the RMPD carries another number: check the locator number and, if needed, enter e-TOLL PL with an RMPD 101 correction |
RMPD tracking at Moisa Logistics: price
- Trip tracking is included in the RMPD price: full service - 500 UAH per document, self-service in the account - 100 UAH (the first 10 days - 0 UAH).
- RMPD 406 - 50 UAH for an RMPD made elsewhere: a route map from PUESC data and an alert when GPS disappears.
Order: RMPD full service, RMPD self-service, RMPD 406. How to read the tracking statuses is explained in the article why RMPD 406 and trip tracking.
Frequently asked questions
Sources
- Ustawa z dnia 6 września 2001 r. o transporcie drogowym, tekst jednolity Dz.U. 2025 poz. 1490 (art. 28, 28b, 28c, 89a1, załączniki nr 1 i 3)checked 21 November 2026
- Ustawa o systemie monitorowania drogowego i kolejowego przewozu towarów (SENT), tekst jednolity Dz.U. 2024 poz. 1218: art. 2, 3 ust. 6, 5-11, 13-17, 21-24, 31-32 (dla RMPD - przez art. 28b ust. 5 ustawy o transporcie drogowym)checked 21 November 2026
- PUESC - FAQ SENT, 07. Obsługa zewnętrznych systemów lokalizacji ZSL/OBU (07.05-07.20, aplikacja e-TOLL PL jako lokalizator zapasowy)checked 21 November 2026
- e-TOLL - Urządzenia pokładowe OBU i ZSLchecked 21 November 2026
- e-TOLL - Lista Operatorów i urządzeń OBU/ZSL dopuszczonych do systemu e-TOLL (wersja z 06.11.2026)checked 21 November 2026
- e-TOLL - Aplikacja mobilna e-TOLL PL: instrukcja korzystania dla przejazdów SENT/RMPD (identyfikator biznesowy, Przejazd SENT/RMPD, Lokalizacja GPS SENT/RMPD 406, status baterii i GPS)checked 21 November 2026
- Mapon Help Center - How to create API key: Settings → API keys → CREATE API KEY, available vehicles and actions, SAVE; only account administrators or users with unlimited permissions; separate keys for different third-party platformschecked 21 November 2026
- Mapon - fleet management platform: GPS tracking, tachograph, fuel, video telematics, integrationschecked 21 November 2026
Need documents for a trip?
Create a free account and prepare the document in your account - by yourself or with our team’s hands. Or leave a request: we will call you and tell you what you need for your particular trip.
More news



We are on TikTok
How to prepare documents from your phone, what is changing for carriers and where to save - in short videos.



