Partner Guide: Screen & Protect API Incident Submission Requirements & Customer Copy
For partners:This article explains what your customers need to provide when submitting an incident report through the Screen and Protect API, plus suggested copy you can adapt for your platform's help documentation.
Incident Report Requirements
All incident reports must be submitted within 30 days of guest checkout. Incidents submitted after this deadline are not eligible for review.
What YOUR Customers Need to Provide
Guest Information
- Guest name
- Guest email address
Damage Evidence
- Before and after photos from multiple angles
- Written description of what happened
- Professional repair quotes or receipts
- Proof they contacted the guest about the damage
- Supporting documentation (house rules, police reports if relevant to the incident)
Note for partners: Incomplete evidence doesn't automatically disqualify a incident, but it may impact the outcome of review or processing time.
Suggested Copy for Your Help Documentation
Below is copy you can customize for your platform's help center or incident submission flow:
Customer-Facing Version
How to Submit an Incident Report
Found damage after your guest checked out? Submit the details below and we'll take it from there.
Important: Submit within 30 days of checkout
What You'll Need:
- Guest name and email
- Before and after photos (multiple angles)
- Description of what happened
- Repair quotes or receipts
- Any messages you sent to the guest about the damage
- Supporting documents like house rules or police reports (if applicable)
➡️ Partner Guide: Screen & Protect API – What's Protected?
➡️ Partner Guide: How the Screen & Protect API Incident Process Works