Jul 20, 2026

Motive API: The Key Is Instant Despite What the Button Says

A driver is approaching an HOS limit; Carly can put the issue in front of dispatch while there is still time to re-plan. Motive’s fault codes, geofence arrivals, gateway and camera status, and other fleet events can likewise become shop messages, customer updates, follow-up tasks, and recurring dispatcher briefs.

Motive’s dashboard button says “Request API Key,” which makes it look like there’s a queue. There isn’t. Motive’s own developer docs walk through it: click the button, name the key or just click Save, and “You have now successfully generated an API key for yourself.” No approval, no wait.

The confusing label is the single most common reason people email Motive support instead of just clicking it. Path is Fleet Dashboard → Admin → Developers, and you need Fleet Admin rights. You can create multiple keys, and each has a Test Mode checkbox that blocks third-party writes against live data.

There is an older help article describing an API Access tab where the button emails API Support. Its screenshots are visibly dated and two of three sources describe the instant flow, so treat the email variant as legacy — but if that’s the UI your tenant shows, apisupport@gomotive.com is the escalation path.

What fleets actually automate with it

Motive pushes a lot of events, so the useful question is which ones are worth acting on:

HOS violations caught before they’re violations. A driver approaches their limit and the dispatcher finds out in time to re-plan, rather than after the log is already out of compliance.
Fault codes that reach the shop. fault_code_opened fires the moment it happens; without something listening it becomes a dashboard row nobody opens until the truck is stopped.
Geofence arrivals that update the customer automatically instead of a dispatcher typing it out.
Gateway and dashcam disconnections that get chased. A unit goes dark and you often don’t notice for days — by which point you’ve lost the footage and the tracking you’re paying for.

That last one is quietly the highest-value automation in the list, because the cost of not noticing is invisible until you need the data.

OAuth apps are self-serve too

This gets described as undocumented, and it isn’t. Sign up at developer.gomotive.com, click + Create App, open the Configuration tab, and you have a client ID and secret. Set the redirect URI, tick the permissions you need, save. There is no review step in that flow.

The approval gate people are thinking of is a different thing entirely: listing on Motive’s App Marketplace requires partner onboarding, a submission of technical, security, and business details, and access to a separate partner portal. Building for your own fleet doesn’t touch any of that.

Flow details: authorize at https://gomotive.com/oauth/authorize, exchange at https://api.gomotive.com/oauth/token. Authorization codes expire in 10 minutes, and expiry forces a full re-authorization. There are 18 permission groups.

Auth and the limits nobody published

API key via X-API-Key header for server-to-server, or OAuth 2.0 for third-party apps
Scopes are <resource>.read and <resource>.manage; every GET needs read, everything else needs write
Base URL https://api.gomotive.com/. The legacy api.keeptruckin.com still works with no announced deprecation.
Pagination: per_page defaults to 25, maxes at 100, with page_no

Motive publishes no rate limits at all. There’s no rate-limit page in the docs, and 429 doesn’t appear in the documented response codes list. You’ll find secondhand claims of “429 with Retry-After at Motive’s discretion” — that’s plausible but unverifiable from primary sources. Build in backoff regardless and don’t design against a number nobody has published.

Pricing is the same story: Motive publishes no pricing whatsoever. The pricing URL redirects to a contact form, and no Motive-owned page states which tiers include API access. Third-party review sites claim it’s Enterprise-tier at $25–35 per vehicle per month; none of that traces back to Motive. Ask your rep rather than trusting the number.

Webhooks are the strongest part of the surface

Eighteen-plus event types, and — unusually — you can create them through the API with POST /v1/company_webhooks, not just the dashboard.

The catalog: vehicle_location_updated, vehicle_location_received, vehicle_upserted, user_upserted, user_duty_status_updated, fault_code_opened, fault_code_closed, inspection_report_upserted, hos_violation_upserted, vehicle_geofence_event, asset_geofence_event, engine_toggle_event, driver_performance_event_created and _updated, aggregated driver performance events, speeding_event_created and _updated, form_entry_upserted, vehicle_gateway_disconnected, vehicle_gateway_disconnect_ended, and dashcam_disconnected.

The mechanics carry some genuine landmines:

Signatures are HMAC-SHA1 in a header called X-KT-Webhook-Signature — both KeepTruckin-era artifacts that don’t match what a modern integration expects. If you assumed SHA256, verification fails.
The response timeout is 3 seconds, and the retry ladder is 1 minute, 1 hour, 6 hours. Any synchronous processing in your handler pushes you into a six-hour hole with no dead-letter queue and no faster backoff. Acknowledge immediately, process async.
POST /v1/company_webhooks takes query parameters, not a JSON body. URL, secret, format, actions, and enabled all go in the query string. The secret must be exactly 20 characters or it’s auto-generated.
Caps: one webhook per action-and-URL pair, maximum two active webhooks per action.
Enabling fires a test request, and the webhook only activates on a 200 or 201.
Driver performance and speeding events lag the real event by a few minutes.

V2 adds AWS SQS and SNS delivery, but it “must be enabled by your Motive partner on request” — V1 is what you get by default.

What writes, and the one thing regulation blocks

Writable: users, vehicles, assets, groups and membership, geofences (circular and polygon), dispatches, dispatch locations, documents, fuel purchases, messages (single and bulk), timecards, inspection reports, external IDs, reefer temperature thresholds, user spend profiles, video recall requests, and webhooks.

Read-only: ELD devices, fault codes, scorecards, HOS, driving periods, IFTA, utilization, locations.

You cannot edit HOS logs — only submit log_suggestions. FMCSA ELD rules require that a third party can only suggest a change the driver must accept. Anyone planning to “clean up driver logs via API” is blocked by regulation, not by Motive’s product decisions.

Two write surfaces worth knowing about: the Camera Control API can remotely power both dashcams fully off, persisting across ignition cycles and reboots. And the Video Request API pulls past footage asynchronously — request, poll status, download — with a quota that needs an account rep to raise.

What “Motive AI” actually means today

The keyword is searched more than the API itself, and the easy mistake is conflating the shipped product with the announced one.

AI Answers is shipped — launched October 2025, with a 2.0 adding conversation history in April 2026. But it’s gated to Strategic, Enterprise, and Midmarket tiers, US and Canada only.
Automations is shipped and available now — trigger-based fleet workflows configurable in natural language, covering things like HOS pre-alerts, auto-assigned training, and fault-code responses.
Atlas is announced only. Unveiled May 2026, it includes a Motive MCP connector for Claude, ChatGPT, Copilot, and Gemini. Motive’s own site contradicts itself on timing — the US page says Summer 2026, the UK page says late 2026 — and there’s no live MCP endpoint today: api.gomotive.com/mcp returns a 404 identical to a nonsense control path, and MCP appears nowhere in the developer docs index.
AI Dashcam and AI Omnicam are GA; AI Dashcam Plus launched January 2026 with features staggered through the year, and AI Omnicam Plus is announced for Q4 2026.

One thing to avoid repeating anywhere: Motive’s dashcam accuracy claims have a court-ordered corrective notice on Motive’s own page, stating that its comparative accuracy claims against Samsara were ruled literally false under the Lanham Act. Separately, the “99%” figure that circulates is a G2 satisfaction score, not a detection accuracy rate. And “Motive Intelligence” isn’t a product — it’s a phantom term.

Getting the event to do something

A fault code opening, a geofence crossing, an HOS violation — Motive fires all of these reliably. What happens next is usually a notification someone reads eventually.

Handing that to an AI assistant runs into a specific limit.

Scheduled work is no longer the dividing line — ChatGPT and Claude both run tasks on a timer without anyone watching. The line that still holds is event triggers. Nothing kicks off because something happened in one of your apps; it kicks off because the clock said so, which means anything time-sensitive waits for the next run.

Motive’s own Automations cover trigger-based workflows inside Motive, which is genuinely useful. What they don’t do is reach across into your email, CRM, or task system and finish the job.

That’s where Carly fits:

Fires on the Motive webhook — fault_code_opened, hos_violation_upserted, vehicle_geofence_event
Runs the whole response in one flow — read the event, identify the driver and vehicle, draft the message, send it, open the task, update the record
Actually sends — Gmail and Outlook, with attachments
Acknowledges in time — a 3-second timeout with a 1-hour second attempt is exactly the constraint that punishes hand-rolled receivers

Because Motive exposes a public API, you can connect it natively to Carly from the Integrations tab with your API credentials. Carly can then use Motive in on-demand, recurring, and event-triggered workflows. AI agents start at $35/month, and workflow steps that don’t use AI run free and unlimited.

Frequently Asked Questions

Do I have to request a Motive API key and wait for approval?

No. Despite the button reading “Request API Key,” the flow is immediate — name the key and save, and it exists. Go to Fleet Dashboard → Admin → Developers as a Fleet Admin. Registering an OAuth app is also self-serve with no review step.

What are the Motive API rate limits?

Motive doesn’t publish any. There’s no rate-limit documentation and 429 isn’t in the documented response codes. Build in exponential backoff rather than designing against an unpublished figure.

What webhooks does Motive support?

Eighteen-plus events covering vehicle location, fault codes, HOS violations, geofences, inspections, duty status, speeding, driver performance, forms, and gateway and dashcam disconnections. They’re signed with HMAC-SHA1 in an X-KT-Webhook-Signature header, and your endpoint must respond within 3 seconds.

Can I edit driver HOS logs through the Motive API?

No. FMCSA ELD rules only permit submitting log suggestions that the driver must accept. This is a regulatory constraint, not a Motive limitation.

Is Motive’s AI agent available?

Not yet. Atlas, including its MCP connector, was announced in May 2026 but isn’t live — Motive’s own pages disagree on whether it arrives in summer or late 2026. What ships today is AI Answers, which is restricted to higher tiers in the US and Canada, and Automations, which is generally available.

Which Motive plan includes API access?

Motive publishes no pricing or tier documentation, so there’s no verifiable answer. Third-party claims that it’s Enterprise-only at $25–35 per vehicle aren’t traceable to Motive. Ask your account rep.

More: AI agents for ops · Best AI workflow automation tools · Best AI agents for productivity

Ready to automate your busywork?

Carly schedules, researches, and briefs you—so you can focus on what matters.

See what people say

"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.

Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.

On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."

Gus Ibrahim, Founder & Director, IHR