Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Navixy (BYOK) — connector documentation

  • MCP endpoint: https://byok-navixy.connectorbay.com/mcp
  • REST API: POST https://byok-navixy.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-navixy.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Navixy Navixy API key (sent as 'Authorization: NVX '), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-navixy.connectorbay.com/health · Tool schemas: https://byok-navixy.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-navixy · agent@connectorbay.com

What Navixy (BYOK) is for

Navixy (BYOK) lets an AI assistant read your own Navixy data through the Navixy API with a key you supply (Navixy API key (sent as 'Authorization: NVX ')). Read-only: 12 tools (list_trackers, get_tracker_state, list_vehicles, list_service_tasks, list_tracks, get_tracker_mileage, get_tracker_engine_hours, get_tracker_fuel, get_tracker_diagnostics, list_tracker_groups, list_depots, list_tasks). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.eu.navixy.com, api.us.navixy.com, api.me.navixy.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Navixy. Navixy and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which trackers are registered in my Navixy account?"
  • "Is Navixy tracker 123456 moving and where is it?"
  • "Which vehicles are in my Navixy account?"
  • "Which Navixy vehicle service works are overdue?"
  • "What trips did Navixy tracker 123456 make last week?"
  • "How many km did Navixy tracker 123456 drive each day last week?"

What it does

  • list_trackers: List the account's GPS trackers with id, label, group, device model, blocked flag, tariff and phone-less source details.
  • get_tracker_state: Get the current state of one tracker: GPS position, speed and heading, connection status, movement status (moving, stopped, parked), ignition, GSM signal and battery level.
  • list_vehicles: List vehicles with label, linked tracker, type, model, plate, VIN, year, fuel type, tank size, depot and status. Supports a text filter and paging.
  • list_service_tasks: List vehicle service works (maintenance jobs) across vehicles: description, status (created, notified, expired, done), repeat flag, cost, completion date and start and current mileage or engine hours.
  • list_tracks: List a tracker's trips over a period with start and end time, length in km, maximum and average speed and norm fuel consumed, plus totals. Addresses are left out unless asked for; GPS points are not requested.
  • get_tracker_mileage: Get mileage in km per day for one tracker over a period. A day without data is null, not zero.
  • get_tracker_engine_hours: Get engine hours (time the engine was on) for one tracker over a period. Trackers without an ignition input answer with an error.
  • get_tracker_fuel: Get the current fuel level of the tracker's tanks from its fuel sensors, with units and update time.
  • get_tracker_diagnostics: Get the last CAN-bus and OBD readings of a tracker (engine values, odometer and similar) with labels, units and the time of the last update.
  • list_tracker_groups: List tracker groups (the default group 0 is not listed) with title and color.
  • list_depots: List depots (garages) with organization name and address; people's names are not returned.
  • list_tasks: List field tasks (jobs assigned to tracked units) with label, status (unassigned, assigned, done, failed, delayed, arrived), time window, assigned tracker, arrival time and stay duration. Locations are left out.

BYOK key

You bring your own Navixy Navixy API key (sent as 'Authorization: NVX ') (https://www.navixy.com/docs/navixy-api/user-api/getting-started). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.eu.navixy.com, api.us.navixy.com, api.me.navixy.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Navixy API (api.eu.navixy.com, api.us.navixy.com, api.me.navixy.com) with a BYOK key; documentation: https://www.navixy.com/docs/navixy-api/user-api/getting-started. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Navixy. Navixy and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Navixy account.

Built for: Worldwide. Languages: English.