The MyGeotab platform supports several integration shapes. Choose one based on the work the customer needs to perform:

An integration can combine these patterns. For example, an Add-In can provide an interactive workflow while a server-side process synchronizes changes to another operational system.

The API exposes fleet entities and activity such as devices, users, groups, zones, trips, locations, engine measurements, faults, rules, maintenance records, electric-vehicle data, and media metadata. Availability depends on the database's features, the API user's clearances and data scope, and support for the specific method or entity.

• Use Get for bounded current-state queries.
• Use GetFeed to maintain a checkpointed stream of supported changes.
• Use the Electric Vehicles guide for electric-vehicle state and charging data.
• Use the Media Files guide for camera and other binary media workflows.

API results reflect the authenticated user's access. Test with the integration's real security model, not only with an administrator account.

Applications can connect MyGeotab to maintenance, dispatch, customer relationship management, payroll, safety, compliance, and other operational systems. Supported entities can be added, updated, or removed through the API.

The API is not a single flat data export. Entities have relationships, searches have type-specific behavior, and high-volume records require bounded queries or feeds. Read Concepts for the data model and the reliable integration guide for production patterns and common failure modes.

Add-Ins extend MyGeotab or Geotab Drive with customer-specific pages, controls, and workflows. They can use the host application context and call APIs within the signed-in user's data scope.

• Use Developing Add-Ins for the application lifecycle and configuration.
• Use Map Add-Ins to add map items and interactions.
• Use Add-In Storage for supported persistent Add-In data.
• Use Service Add-Ins for supported background behavior in the host.

A user-facing Add-In does not replace a durable server-side synchronization service. Separate interactive work from long-running feeds, analytics, and processes that must continue when no user is signed in.

The method reference describes call parameters, results, rate limits, and supported entity types. The entity reference describes fields, search objects, inheritance, and related types. Use both with the guides:

1. Choose an integration pattern and security boundary.
2. Use the reference to confirm support for each method, entity, search property, and field.
3. Build a small read-only call against a test database.
4. Add pagination, checkpoints, retries, observability, and write safeguards before production.

Keep API client packages current and review the MyGeotab release notes as part of normal maintenance.