Key takeaways
- Signed, retrying webhooks fire on completion.
- Versioned REST API covers the full object model.
- Zapier and Make cover no-code use cases.
- You can start manual and formalise later without rework.
Webhooks in real time
The moment an inspection completes, a webhook fires with the full payload — metadata, media URLs, verification results, and audit trail. Route it into your CRM, claims platform, loan origination system, or dealer management system.
Payloads are signed so your endpoint can verify authenticity, and delivery retries on failure.
REST API
Full programmatic access to templates, inspections, sessions, media, and audit logs. Documented, versioned, and rate-limit aware.
Typical uses: create inspections from your own system, poll status, and pull signed report PDFs into your document store.
No-code connectors
Zapier and Make connectors let non-developers wire inspections into Google Drive, Slack, HubSpot, Salesforce, Airtable, Notion, and hundreds more without engineering time.
A pragmatic rollout order
Most teams start manual, move to a Zapier flow within a week, and graduate to signed webhooks once volume justifies it. Nothing about the data model changes between those stages.
Keep reading
People also ask
- Do you have a Salesforce integration?
- Yes, via the Zapier and Make connectors or directly against the API.
- Are media URLs in webhooks public?
- No — they are short-lived signed URLs scoped to your workspace.
- Is there a sandbox?
- Yes, test workspaces let you exercise webhooks without touching production volume.
Need a hand with something more specific?
help@virtualinspection.ai