Skip to main content
RastroSystem is a Brazilian vehicle-tracking platform used by tracking companies to manage their fleet of monitored vehicles, trackers and SIM chips, their customers, installation and maintenance work orders, support tickets and billing. The connector reads your company’s RastroSystem platform through its REST API v3 and brings vehicles with their last position, tracker events, geofence entries and exits, people, equipment, service orders, tickets and receivable and payable installments to your Lakehouse.

​
Configuring RastroSystem as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the RastroSystem option from the list of connectors. Click Next and you’ll be prompted to add your access.

​
1. Add account access

RastroSystem has no API keys: the connector signs in with the username and password of a RastroSystem platform user, the same ones used to open your company’s platform in the browser. Every company has its own platform address, such as https://yourcompany.rastrosystem.com.br.
Create a dedicated user for Nekt instead of using a person’s login, so a password change or a deactivated employee does not stop your syncs.
The connector reads only what this user is allowed to see. Give the user permission to list vehicles (veiculos_ver_todos to see every customer’s vehicles), people, equipment, chips, service orders (ordens_servico_listar), tickets, the financial accounts (menu_financeiro) and the event report (relatorios_rel_eventos). If the user cannot read a stream you selected, the sync stops with a message naming the stream and the missing permission: grant it to the user or deselect the stream. A table is never replaced by incomplete data.
The following configurations are available:
  • Platform URL: the address of your company’s RastroSystem platform, such as https://yourcompany.rastrosystem.com.br. The subdomain alone (yourcompany) is also accepted. Only addresses under rastrosystem.com.br are accepted, and the connection always uses HTTPS. Required.
  • Username: the username of the RastroSystem user. Required.
  • Password: the password of that user. Required.
  • Start Date: the earliest date of vehicle events and geofence entries and exits to extract. The first sync, and every vehicle or geofence that appears later (a new vehicle, a tracker installed afterwards), is read from this date, so choose how much history you want to keep, such as the start of the year. The other tables are always extracted in full. Required, even if you do not select Vehicle Events or Geofence Events.
  • Events Lookback Days: (Default: 2, minimum: 1) how many days are re-read before each vehicle’s and geofence’s sync point on every sync, so events that arrive late are not missed. Increase it if your trackers often stay out of coverage for several days (see Data Quality Considerations).
  • Requests Per Second: (Default: 5) the maximum number of requests per second sent to RastroSystem. Keep the default unless RastroSystem asks for a lower rate.
Once you’re done, click Next.

​
2. Select streams

Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select entire groups of streams or pick specific ones.
Tip: The stream can be found more easily by typing its name.
Vehicle Events, Geofence Events, Person Details and Equipment Details make requests per vehicle, geofence, person or tracker. On large fleets they are the slowest streams, so select them only when you need them.
Select the streams and click Next.

​
3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.
  • Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
  • Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
  • Sync Type: Vehicle Events and Geofence Events must use INCREMENTAL, which keeps the full event history and reads only new events on each sync (each vehicle and geofence keeps its own sync point). Every other stream is FULL_TABLE: RastroSystem has no “changed since” filter, so each sync reads the current state of the registry. Read more about Sync Types here.
Do not use FULL_TABLE, or a manual or additional full sync, for Vehicle Events and Geofence Events. A full sync re-reads events only from the Start Date and replaces the whole table: events older than the Start Date, and the entries and exits of geofences deleted in RastroSystem, are no longer available in RastroSystem and are removed from the table for good.
Once you are done configuring, click Next.

​
4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can define some additional settings:
  • Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
  • Do not schedule an Additional Full Sync for this source if Vehicle Events or Geofence Events are selected: as explained above, it would remove from those tables every event older than the Start Date and the history of deleted geofences. The other streams already read their full state on every sync, so they do not need it.
Once you are ready, click Next to finalize the setup.

​
5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

​
Streams and Fields

​
Available streams

The table below lists every stream, its slug (the exact identifier to pass when creating the source via API) and a short description.

​
Fields by stream

Small references (such as the owner or the vehicle group) are split into _id and _nome or _descricao columns, and the last position into posicao_* columns. Lists and free-form structures (geofence geometry, phone lists, device configuration, route stops) are JSON strings.
One row per vehicle, with its owner, tracker, default driver, group and the last position reported by the tracker.Primary key: id
Events reported by each vehicle’s tracker (ignition on/off, alarms, speeding and the other types listed in Event Types), read in date windows with one sync point per vehicle. Vehicles without a tracker are not queried.Primary key: veiculo_id, id · Replication key: data_hora
Catalogue of the event type codes used in Vehicle Events.Primary key: tipo
Drivers registered under each owner.Primary key: id
One row per alert configured on a vehicle.Primary key: veiculo_id, id
Customers, suppliers, employees, technicians, consultants and other people registered in the platform.Primary key: id
Address, phone list and employee data of each person. One request per person, so select it only when you need these fields.Primary key: id
Trackers (equipment) with their model and SIM chip.Primary key: id
Online status, last contact with the server, stock location, last position and device configuration of each tracker. One request per tracker.Primary key: id
SIM chips (data lines) used by the trackers.Primary key: id
Installation and maintenance work orders, with customer, technician, consultant, vehicle, status and dates.Primary key: id
Customer support tickets (atendimentos) with their project, status, priority and responsible user.Primary key: id
Installments the company has to receive from its customers, with amounts, due and payment dates and payment links.Primary key: id
Installments the company has to pay.Primary key: id
Virtual fences (polygons or circles) and the vehicles linked to them.Primary key: id
Entries into and exits from each geofence, read in date windows with one sync point per geofence.Primary key: cerca_id, id · Replication key: data_hora
Points of interest registered for the route planner.Primary key: id
Planned routes with their stops and vehicles.Primary key: id

​
Implementation Notes

​
Data Quality Considerations

  • Event dates (data_hora) and the dates sent to RastroSystem follow the time zone configured in your RastroSystem account.
  • RastroSystem returns a tracker’s events only since it was last moved from another vehicle, so a reused tracker does not carry the previous vehicle’s history.
  • When a geofence is deleted in RastroSystem, its entry and exit history can no longer be read; rows already in your Lakehouse are kept by INCREMENTAL syncs and lost on a full sync.
  • Each vehicle and geofence keeps its own sync point. A vehicle or geofence seen for the first time is read from the Start Date; every sync then reads from its sync point minus Events Lookback Days.
  • Trackers that lose coverage store their events and upload them later with the original date and time, so a sync point never moves past the point where late events can still arrive:
    • Vehicles: the sync point is the newest event already read. A vehicle with no new events moves at most to the day of its tracker’s last reported position, never to “today” (a position dated in the future is ignored). When the tracker comes back and uploads what it stored, those events are read on the next sync.
    • Geofences: a geofence collects entries and exits of many vehicles, so after every sync its sync point is set to 30 days ago, with or without recent movement. Entries and exits uploaded up to 30 days late are read, at the cost of re-reading about the last 30 days of each geofence on every sync. The first sync of a geofence still reads from the Start Date.
  • If a tracker returns from a long outage and sends a live event before uploading what it stored, and a sync runs in between, stored events older than that live event minus Events Lookback Days are not read. Increase Events Lookback Days if your fleet has trackers that stay out of coverage for long periods.
  • Vehicles without a tracker have no events and are not queried. When a tracker is installed, the vehicle’s events are read from the Start Date on the next sync.
  • If the user is not allowed to read the events of some vehicles, those vehicles are skipped with one warning in the run log and their sync point is kept, so their events are read once access is granted. The warning repeats on every sync while the access is missing.
  • The posicao_* columns of Vehicles and Equipment Details are a snapshot of the last position at sync time. For the history, use Vehicle Events.

​
API Limits & Performance

  • Vehicle Events, Geofence Events, Person Details and Equipment Details make requests per record, so their extraction time grows with the size of the fleet.
  • Events are requested in windows of 30 days; RastroSystem accepts at most 31 days per request.
  • If RastroSystem answers with an error page or an unexpected response, the connector retries a few times and then stops the sync, so a table is never replaced by incomplete data.
  • The connector sends at most 5 requests per second by default and waits when RastroSystem asks it to slow down.

​
Troubleshooting