Property Protect Quickstart
This quickstart gets a Property Protect integration through the basic server flow: authenticate, register a Fixed Location, and create a callout when an alarm or operator action requires response.
Authenticate
First, exchange your client ID and client secret for a secure bearer token. Include this token in the header of all subsequent API calls.
- Reference: Exchange credentials for a token
Register a Fixed Location
Before you can create a callout for a property, register it as a Fixed Location with coordinates, details, and your own stable externalReferenceId.
- Reference: Create a fixed location
Create a Fixed Location callout
When an alarm or operator action requires AURA response, create a callout by passing the Fixed Location’s externalReferenceId.
- Reference: Create a fixed-location callout
The body is optional. Store the returned callout id for cancellation,
events, and polling. If the externalReferenceId is unknown, the API
responds with 400 (not 404) and the detail in the message field.
Verify and close the callout
Read the callout back with Get a callout — note the read endpoint returns a richer, nested shape than the creation response.
Staging callouts are never closed automatically. To drive your callout
through dispatch, arrival, completion, and closure, open the
Responder Simulator in the AURA portal
(switch to Staging mode), enter your calloutId, and step through the flow.
The simulator does not emit webhook events — poll the callout to observe
its state changes.
