Inspection Types

Inspection types define the configuration Vision applies when you create an inspection.

An inspection type acts as a reusable template for a category of inspections. When you create an inspection, the inspection_type_id determines which custom fields, list, message templates, alerts, outcomes, address rules, geofencing rules, and language settings apply.

What an inspection type controls

Use the Vision Dashboard to configure inspection types. Use the API to retrieve inspection type configuration and apply it when creating inspections.

How inspection types affect inspection creation

When you create an inspection with POST /v3/inspections, include the inspection_type_id for the inspection type you want to use.

Vision uses that inspection type to determine:

1. Which custom field values you must provide in custom_field_values.
2. Which default list to include when include_list is true.
3. Which message template set is used if Vision sends SMS or email communications.
4. Which alert configuration produces automated recommendations.
5. Which outcome set is available when the inspection is closed.
6. Whether the customer address is required.
7. Whether geofencing rules apply.
8. Which language is used for customer-facing messages.

Custom fields

Every inspection type must define at least one custom field. Custom fields collect business-specific values your organization needs before creating an inspection, such as a claim number, policy number, account ID, or vehicle identifier.

An inspection type can include any number of additional custom fields. Each custom field can be required or optional, and each field defines how the value should be entered.

Vision supports these custom field entry methods:

Use GET /v3/inspection-types to retrieve inspection types and their custom_fields metadata. This lets your integration render the fields required for a selected inspection type before calling POST /v3/inspections.

Custom fields do not include a separate order property. Render the fields in the order they appear in the custom_fields array, and send values in that same order in custom_field_values when creating the inspection.

Selectable fields are primarily configured and managed in the Vision Dashboard. In the Dashboard, they appear as dropdown fields with predefined options.

Teams

Inspection types are assigned to teams. Team assignment controls which teams can use the inspection type when creating inspections.

When you create an inspection, provide a team_id and an inspection_type_id that are valid together. The team controls customer-facing branding, sender configuration, reminders, and other team-level settings. The inspection type controls the inspection-specific configuration described on this page.

See Teams for more about team-level configuration.

Lists

An inspection type can define a default list. A list is the set of photos, videos, and questions the customer must complete during the inspection.

When you create an inspection with include_list: true, Vision includes the default list from the inspection type unless you provide a custom list object in the request. Use a custom list when the requested items vary per inspection.

See Lists for list structure and examples.

Message template sets and language

The inspection type determines which message template set Vision uses for customer communications. Message template sets define the SMS and email content used for events such as the original inspection request, reminders, and requests for more photos or videos.

The inspection type also includes the language used for customer-facing messages. Use this setting to align the inspection's communications with the intended customer language.

See Message Template Sets for more about customer communication templates.

Alerts

An inspection type can include an alert configuration. Alert configurations define which tests are evaluated and how warning and failure thresholds produce an automated recommendation when the inspection is complete.

Use alert recommendations to route inspections for manual review, automate clean outcomes, or identify inspections that need follow-up.

See Alerts for alert configuration details.

Outcomes

An inspection type can include an outcome set. Outcome sets define which outcomes can be assigned when the inspection is closed, such as approval, rejection, or re-inspection decisions.

See Outcomes for details on configuring and assigning outcomes.

Address requirements and geofencing

An inspection type can require a customer address. When address is required, include the customer's address when creating the inspection.

Inspection types can also configure a maximum distance from the provided address. This geofencing setting controls how far from the address the customer can be when completing the inspection.

Use address and geofencing settings when inspection location matters, such as confirming that photos or videos are captured near a property, vehicle, or other expected location.

Name field behavior

Inspection types can control whether the customer name is collected as separate first and last name fields or as a single name field.

When use_single_name_field is true, provide customer_name when creating the inspection. Otherwise, provide customer_first_name and customer_last_name.

Related API endpoints

Use these endpoints when working with inspection types:

What to read next