Inspections are field records created when a technician inspects a piece of equipment at a site using a checklist template. Each inspection tracks its status through a review workflow and accumulates findings — discrete observations with severity ratings.Documentation Index
Fetch the complete documentation index at: https://developers.novala.ai/llms.txt
Use this file to discover all available pages before exploring further.
The inspections API requires the
calso module to be enabled for your tenant. Requests made without the module active will return 403 Forbidden.Inspection statuses
An inspection moves through the following lifecycle:| Status | Meaning |
|---|---|
draft | Created, not yet submitted by the technician. |
submitted | Submitted by the technician for review. |
in_review | Under review by a coordinator or manager. |
approved | Inspection approved. |
delivered | Report delivered to the customer. |
rejected | Returned to the technician for corrections. |
Finding severities
| Severity | Meaning |
|---|---|
imminent | Requires immediate action; equipment should be taken out of service. |
serious | Significant deficiency requiring prompt repair. |
minor | Low-risk observation; should be addressed in routine maintenance. |
List inspections
GET /api/inspections
Returns a paginated list of inspections for the authenticated tenant.
Query parameters
Filter by inspection status. One of:
draft, submitted, in_review, approved, delivered, rejected.Filter by technician UUID. Returns inspections where the user is the lead technician or a team member.
Filter by company (customer) UUID.
Full-text search across company name, equipment type name, technician name, and serial number.
1-based page index.
Results per page. Maximum
100.Response
Get an inspection
GET /api/inspections/{id}
Retrieves a full inspection record including equipment details, checklist template, findings with photos, and the technician team.
Path parameters
UUID of the inspection.
Response fields
Equipment with
id, manufacturer, model, serialNumber, ratedCapacity, status, nameplatePhotoUrl, locationLabel.Equipment type with
id, name, category, oshaStandard.Site with
id, name, address, city, state.Company with
id and name.Lead technician with
id, name, email.Checklist template with
id, name, and sections.Array of team members with
id, technicianId, role (lead or member), and name.Create an inspection
POST /api/inspections
Creates a new inspection in draft status. The inspection is assigned to the authenticated user unless a technicianId (or technicianIds) is specified, which requires the Admin or Coordinator role.
Request body
UUID of the equipment to inspect.
UUID of the site where the inspection takes place.
UUID of the checklist template to use. Must belong to your tenant.
Date of inspection in
YYYY-MM-DD format.Pre-inspection notes.
UUID of the lead technician. Only honored when the caller has the
system_admin or field_coordinator role.Array of technician UUIDs. The first element is the lead; subsequent elements are team members. Takes precedence over
technicianId.Response
Returns201 Created with the new inspection object (without nested relations). Initial status is always draft.