PropertyMe · Arazzo Workflow
Schedule, conduct, report and close a PropertyMe inspection
Version 1.0.0
The routine and entry/exit inspection lifecycle. Requires activity:read for the reads and activity:write for every transition. The permitted transition graph is not published, so each step reads current state first and treats a 400 as an illegal transition rather than a retryable failure. Note a defect in PropertyMe's own contract: the transition paths are templated /v1/inspections/{id}/... in lower case while the declared path parameter is named Id. This workflow uses the DECLARED parameter name, Id.
View Spec
View on GitHub
Real EstateAustraliaProperty ManagementRentalsPropTechTenancyTrust AccountingInspectionsMaintenanceDocumentsPaymentsNew ZealandArazzoWorkflows
Provider
Workflows
schedule-inspect-report-close
Create an inspection on a property, schedule it, conduct it, file the report and close it.
1
create-inspection
AddInspectionRequestinspections_Post
Create the inspection. No idempotency key exists — on a timeout, confirm with SearchInspectionsRequestinspectionssearch_Get filtered by LotId before retrying.
2
read-inspection
GetInspectionRequestinspectionsId_Get
Read current state before transitioning.
3
schedule-inspection
ScheduleInspectionRequestinspectionsidschedule_Post
4
conduct-inspection
InspectInspectionRequestinspectionsidinspect_Post
Mark the inspection as conducted.
5
create-report
CreateInspectionReportRequestinspectionsIdreport_Post
6
update-report
UpdateInspectionReportRequestinspectionsIdreport_Create
Revise the report. The operationId ends _Create but the method is PUT.
7
read-report
GetInspectionReportRequestinspectionsreportsId_Get
The report is fetched by REPORT id on its own path, not under the inspection.
8
attach-document
AddInspectionDocumentRequestinspectionsIddocuments_Post
9
close-inspection
CloseInspectionRequestinspectionsidclose_Post