Device management Configure telematics hardware from multiple manufacturers in a single feature-rich interface, via API, or via SMS. Connect your GPS tracker to flespi and start managing it Configure all devices in your infrastructure from a single interface. Change common settings for multiple devices in bulk. Embed device management functionality in your solution with via REST API. Debug device connectivity issues in a handy Toolbox tool. more about device management in our kb Device management API CREATE A FREE ACCOUNT AND TRY Possible usage scenarios Remote device management via dedicated Setbox tool. Device configuration via REST API. Device management via SMS. Device management embedded into your solution. Connect your GPS tracker to flespi and start managing it Login/register Related articles Read more news

Accelerated telematics & IoT development. Leverage flespi to aggregate normalized data from a variety of IoT and telematics sources, manage devices over the air, enrich messages, and analyze data in real-time. All via API. GPS trackers IoT sensors OEM parse normalize forward calculate augment transform manage debug Your solution Azure Google Amazon Learn more about flespi dataflow Who is flespi for? IoT solutions companies to build and implement their offerings on top of flespi back-end IoT / telematics hardware manufacturers to offer API access to their device data IoT integrators / consultants to simplify the development and help their clients get to the market quicker Any companies to integrate IoT/telematics into their business. Learn more if unsure Trusted by and 300+ telematics & IoT startups We collect data from Telematics devices Connect the vehicle, asset, personal, scooter, moped, bike GPS trackers from versatile manufacturers. {TCP} {UDP} IoT sensors Add specific data from BLE tags, beacons, whatever-meters, and other sensing equipment. {MQTT} {HTTP} OEM Feed the telemetry data from the online platforms provided by various vehicle manufacturers. {API} With flespi you can Ingest data Feed the telemetry data from 1,000+ types of IoT and telematics devices by multiple manufacturers. Access normalized data via API Consume the messages in a universal JSON format with unified parameter names. Forward data to third-party platforms Establish data streaming to cloud hubs, fleet management platforms, IoT & telematics solutions, and more. Manage devices Configure different IoT and telematics devices over the air via API or using a universal configuration tool. f Calculate aggregated metrics Define custom algorithms to get meaningful summaries out of hundreds of messages. Debug & troubleshoot Use specialized tools to detect errors, diagnose connectivity issues, analyze raw traffic, and more. Visualize data Create live dashboards to monitor key metrics in real time. Learn how flespi works Get the data you need in the target downstream application or platform Including popular cloud IoT hubs Feed the normalized and pre-processed data from flespi to your solution, cloud service or specialized application. {REST API} {MQTT API} {Specialized streams} Learn more about data consumption options Learn more about data consumption options Flespi fits perfectly into versatile vertical solutions Micro-mobility services Asset monitoring Fleet management Usage-based insurance Check implemented cases here Take a few minutes to point your device to flespi and see what opportunities it has to offer Follow our quick start guide or Create a free account now Using flespi for testing and development is completely free

MQTT API Event-based alternative to the REST API with SSL-protected connections, high-precision data extraction, and no need for repeated requests. The MQTT protocol ensures fast and secure message delivery so you receive an event message in MQTT session once it appears inside the flespi platform. You can use flespi MQTT broker separately from telematics by publishing and subscribing any messages to it. MQTT broker is an efficient events bus that can interconnect software (micro-)services between each other.   flespi MQTT broker connection details Configuration Host mqtt.flespi.io Port MQTT over TCP: 8883 (SSL) or 1883 (non-SSL) MQTT over WebSockets: 443 (SSL) or 80 (non-SSL) MQTT version 3.1, 3.1.1, 5.0 QoS supported QoS 0, QoS 1 Topic you can publish messages to any topic except flespi/ Authorization Username Password ClientID your flespi token not used * any * Alternatively, if it's more convenient and secure for your client library, you can put a flespi token into the Password field instead of Username. ** For MQTT clients with a 16-byte limit on username or password fields, you may use special authorization. You may play with MQTT API using MQTT Board — client tool for MQTT debugging and testing. You can open an already preconfigured and connected instance of MQTT Board directly in flespi.io — this is the best way to do an initial investigation of the flespi MQTT API. MQTT topics Below is the list of flespi MQTT topics to get updates about events for different platform entities: Topic Description flespi/message/gw/channels/{channel_id}/{ident} New message from device identified with {ident} received by channel flespi/message/gw/devices/{device_id} New message received by device flespi/message/gw/modems/{modem_id}/{phone} SMS message from {phone} received by modem flespi/log/{api}/{origin}/{event_type} {event_type} has occurred in {origin}, see platform logs for more information flespi/state/{api}/{origin}/{id} {origin} object with default properties flespi/state/{api}/{origin}/{id}/{property} {property} changes in object of type {api}/{origin}, see objects state for more information flespi/state/gw/devices/{id}/telemetry/{parameter} Retain messages contain latest value and modification timestamp for {parameter} received by device. All new received messages by device also generate dedicated publication per each {parameter} into specified topic. flespi/state/gw/devices/{id}/settings/{name} Retain messages contain current device {name} setting value, objects state for more information flespi/state/gw/plugins/{plugin_id}/devices/{device_id} Retain messages contain plugin configuration of specified device. flespi/rest/{method}/{api-uri} Use any existing {method} to manipulate flespi instances in {api-uri}}, see REST API over MQTT for more information flespi/interval/gw/calcs/{calc_id}/devices/{device_id}/{event} Interval generated by calculator {calc_id} for device {device_id} was updated by the system. Possible {event} types are: created, deleted, updated. See flespi analytics for more information. See all MQTT topics MQTT session MQTT connection can be opened with a clean-session flag. In a clean-session mode subscriptions and undelivered messages are removed as soon as the connection to the broker closes. Non-clean session is persistent — it keeps undelivered messages and subscriptions until the new connection to the broker is established (up to 10 days). MQTT broker You can access flespi MQTT broker via special REST API to manage sessions, subscribe and unsubscribe to different topics, and even publish MQTT messages with HTTP calls. flespi objects state The topic flespi/state/{api}/{origin}/{id}/{property} contains {api} objects property values. This function is responsible for the properties that are valuable to define current state of flespi objects: name, configuration, storage buffer size, counters, etc. Usage: receive current values as retained messages on subscription; receive new property values as soon as object state changes; learn more in the corresponding blog article. REST API over MQTT Publish to topic flespi/rest/{method}/{api-uri} to perform REST API call to the flespi platform. {method} should be lowercase and valid for the specified {api-uri}. Optional data parameter may be passed as MQTT message payload. MQTT v5.0 accepts "response topic" parameter with the indication of the topic to which to publish a response to API call. Otherwise, the response is published to the same topic. Additional user property "response_cid" allows redirecting the response to another subaccount. This is a special feature helpful when you want to perform an API call on the top-level (from the master account) and redirect its result from the flespi broker directly to one of the subaccounts. One more feature is the "response_chunked" user property. If it's "true", the response will be chunked in multiple MQTT messages. A message with the specified "http_code" user property is the indication of the last chunk (message). Learn more in the corresponding blog article. Want to consume messages from flespi via MQTT? Let us tell you how to do that

API Box Test all available REST API methods, generate curl requests, preview affected items, learn about deprecated methods, and more. More details and screenshots in a dedicated article. Start exploring the flespi REST API now. Run flespi.io/docs/ Interactive Just a few mouse clicks to form the request and you see the result in an instant. Personalized Tied to your flespi account via token, API Box allows to directly communicate with all the items in your account. Caring For potentially risky requests (PUT, POST, DELETE) that can accidentally cause "harm" API Box allows to preview the list of affected items to make sure nothing unwanted happens. Neat The new interface and usability are well thought-out to make your experience highly productive. Testing REST API with pleasure Pick the flespi entity to manage, select the proper API request, configure it, and view the result. Create new items, configure the necessary fields, copy the JSON schema, get the curl, etc. Start exploring the flespi REST API with flespi.io/docs/.

REST API API to perform any operation with the flespi platform. Open API Box to delve into the API docs now. Also check our MQTT API. Flespi is a backend platform that is destined to sit under the hood of your beautiful solution. Therefore, most of the time, flespi is in itself the API. ALL operations with the flespi platform can be performed via the REST API and signed with the authorization token. Request structure curl -X [GET|POST|PUT|DELETE] --header ’Authorization: FlespiToken XXXXXX’ -d ‘[{"name":"new-name","parameter":"value"}]’ ‘https://flespi.io/resource-location-URL’ Learn how to obtain authorization token in our KB. Example 1: get the list of all registered devices curl -X get --header 'Authorization: XXXXXX' 'https://flespi.io/gw/devices/all' Example 2: create new ‘teltonika’ channel curl -X post --header 'Authorization: FlespiToken XXXXXX' -d '[{"name":"new-channel-name","protocol_name":"teltonika"}]' 'https://flespi.io/gw/channels' Example 3: delete a flespi device with specific id curl -X delete --header 'Authorization: FlespiToken XXXXXX' 'https://flespi.io/gw/devices/123456 Example 4: get latest digital inputs and position information for multiple devices selected by id curl -X get --header 'Authorization: XXXXXX' 'https://flespi.io/gw/devices/1,2,3,4,5/telemetry/position,din' Available APIs Platform API To manage your account data and authorization tokens. Gateway API To create and manage the instances of the telematics hub that jointly provide the end-to-end communication between the GPS trackers and your target application (you will need this one most of the time). Storage API To set up and manage low-level storage elements that can be used inside any telematics system. MQTT broker API To operate flespi MQTT broker via REST API. API Box is the latest version of the flespi REST API documentation perfect for finding the proper request methods, interactive testing, learning about deprecated methods, and a lot more (check the detailed API Box guide here). Interesting fact All the user-friendly tools you use to manage your flespi account — flespi panel, Toolbox, TrackIt, HelpBox, etc. — are just neatly developed customer-facing interfaces wrapped around the API. Basically, these are the living examples of applications developed on top of the flespi API;) Permissions You can use ACL tokens to grant access to the specific parts of the platform: Request limits Limits on the number of REST API calls in Free and Commercial accounts are outlined here. Want to know more about API Box functionality? Tell me more

Raw data ingestion Get telemetry data from GPS trackers, IoT devices, and platforms normalized into JSON. Create your first channel with flespi 130+ protocols Connect any of the 1000+ supported device models. 10+ platforms Inject telemetry data from third-party solutions (Webfleet, Invers, General Motors OnStar, and more). High-precision parsing engine We closely work with GPS tracker manufacturers and use our powerful proprietary protocol description language to leave no byte unparsed. Output in JSON Get clearly structured parametrized messages easy to handle in any downstream platform. Standardized parameter names We unify the naming of the most common datapoints across protocols to make consumption handier. more about channels in our kb Channels API CREATE A FREE ACCOUNT AND TRY Getting your data in flespi 1. Log in with the flespi panel. 2. Go to Telematics hub in the left-side menu -> Channels -> click “+”. 3. Pick the proper protocol depending on the hardware manufacturer; give it a name, and click Save. 4. Point your GPS tracker to the channel’s domain name:port. 5. Check the Toolbox tab for logs and messages. In case of any issues, check our troubleshooting checklist Watch how to create a channel Possible usage scenarios Stream the entire channels to target platforms. Aggregate data by device. Plug in a script. Create your first channel with flespi Login/register Related articles Read more news

Data transformation Add or remove parameters, inject data from third-party services, script custom parsing, and more. Create your first plugin with flespi Plugins are the key instance in flespi responsible for the transformation of the received message before it departs to the destination. Plugins apply to device messages. You can apply multiple plugins to a message in the specified order. Plugins can inject values obtained from third-party services, e.g. geocoding or LBS data. You can request the development of a custom plugin to meet your specific business needs. More about plugins in our KB Plugin types Plugin type Description Type item-fields add static fields to the designated item, some of the fields can be stored as message parameters Add params item-telemetry add cached telemetry values in place of missing device message parameters Add params msg-expression add new message parameters as a result of evaluating expressions Add params msg-geofence detect if the position from a given device message is inside a specified list of geofences; add parameters with the status (in/out) and geofence name to the device message Add params msg-erase remove the listed parameters from the message Delete params msg-copy copy device messages to another device Copy message msg-pvm-code execute PVM code to process the message Custom parsing msg-cancel prevent device message registration Delete message msg-dtc-decoder add a human-readable description of DTC code into the message DTC decoder msg-param-calibrate convert value with a stepwise linear function Convert params google-reverse-geocoding resolve the position address using Google reverse geocoding and add it to the message Geocoding nominatim-reverse-geocoding resolve the position address using Nominatim reverse geocoding (OSM) and add it to the message. Public and private servers supported. Geocoding here-reverse-geocoding resolve the position address using Here reverse geocoding and add it to the message Geocoding wialon-reverse-geocoding resolve position address using reverse Gurtam Wialon geocoding and add it to the message Geocoding locationiq-reverse-geocoding resolve position address using reverse LocationIQ geocoding and add it to the message Geocoding gisgraphy-reverse-geocoding resolve position address using reverse Gisgraphy geocoding and add it to the message Geocoding google-wifi-geolocation resolve Wi-Fi router MAC address information into location data using Google Wi-Fi Geolocation API and add them to the message Geocoding wialon-lbs-geocoding resolve position coordinates using LBS Wialon geocoding and add them to the message LBS unwiredlabs-geocoding resolve position coordinates using Unwiredlabs geolocation API and add them to the message LBS wialon-overspeeding-plugin detect speed limits using Wialon API and add them to the message Add params We regularly add new plugins to the list. Follow the “plugins” tag on our forum to keep updated about all plugin-related news Plugins API CREATE A FREE ACCOUNT AND TRY Possible scenarios Add, remove, or replace message parameters Add reverse geocoding data into messages Configure custom parsing logic for message payload Add geofence status into messages Add LBS data into messages Add Wi-Fi-based geolocation into messages Create your first plugin with flespi Login/register Related articles Read more news

Devices Protocols Manufacturers Devices Explore hundreds of types of IoT and telematics hardware ready to connect to flespi. Filter devices by name or tags. Learn their specs, find out usage specifics, explore all supported settings for remote configuration. If you don't see the desired device in the list, request on-demand integration.

About us Easy telematics. From developers to developers. flespi is an innovative backend platform by Gurtam, a company with more than 20 years of best software engineering practice in the area of GPS tracking. Years of experience developing Wialon cloud solution now operating on hundreds of servers and processing real-time data from over 3 million connected vehicles equipped us with a unique expertise. Every architecture idea that we put into the flespi platform and every piece of code we develop stem from that priceless background. Get to know more about the flespi brand in our presentation. 20 years of experience 12 team members 1 ambitious idea Our mission We make technologies closer to businesses and widely available. We simplify the use of telematics services inside any software to spread them faster, thus making telematics itself more useful to people in all application areas. Our philosophy keep it simple flespi platform relieves you from significant investments in R&D and offers you to start using telematics data for the good of your business. keep it speedy Fast integration. Quick data parsing. Instant economic effect. keep it flexible Unified data communication protocol eliminates any dependencies on specific hardware, protocols, and business software – no limits for roaring success. Our history Driving innovations is what Gurtam began with and made a lifelong focus on. Since the company foundation solutions by Gurtam were ahead of their time, but we never stopped seeing beyond. Progressive concepts and accumulated experience materialized in the new type of telematics product. Every breakthrough from entering the market with the first web-based solution in 2006 and Wialon SDK release in 2012 guided us on the way to flespi – the new product for the telematics IoT market. 2006 – First web-based solution on the market We were the first on the telematics market to deliver web-based GPS tracking software. In the market saturated with server-based solutions, we offered real-time vehicle movements and mapping information in a web browser. Today about 95% of telematics software is pure web services. 2009 – First SaaS distribution mode First-ever we employed the SaaS model to offer telematics software to system integrators. SaaS term became known and widespread a few years later. Now SaaS distribution model is widely used by software development companies to speed-up sales, maintain predictable revenue, provide instant updates and support. 2012 – First opened API for third-party developers We were the first on the market to make a step towards third-party software developers and start delivering Wialon software as a frontend and a backend available via API. We also made all backend API open and documented. Today Wialon is the only GPS tracking system in the world with 100% features available to third-party developers via API. Now integrations with ERP systems and third-party applications are one of the major requirements for any large-scale project. 2017 – flespi – a new breakthrough by Gurtam With a brand new flespi platform Gurtam is a pioneer in the yet unknown market sector, where telematics data is to be consumed not by the humans but the applications. flespi offers an extensive DIY kit for developers to build customized telematics and IoT solutions with minimal efforts to technical aspects and maximum focus on the business goals. 2018 – First MQTT 5.0-compliant broker on the market flespi MQTT broker becomes the first to support all key features of the new MQTT 5.0 specification. Written in pure C the broker proves to be the best-performing solution of the kind. 2021 – First to offer a real-time telematics data enrichment technology Plugins in flespi offer rich post-processing capabilities for device messages before they are saved in the database. Plugins also accept scripts written in a special PVM language. Excerpts of PVM code allow describing custom data processing and transformation logic to bring the telematics messages to the desired form most suitable for the downstream platforms. 2023 – First to offer AI assistance in dealing with Telematics hardware and software services We were the pioneers in the Telematics industry to apply generative AI capabilities to the knowledge we had accumulated over the years in the Telematics realm and provided such a consulting tool to our users. 2024 – First million devices We’ve joined the 1 million devices club! Another historic date for us—September 4th, 2024—when we connected our first million devices. Aliaksei Shchurko Chief Gurtam Architect Aliaksei started an IT outsourcing business in 2002 as a student. Four years later he joined forces with his father to develop a unique satellite tracking system as their product. After a few initial iterations, the new product was introduced to the market under the brand name Wialon. Being the first web-based solution of its kind Wialon took the global lead within several years. Gurtam team piloted by Aliaksei from the start has grown from 3 co-workers to more than 300 high-skilled IT professionals. Innovations and technologies have always been the key to success, allowing us to stay far ahead of most competitors every time we create something new. Today Aliaksei and a dedicated part of the Gurtam development team are approaching the edge market of IoT and vehicle telematics with a flespi platform. Initially driven by simplicity to widespread telematics everywhere it's now a powerful tool offering wide telematics data pre- and post-processing capabilities and used by hundreds of companies worldwide. flespi is a team We are not just faceless skillsets but bright personalities with passions and desires together performing the symphony of our brand Contact us You're always welcome at our HQ in Lithuania! Ozo g. 12A, Vilnius, 08200 Vilniaus m. sav. Also you can find us online:

Downstream integrations Send telematics data to cloud hubs, fleet management platforms, and other services. Create your first stream with flespi Forward normalized telemetry data to multiple destinations in seconds. If the destination is unavailable, streams use a buffer to temporarily store the messages to be sent. Streams are not the only option to get data from flespi — you can also use REST or MQTT API. more about streams in our kb Destination platforms   Target platform Destination type Amazon AWS IoT Cloud services Microsoft Azure IoT Cloud services Google IoT Cloud Cloud services Wialon Fleet management GPSWOX Fleet management Mapon Fleet management Navixy Fleet management Traccar Fleet management GpsGate Fleet management Key Telematics Fleet management Fleetbase Fleet management Ruhavik GPS tracking Maxoptra Telematics & IoT platforms Thingsboard Telematics & IoT platforms GEFCO Logistics platforms Redlist Maintenance platforms BG Toll National toll road systems e-Toll Poland National toll road systems SENT-geo The National Revenue Administration monitors road and rail transport using the SENT (System for Electronic Transport Supervision) IT system. Pulsar MQTT broker RabbitMQ MQTT broker HTTP Generic MQTT Generic flespi gateway Generic Wialon Retranslator Generic AWS S3 Storage External storage Streams API CREATE A FREE ACCOUNT AND TRY Possible usage scenarios Forward data to major cloud platforms: Google IoT Hub, Amason AWS, Microsoft Azure IoT. Forward data to telematics and IoT platforms: Wialon, Thingsboard, Maxoptra. Forward data via generic HTTP and MQTT protocols. Create your first stream with flespi Login/register Related articles Read more news