post
https://api.mitti.com/inspections/v1/inspections//clone
Create a copy of an existing inspection, including its answers, metadata, and structure. The cloned inspection is set to Incomplete status so it can be reviewed and re-submitted. The cloned inspection is a new, independent inspection linked to the same template as the source.
Administrators can turn off inspection duplication for their entire organization. When this setting is turned off, all clone requests fail, regardless of your permissions or access level.
Requirements
Cloning behavior by field
| Data | Behavior | Detail |
|---|---|---|
| Title | 🔄 Reset | Regenerated from the template's title rules, not copied from the source. |
| Answers and responses | ✅ Copied | All answers are copied, including text, selection, and date/time responses. Date/time answers retain their original values and are not updated to the clone timestamp. |
| Flagged items | ✅ Copied | |
| Score | ✅ Copied | Derived from the copied answers. |
| Media and attachments | ✅ Copied | File attachments (such as PDFs and images) linked to answers are copied and appear in the media summary. |
| Site | ✅ Copied | |
| Location (GPS) | ✅ Copied | |
| Asset | ✅ Copied | |
| Template link | ✅ Copied | The clone is linked to the same template as the source. |
| Completion status | 🔄 Reset | Always reset to Incomplete, even if the source was completed. |
| Inspection date | 🔄 Reset | Set to the time of the clone request. |
| Assigned inspector | 🔄 Reset | Set to the API caller. |
| AI Summary | 🔄 Reset | Regenerated for the clone based on the new date and inspector. |
| Inspection access | 🔄 Reset | The source inspection's access list is not copied. The clone's access is set based on the API caller and the template's auto-sharing rules (e.g., groups or users configured to receive access automatically). To adjust access after cloning, use Set inspection access. |
| Approvals | 🔄 Reset | If the source has an approval section, the approval state is reset to `Not requested' and all approval question responses are cleared. |
| Linked actions | ❌ Dropped | Actions are not carried over. The clone's action count is 0 even if the source had actions. The answer structure that references actions is preserved. |
| Linked schedule | ❌ Dropped | If the source was created by a scheduled inspection, the clone is not linked to that schedule. |
If your workflow depends on actions, you will need to recreate them on the cloned inspection using the Create an action endpoint separately.