Loading...

Device API Access, Command Search, and 17 New GPS Brands

Quickly finding trackers that use a particular command and connecting their data to an authorized application simplifies work for integrators and fleet administrators. This Plaspy update adds device search by commands, API key generation for administrators of their own account, corrected filtering for brand names containing spaces, and compatibility with 17 additional GPS tracker brands.

Search devices by commands

Device management can now search trackers using their configured command information. This function helps when an account contains many devices and a technician needs to identify those that share an instruction or related configuration.

Instead of opening every device individually, users can apply command criteria to narrow the list and focus on relevant trackers. This is useful for preparing a review, checking a template, or locating devices that support a particular action.

A search match does not confirm that every device can execute the command in the same way. Technicians must verify the model, protocol, exact text, channel, and manufacturer documentation before sending an instruction.

API key for account administrators

Users who administer their own account can generate an API key for accessing their devices through an authorized integration. The API allows an external application to query or process information within the granted scope without using the main sign-in password as the integration credential.

What can a business do with API access?

  • Retrieve authorized device data from its own application.
  • Integrate tracking information into an operations dashboard.
  • Automate processes that need positions or states supported by the API.
  • Connect Plaspy with controlled analysis or response workflows.

The API key must be treated as a secret credential. It should not be published in web pages, repositories, screenshots, or messages. Integrations should store it securely, grant only necessary access, handle errors, and follow current documentation. If exposure is suspected, the administrator should replace the key through the available options.

The API only provides information available in Plaspy and permitted by the applicable access. Position frequency and quality still depend on trackers and their connectivity.

Brand filter for names containing spaces

The device-brand filter was corrected for names containing spaces. Users can consistently find brands such as Fortuna Impex or GenX Mobile without the separation between words preventing results.

This correction improves equipment selection in catalogs and accounts containing several manufacturers and reduces the chance of assuming that a brand is unavailable simply because it has a compound name.

17 additional compatible GPS tracker brands

Plaspy expanded its catalog with the following brands:

  • AoYa
  • Apello
  • Aquila
  • Arusnavi
  • Falcom
  • Flextrack
  • Fortuna Impex
  • GenX Mobile
  • Goome
  • Homtecs
  • Huabao
  • Neomatica
  • NVS
  • Sentar
  • Supermate
  • ThinkRace
  • Zilogic

The expanded catalog gives customers more options when they already own trackers or are evaluating hardware for vehicles, people, and other assets. An integrator can find the brand, identify a compatible model, and configure it to transmit to Plaspy.

Compatibility must be confirmed by model and protocol, not only by brand name. Two devices from the same manufacturer may use different formats, sensors, or commands. Before installation, verify the exact model, identifier, communication parameters, and functions required by the customer.

Real-world application

A company adds trackers from several manufacturers. Its integrator filters the catalog by brand, including compound names, registers compatible models, and uses command search to find devices that share a validated instruction.

The administrator generates an API key for an authorized internal dashboard that retrieves permitted devices. The dashboard can present operational information without storing the account's main password, while Plaspy remains the source of received tracking data.

Technical summary for users and integrators

  • Device search using configured command information.
  • API key generated by administrators of their own account for access to authorized devices.
  • Corrected brand filtering for compound names containing spaces.
  • Compatibility added for 17 GPS tracker brands.
  • Support must be verified for the required model, protocol, sensors, and commands.
  • The API key must be protected as a credential and limited to authorized use.

Plaspy combines GPS tracking, tracker management, commands, an API, maps, history, alerts, and statistics to connect vehicles, people, and assets with operational processes. Explore Plaspy plans and features to review the capabilities currently available.