GuardDog
DocumentationIntegrationsMotive
Company-specific Motive API keyManual webhook setup

Motive AI Dashcams

Connect Motive to GuardDog

GuardDog binds a company-specific Motive API key, discovers vehicles, accepts tenant-bound safety-event webhooks, verifies an optional Motive signature, and requests incident video recalls.

Open GuardDog integrationsMotive developer portal
On this page

Requirements

Prepare the provider account, permissions, and camera access before opening the integration in GuardDog.

Credentials

API key

Required

A company-specific Motive API key with company, fleet/vehicle, safety-event, and camera video-recall access.

Webhook secret

Optional

The signing secret from the Motive webhook configuration, when Motive provides one.

Provider account checklist

  • A company-specific Motive API key that resolves to exactly one company.
  • Access to company information, vehicles, safety events, and camera video recall.
  • Permission to create a safety-event webhook in Motive Settings → Developer → Webhooks.
  • At least one demo vehicle with an active Motive dashcam and available video-recall quota.

Capabilities

Device discovery

Supported

Sync Motive vehicles and stable identifiers for GuardDog unit assignment.

Safety events

Manual setup

Create a Motive safety-event webhook using the tenant-specific GuardDog URL.

Incident video

Supported

Create and poll one-minute regular video recalls around an event time.

Live video

Not available

The current GuardDog Motive integration does not start live camera sessions.

Setup guide

  1. 1

    Create the Motive API key

    In Motive Settings → Developer → API Keys, create a company-specific key with company, fleet, safety, and camera media access.

  2. 2

    Connect Motive in GuardDog

    Open Integrations, choose Motive, enter the API key and optional webhook secret, then test and save.

  3. 3

    Copy the GuardDog webhook URL

    After saving, copy the tenant-specific Motive callback URL from the integration page.

  4. 4

    Create the Motive webhook

    In Motive Settings → Developer → Webhooks, add the GuardDog URL and select safety-event delivery. If Motive supplies a signing secret, save the same value in GuardDog.

  5. 5

    Discover and assign vehicles

    Run device discovery and assign each Motive vehicle to its GuardDog unit.

  6. 6

    Verify an event and video recall

    Generate a controlled safety event or use a recent demo event, then confirm event matching and front/driver-facing video recall.

Provider configuration

  • The callback URL contains a high-entropy tenant token and must be copied exactly.
  • When a webhook signing secret is configured, GuardDog verifies the Motive signature in addition to the tenant-bound URL.
  • Use a key that resolves to one company. GuardDog rejects ambiguous multi-company bindings and locks the resolved company after connection.
  • Video recall is asynchronous and quota-consuming. GuardDog creates one regular recall centered around the incident and polls until media is ready.

Verify the integration

Complete each check before enabling the provider for production alerting.

  • CheckThe API key resolves to the intended Motive company.
  • CheckDevice discovery lists the expected vehicles and camera-capable assets.
  • CheckThe Motive webhook uses the exact GuardDog tenant URL.
  • CheckA delivered safety event maps to the correct GuardDog unit.
  • CheckThe video recall reaches a terminal available state and returns the expected camera views.

Before generating a test event: verify the GuardDog organization, branch, contacts, call settings, and provider demo account. A real event can start texts and paid calls when alerting is enabled.

Troubleshooting

The API key resolves to multiple companies+

Create a company-specific Motive key instead of using an unrestricted partner key.

No webhook events arrive+

Confirm the exact tenant-specific URL, safety-event delivery selection, and Motive webhook status.

Signature verification fails+

Confirm the same Motive webhook secret is stored in GuardDog, or remove the optional secret from both sides and reconnect.

Video recall fails or remains unavailable+

Confirm the vehicle had camera footage at the event time and check the company’s recall quota and camera position availability.