Geotab website screenshot

Geotab

Geotab is a fleet telematics platform providing the MyGeotab SDK and REST API for vehicle tracking, driver behavior monitoring, fuel management, ELD compliance, and route optimization. The MyGeotab API uses JSON-RPC 2.0 over HTTPS with session-token authentication, exposing a single versioned endpoint at /apiv1 that supports Get, Add, Set, and Remove operations across all fleet entities including devices, trips, fault data, and status data. The MyAdmin API provides reseller and partner access to manage databases, orders, and provisioning. Native SDK clients are available for JavaScript, .NET, Java, and Python, and the full SDK and sample code are published on GitHub.

Geotab publishes 5 API contracts indexed on the APIs.io network, including Authentication API, Invalid Records API, Records API, and 2 more. Tagged areas include Fleet Management, Telematics, Vehicle Tracking, ELD Compliance, and Driver Behavior.

The Geotab catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

Geotab’s developer surface includes authentication, documentation, engineering blog, pricing, and 13 more developer resources.

36.9/100 thin ▬ flat Agent 32/100 agent ready Front door AI 5/6 prominent Heartbeat 92/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →
AccessPaid
1 published contract
Fleet ManagementTelematicsVehicle TrackingELD ComplianceDriver BehaviorFuel MonitoringRoute OptimizationGPS TrackingIoT

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Vehicle Connected Services Management
BC-3460
Records
POST /records

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site. Kin Score badge preview for Geotab It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/geotab/"><img src="https://apis.io/badge/geotab/card.svg" alt="Geotab on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
  • MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
  • Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
  • A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
  • Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
  • Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
  • Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks
7 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/geotab/apis.yml: open an issue on github.com/api-evangelist/geotab to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

MarketPositionDepthRegistered MCP serverDeclares compatibility
Automotive and Mobility gravity 57.0 - -
TX-RAMP Certified Cloud Products (Texas DIR) gravity 57.0 - -
FMCSA Registered Electronic Logging Devices gravity 57.0 - -

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

measured — observed by APIs.io (published)

APIs 5

Individual APIs this provider publishes, each with its own machine-readable definition.

MyGeotab API

The MyGeotab API provides JSON-RPC 2.0 access to all fleet telematics data including vehicle location, trip history, driver behavior, fault codes, fuel usage, HOS/ELD compliance...

MyAdmin API

The MyAdmin API provides reseller and partner access to Geotab's administrative platform for managing databases, device provisioning, orders, billing, and account management. Ac...

Geotab Authentication API

The Authentication API from Geotab — 3 operation(s) for authentication.

Geotab Invalid Records API

The Invalid Records API from Geotab — 1 operation(s) for invalid records.

Geotab Records API

The Records API from Geotab — 1 operation(s) for records.

Open Collections 3

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Geotab API pricing

Not yet checked against Geotab's own pricing page. Compiled by API Evangelist on 2026-06-12 from www.geotab.com/software-packages/; confirm before you rely on a figure.

PlanPrice
GO Core Plan paid —
GO Plan paid —

Plan details, limits and sources →

Billed by: Vehicle/Month · FinOps profile →

Pricing Plans 1

Published pricing tiers and plan structures.

Geotab Plans Pricing

2 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Geotab Rate Limits

0 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Geotab

SLA

FinOps 1

Cost, billing, and metering signals for API financial operations.

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Geotab Context

0 classes · 47 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Geotab — jsonschema rules

5 rules · 4 warnings 1 info

SPECTRAL

JSON Schema 2

Standalone JSON Schema definitions for this provider's data models.

GpsRecord

16 properties

JSON SCHEMA

StatusRecord

5 properties

JSON SCHEMA

Examples 2

Example request and response payloads for these APIs.

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Geotab Authentication

http · 1 scheme

SECURITY

Geotab Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Geotab Vulnerability Disclosure

no policy recorded

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Geotab Agentic Access

5 operations · 4 acting · 1 human-in-the-loop

5 operations · 4 acting

AGENTIC

Resources

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Other 2

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: geotab
name: Geotab
type: Index
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/geotab.png
url: https://raw.githubusercontent.com/api-evangelist/geotab/refs/heads/main/apis.yml
created: 2026-06-12
modified: 2026-06-12
specificationVersion: '0.23'
description: 'Geotab is a fleet telematics platform providing the MyGeotab SDK and REST API for vehicle tracking, driver behavior
  monitoring, fuel management, ELD compliance, and route optimization. The MyGeotab API uses JSON-RPC 2.0 over HTTPS with
  session-token authentication, exposing a single versioned endpoint at /apiv1 that supports Get, Add, Set, and Remove operations
  across all fleet entities including devices, trips, fault data, and status data. The MyAdmin API provides reseller and partner
  access to manage databases, orders, and provisioning. Native SDK clients are available for JavaScript, .NET, Java, and Python,
  and the full SDK and sample code are published on GitHub.

  '
tags:
- Fleet Management
- Telematics
- Vehicle Tracking
- ELD Compliance
- Driver Behavior
- Fuel Monitoring
- Route Optimization
- GPS Tracking
- IoT
tags_raw:
- Fleet Management
- Telematics
- Vehicle Tracking
- ELD Compliance
- Driver Behavior
- Fuel Monitoring
- Route Optimization
- GPS Tracking
- IoT
- Fleet
apis:
- aid: geotab:mygeotab-api
  name: MyGeotab API
  type: REST
  description: 'The MyGeotab API provides JSON-RPC 2.0 access to all fleet telematics data including vehicle location, trip
    history, driver behavior, fault codes, fuel usage, HOS/ELD compliance records, and sensor data. It supports GetFeed for
    real-time data streaming and batch retrieval operations.

    '
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://developers.geotab.com/myGeotab/introduction/
  baseURL: https://my.geotab.com/apiv1
  tags:
  - Fleet Telematics
  - Vehicle Data
  - GPS
  - ELD
  properties:
  - type: Documentation
    url: https://developers.geotab.com/myGeotab/introduction/
  - type: APIReference
    url: https://geotab.github.io/sdk/software/api/reference/
  - type: JSONSchema
    url: json-schema/geotab-gps-record-schema.json
  - type: JSONSchema
    url: json-schema/geotab-status-record-schema.json
  contact:
  - FN: Geotab Developer Support
    url: https://developers.geotab.com/
- aid: geotab:myadmin-api
  name: MyAdmin API
  type: REST
  description: 'The MyAdmin API provides reseller and partner access to Geotab''s administrative platform for managing databases,
    device provisioning, orders, billing, and account management. Access requires a MyAdmin account with the MyAdminApiUser
    role.

    '
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://developers.geotab.com/myAdmin/introduction/index.html
  baseURL: https://myadmin.geotab.com/v2/MyAdminApi.ashx
  tags:
  - Fleet Management
  - Reseller
  - Administration
  - Provisioning
  properties:
  - type: Documentation
    url: https://developers.geotab.com/myAdmin/introduction/index.html
  - type: RateLimits
    url: https://developers.geotab.com/myAdmin/guides/rateLimits/
  contact:
  - FN: Geotab Developer Support
    url: https://developers.geotab.com/
- aid: geotab:geotab-authentication-api
  name: Geotab Authentication API
  description: The Authentication API from Geotab — 3 operation(s) for authentication.
  humanURL: https://developers.geotab.com/myGeotab/introduction/
  baseURL: https://my.geotab.com/apiv1
  tags:
  - Authentication
  properties:
  - type: OpenAPI
    url: openapi/geotab-authentication-api-openapi.yml
  - type: Examples
    url: examples/geotab-dig-authenticate-example.json
  - type: Examples
    url: examples/geotab-dig-records-example.json
- aid: geotab:geotab-invalid-records-api
  name: Geotab Invalid Records API
  description: The Invalid Records API from Geotab — 1 operation(s) for invalid records.
  humanURL: https://developers.geotab.com/myGeotab/introduction/
  baseURL: https://my.geotab.com/apiv1
  tags:
  - Invalid Records
  properties:
  - type: OpenAPI
    url: openapi/geotab-invalid-records-api-openapi.yml
  - type: Examples
    url: examples/geotab-dig-authenticate-example.json
  - type: Examples
    url: examples/geotab-dig-records-example.json
- aid: geotab:geotab-records-api
  name: Geotab Records API
  description: The Records API from Geotab — 1 operation(s) for records.
  humanURL: https://developers.geotab.com/myGeotab/introduction/
  baseURL: https://my.geotab.com/apiv1
  tags:
  - Records
  properties:
  - type: OpenAPI
    url: openapi/geotab-records-api-openapi.yml
  - type: Examples
    url: examples/geotab-dig-authenticate-example.json
  - type: Examples
    url: examples/geotab-dig-records-example.json
common:
- type: CapabilityMap
  url: capabilities/geotab-capability-edges.yml
  name: Geotab Business Capability Map
- type: AgenticAccess
  url: agentic-access/geotab-agentic-access.yml
- type: VulnerabilityDisclosure
  url: security/geotab-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/geotab-domain-security.yml
- type: Authentication
  url: authentication/geotab-authentication.yml
- type: Website
  url: https://www.geotab.com/
- type: Documentation
  url: https://developers.geotab.com/
- type: GitHubOrganization
  url: https://github.com/Geotab
- type: LinkedIn
  url: https://www.linkedin.com/company/geotab
- type: X
  url: https://x.com/geotab
- type: Blog
  url: https://www.geotab.com/blog/
- type: Pricing
  url: https://www.geotab.com/software-packages/
- type: Plans
  url: plans/geotab-plans-pricing.yml
- type: RateLimits
  url: rate-limits/geotab-rate-limits.yml
- type: FinOps
  url: finops/geotab-finops.yml
- type: Vocabulary
  url: vocabulary/geotab-vocabulary.yml
- type: JSONLDContext
  url: json-ld/geotab-context.jsonld
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Geotab API — frequently asked questions

Does Geotab have an API?

Yes. APIs.io lists 5 APIs from Geotab, including MyGeotab API, MyAdmin API and Geotab Authentication API, and 2 more.

Is there an OpenAPI specification for the Geotab API?

Yes. APIs.io indexes 3 OpenAPI specifications for Geotab, each linked for download from this page.

How do I authenticate with the Geotab API?

Geotab uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Geotab Authentication.

How much does the Geotab API cost?

APIs.io lists 2 pricing plans for Geotab, with each plan's price, limits and inclusions under Pricing on this page.

Is the Geotab API ready for AI agents?

Geotab has a Kin Score of 36.9 out of 100 (thin) and an Agent Readiness score of 32.0 (agent-ready), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/geotab"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/geotab/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/geotab/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.