Complete iQ Inspect

Integrations

Connect inspections to the systems you already use

Start in the dashboard with no integration at all. When you're ready, a documented REST API, signed webhooks and an MCP server put inspections inside your claims workflow.

Self-inspection

Claim CLM-1042 · Jordan Lee

Report ready
  1. Link sent by SMS
  2. Opened by claimant
  3. Photos submitted · 19 photos
  4. Report ready · VIN matches claim

Photos

  • Front left
  • Driver side
  • Rear left
  • +16 more

Each step can update your claims system automatically

View report
Illustrative example

Three ways to connect

Built for claims systems, fleet tools and AI agents

  • REST API

    Create vehicle inspections, check their status, and pull the released report, the PDF and every photo.

  • Signed webhooks

    Get notified as inspections are opened, submitted, analyzed and triaged, with an HMAC signature on every delivery.

  • MCP server

    Let AI agents and assistants create inspections and read results through the Model Context Protocol.

REST API

Create an inspection with one request

Send the claim number and the claimant's name and contact details. The response includes the inspection ID and status, and the link goes out by text or email.

Public API endpoints
Endpoint What it does
POST /api/v1/inspections Create an inspection and send the link by text, email or both.
GET /api/v1/inspections/{id} Status, submission time, sufficiency result and links to results.
GET /api/v1/inspections/{id}/report The released report as structured JSON.
GET /api/v1/inspections/{id}/report.pdf The released report as a PDF with photos.
GET /api/v1/inspections/{id}/photos Photos with short-lived download links, AI analysis and location.
GET /api/v1/inspections/{id}/photos.zip Every photo, including supplements, in one ZIP file.
GET /api/v1/templates Your organization's inspection templates.

Keys are scoped to your organization and to read or write access. Requests are rate limited, and create calls accept an Idempotency-Key header.

Webhooks

Know the moment something changes

Every delivery includes a unique delivery ID, a timestamp and an HMAC-SHA256 signature. Failed deliveries are retried with increasing delays, so a brief outage on your side doesn't lose events.

  • inspection.created An inspection request was created.
  • inspection.opened The recipient opened the inspection.
  • inspection.submitted The inspection was submitted.
  • inspection.analyzed AI analysis finished.
  • inspection.sufficiency_completed The sufficiency review finished.
  • inspection.supplement_created A follow-up photo request was created.
  • inspection.triage.completed Express triage produced a result.
  • turnaround.completed A fleet condition check was submitted with its verdict.

MCP server

Ready for AI agents

The Complete iQ MCP server gives AI assistants and agent frameworks the same capabilities as the REST API, with the same keys, scopes and rate limits.

  • create_inspection Create an inspection and send the link.
  • get_inspection Check status and get result links.
  • get_inspection_report Read the released report.
  • list_inspection_photos List photos with download links.
  • list_templates List available templates.

Integration questions

Do we need to integrate before we start?

No. Most teams start in the web dashboard. The API, webhooks and MCP server are there when you're ready to connect your claims, policy or fleet systems.

How does authentication work?

Your administrators create API keys for your organization, each with read or write scopes. The full key is shown once, and only a hash of it is stored.

How do we verify webhooks?

Each delivery carries a timestamp and an HMAC-SHA256 signature made with your webhook secret. Check the signature and reject old timestamps to block replays. Failed deliveries are retried with increasing delays.

Can we retry a request safely?

Yes. Send an Idempotency-Key header when you create an inspection, and a retried request returns the original result instead of creating a duplicate.

Which claims systems do you work with?

Any system that can make HTTPS requests and receive webhooks. Tell us what you use and we'll talk through the integration during your demo.

When is a report available through the API?

After an administrator releases it. Until then, report endpoints return a clear not-released response, so unreviewed results never leave your organization by accident.

Talk through your integration

Tell us which systems you use and how inspections fit your workflow, and we'll show you what connecting looks like.

Choose which optional cookies we may use. Your choice is saved in this browser.