Your fleet data, in your systems
Hours, faults and fuel reach your other systems without retyping.
- Go-live
- Live in 10 working days
- How you buy it
- Included in the Command plan
Engine hours live in Gytix, job cost lives in accounting, and somebody retypes one into the other every Friday. Scheduled exports end the retyping by carrying hours, fuel and work orders to accounting, and webhooks tell your other systems the moment something happens.
How integrations go live
- Days 1 to 2
Map the data flow
We list which systems need which fields, such as hours, fuel, work orders and costs, and how often.
- Days 3 to 5
Match the IDs
Gytix machines and jobs are matched to the equipment numbers, job numbers and cost codes in accounting.
- Days 6 to 8
Build the connector
We build the connector to your accounting system, by API or scheduled file, and test it on a real week.
- Days 9 to 10
First live export
Your controller checks totals against timesheets; developers get tokens, and webhooks go live.
What your systems receive
- Who it is for
- Fleets feeding accounting, job cost or in-house systems
- A connector to your accounting or job cost system, built during onboarding
- Scheduled CSV exports of hours by job, fuel, work orders and costs
- REST API access with per-user tokens that carry each user’s permissions
- Webhooks for fault codes, geofence entries and exits, and work order changes
- An MCP server that lets your AI assistant query fleet data and draft work orders
- A written API reference with examples for your developer
Do you need the API?
Right for you if
- Someone retypes hours or fuel into accounting every week
- You run an in-house dashboard, data warehouse or dispatch tool
- Your team already uses an AI assistant at work
Look elsewhere if
- Gytix’s own reports and CSV downloads already cover what you need
- You need a prebuilt listing in an accounting software marketplace
Example: a utility contractor in Odessa
A utility and pipeline contractor runs 320 machines, from mini excavators and directional drills to side booms, out of yards in Odessa and Midland. Two clerks retyped engine hours from timesheets into the job cost system every week. During onboarding we match machines to equipment numbers and jobs to cost codes, then build a nightly export of hours by job. A webhook sends critical fault codes to the contractor’s own ticketing tool. The controller connects an AI assistant through the MCP server and asks which jobs ran the most idle hours last month.
Four ways data leaves Gytix
Every surface works under the permissions of the person or token behind it.
| Surface | What it does | Access | Who it suits |
|---|---|---|---|
| REST API | Reads machines, hours, positions, fault codes, fuel, inspections and work orders; creates and updates jobs and work orders | Per-user tokens that carry that user’s permissions, revocable at any time | An in-house developer or IT contractor building reports or syncing another system |
| Webhooks | Sends an event to your address as it happens: a fault code, a geofence entry or exit, a work order opened or closed | You choose the events and the receiving address for each webhook | Teams whose dispatch, ticketing or alerting tools should react right away |
| MCP server | Lets AI assistants your team already uses query fleet data and create draft work orders | Same permissions as the user who connects it; drafts still need a person’s approval | Managers who already work in an AI assistant and want answers without another screen |
| Scheduled exports | CSV files of hours by job, fuel, work orders and costs, sent daily, weekly or monthly | Set up by an admin; files go to the destination your accounting team picks | Controllers whose accounting or job cost system imports files, with no developer needed |
Tokens, events and the connector
Per-user tokens. Every API token belongs to a person and carries that person’s permissions. A token made by a superintendent sees that superintendent’s jobs; a token made by the controller sees costs. Revoke a token and its access stops at once, and removing a user who leaves the company removes their tokens with them. Nobody shares one master key that outlives the person who made it.
Events, not polling. Webhooks send a message to an address you choose when a fault code arrives, a machine enters or leaves a geofence, or a work order opens or closes. Each message carries the machine, the job and the time, so the receiving system can act without asking Gytix again. A geofence exit can open a ticket in your dispatch tool before the lowboy reaches the highway. Your developer picks the events for each webhook.
The MCP server. The Model Context Protocol is an open standard that lets AI assistants connect to outside data and tools. Gytix’s MCP server lets the assistant your team already uses query fleet data and create draft work orders, with the same permissions as the user who connects it. A draft from an assistant waits for a person to approve it, the same as a draft from the AI maintenance agent.
The accounting connector. Most fleets do not need a developer to get hours into job cost. During onboarding we build the connector to your accounting system, through its API or as a scheduled file it already knows how to import, and match equipment numbers, job numbers and cost codes once. The steps are laid out in from engine hours to job cost.
API and integration questions, answered
Does Gytix have an open API?
Yes. The REST API reads machines, hours, positions, fault codes, fuel, inspections and work orders, and can create and update jobs and work orders. Each token belongs to one user and carries that user’s permissions. The API, webhooks and MCP server come with the Command plan.
Can Gytix send engine hours to our accounting system?
Yes. During onboarding we build the connector to your accounting system, either through its API or as a scheduled CSV file it can import. Machines are matched to your equipment numbers and jobs to your job numbers and cost codes, so hours land on the right job without retyping.
Which events can trigger a webhook?
Fault codes, geofence entries and exits, and work orders opening or closing. You choose the events and the address each webhook sends to. Every message carries the machine, the job and the time, so your dispatch, ticketing or alerting tool can act on it straight away.
What is the MCP server for?
It lets AI assistants your team already uses query fleet data and create draft work orders, using the permissions of the person who connects it. A superintendent’s assistant sees that superintendent’s jobs, nothing more. Drafts still need a person’s approval before anything changes in the shop.
How is the API priced?
The API, webhooks, MCP server and scheduled exports are part of the Command plan, billed per machine per month, month to month. The accounting connector is built during onboarding. Every plan, including Field, can download all of its data as CSV at any time. The written quote after a walkthrough on your own fleet shows the exact figure.
Tell us what you retype today
Send your fleet list. We will show api and integrations on your own machines and quote it in writing.