Get Inspection Details

Use the GET /v3/inspections/{inspectionId} endpoint to retrieve the complete details for a single inspection. The response includes:

• App user's personal information
• App user generated data: photos, videos, and answers to questions
• Smart link
• Truepic test results
• The timeline of all activities related to the inspection
• Inspection status
• Inspection outcome
• Alerts

To see how this data looks in practice, perform an inspection and view the results in the Vision Dashboard.

Key Response Fields

When building a workflow on top of the inspection response, the data breaks down into two levels: inspection-level intelligence that summarizes the overall risk picture, and per-photo detail that provides granular test results for each media item.

Inspection-Level Intelligence

These fields give the approver a high-level summary before examining individual photos or videos. For many workflows, these fields are sufficient to route inspections for auto-approval, manual review, or rejection.

Aggregate Verification Result

result.verification_result returns the overall verification outcome across all photos and videos in the inspection.

Use this as the initial routing signal — for example, auto-approve pass inspections, queue warn for manual review, and escalate fail.

"verification_result": "warn"

Inspection Status

result.status indicates where the inspection is in its lifecycle. Only present an inspection to an approver when it has reached the appropriate status.

"status": {
  "id": 2,
  "id_internal": "STATUS_READY_FOR_REVIEW",
  "name": "Ready for Review"
}

Alert Summary

result.alert provides the alert system's assessment of the inspection based on your configured alert thresholds. This is the most actionable inspection-level field for approver routing — it tells you what went wrong and where.

{
  "config": {
    "fail_threshold": 1,
    "warn_threshold": 1,
    "test_blurriness": true,
    "test_content_analysis_vin": true,
    "test_content_analysis_odometer": true,
    "test_content_analysis_text_matching": true,
    "test_content_analysis_dot_tin": true,
    "test_capture_integrity": true,
    "test_datetime": true,
    "test_device_integrity": true,
    "test_distance_from_address": true,
    "test_geolocation": true,
    "test_object_detection": true,
    "test_pop": true,
    "test_ris": true,
    "test_falsified_location": true,
    "test_insecure_device": true,
    "test_device_flagged": true,
    "test_device_found_other_inspections": true
  },
  "warnings": [
    {
      "photo_id": 42469794,
      "test_key": "test_content_analysis_text_matching"
    }
  ],
  "failures": [],
  "recommendation": "warn"
}

The recommendation is calculated by comparing the count of warnings and failures against the configured warn_threshold and fail_threshold. Use the warnings and failures arrays to link specific issues back to individual photos by photo_id.

Device Insights

result.insights flags risk signals detected across the inspection. These are high-level indicators that may warrant closer review.

"insights": [
  { "type": "device_found_other_inspections" }
]

Device Details

result.devices provides information about each device used during the inspection, including cross-inspection and cross-organization flag history.

{
  "id": 13193976,
  "fingerprint_id": "dpHht8M90xOiyoc9SsRW",
  "os": "iOS",
  "os_version": "18.7",
  "device": "iPhone",
  "flags": [],
  "flags_other_inspections": {
    "inspections": [],
    "flag_counts": {}
  },
  "flags_other_orgs": {
    "first_flagged_dates": [],
    "flag_counts": {},
    "org_count": 0
  },
  "other_inspections": [
    { "id": 2187527, "team_id": 20525, "assigned_to_member_user_id": 2149492 }
  ]
}

A device with flags from other inspections or organizations is a strong risk signal that warrants closer manual review.

Per-Photo Detail

Each object in result.photos contains the full set of test results, location data, and media URLs for a single captured photo or video. This is where an approver gets the detail needed to evaluate each media item individually.

Photo Status and Identity

Verification Test Results

Each photo includes a set of *_result and *_reason field pairs. The _result field contains pass, warn, fail, or null (test not run). When the result is not pass, the _reason field provides a human-readable explanation.

For a category-by-category explanation of these checks and what pass, warn, and fail mean, see Verification Tests.

A photo with status: "warn" will have at least one test with a warn result. Scan the _result fields to find which test triggered it, and display the corresponding _reason to your approver.

{
  "id": "42469794",
  "status": "warn",
  "pop_result": "pass",
  "ris_result": "pass",
  "time_result": "pass",
  "geolocation_result": "pass",
  "jailbreak_result": "pass",
  "data_result": "pass",
  "capture_integrity_result": "pass",
  "content_analysis_result": "warn",
  "content_analysis_reason": "The text detected does not match any of the expected values.",
  "object_detection_result": null
}

Content Analysis Details

When content_analysis_result is not null, the content_analysis_details object provides a full breakdown of what was expected and what was detected.

{
  "type": "TEXT_MATCHING",
  "result": [[]],
  "expected": [
    {
      "text_matching_set_id": 1002,
      "text_matching_set": {
        "id": 1002,
        "name": "Test",
        "type": "Example",
        "strings": ["Example"]
      }
    }
  ]
}

Two additional fields on the photo provide the raw detection data:

Location and Distance

Media URLs

Each photo provides multiple URLs at different resolutions. Choose the appropriate one for your approver UI:

All image URLs include a signed token that grants access for a limited time. If tokens have expired, fetch fresh URLs by re-requesting the inspection.

Device and Capture Metadata

Reading Question Responses

result.list.items contains every prompt in the inspection list, including question prompts and media prompts. To read responses to questions, find items where type is QUESTION and inspect the question.answer field on each item.

Use question.type to determine how to read question.answer:

• For MULTIPLE_CHOICE, question.answer is an array of selected choice objects.
• For TEXT, question.answer is a string.
• If question.answer is null, the customer has not submitted an answer for that question yet.

{
  "type": "MULTIPLE_CHOICE",
  "answer": [
    {
      "name": "Yes"
    }
  ]
}

{
  "type": "TEXT",
  "answer": "0825607"
}

{
  "type": "MULTIPLE_CHOICE",
  "answer": null
}

[
  {
    "id": 41500348,
    "name": "Do you understand the witnessing requirements and have you been trained in the usage of TruePic? ",
    "type": "QUESTION",
    "question": {
      "type": "MULTIPLE_CHOICE",
      "answer": [
        {
          "name": "Yes"
        }
      ]
    }
  },
  {
    "id": 41500350,
    "name": "Container inbound tag ID or Seal #",
    "type": "QUESTION",
    "question": {
      "type": "TEXT",
      "answer": "0825607"
    }
  },
  {
    "id": 41500366,
    "name": "I remained on location until all destruct material was rendered unusable?",
    "type": "QUESTION",
    "question": {
      "type": "MULTIPLE_CHOICE",
      "answer": null
    }
  }
]

If you need the current question-and-answer pairs for an inspection, result.list.items is the primary structure to read. Use result.timeline when you also need the audit trail of when a question was answered: timeline entries with action_type.id_internal: "ACTION_QUESTION_ANSWERED" include the related data.list_item_id, which you can match back to the corresponding item in result.list.items.

Linking Photos to List Items

Each photo can be connected back to the list item (the prompt) that the customer was responding to. This lets your approver see what was requested alongside what was submitted.

Cross-reference a photo's list_item_id with result.list.items to get the list item details when list_item is not embedded on the photo object. Use result.list.groups to resolve a list item's group_id to a human-readable group name.

{
  "id": 37653764,
  "name": "Photo of Logo",
  "type": "IMAGE",
  "group_id": "group_l8slhpdi9m",
  "is_required": false
}

{
  "group_l8slhpdi9m": {
    "name": "Photo of Logo"
  }
}

Next Steps

Once the data has been retrieved, you may perform subsequent actions for the inspection. Some examples include:

1. Workflow Automation. Escalating certain inspections by closing some inspections, while pushing other inspections into different queues for further assessment.
2. Data Storage. Downloading and storing the data on your own servers.
3. Performing follow-up actions, further described in the next section.

To see the full list of query params, try it out in the API Reference via Inspections > Get an existing inspection request.