For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
GuidesAPI Reference
GuidesAPI Reference
  • Get started
    • Introduction
    • Quickstart
    • Authentication
  • Core concepts
    • Callout lifecycle
    • Customers & customer sources
    • Subscriptions & coverage
  • Integration guides
    • Personal Safety
    • Fixed Locations
    • Device & payment gateway
    • Webhooks
    • Go-live
LogoLogo
On this page
  • When to use this
  • How it works
  • In the API Reference
Integration guides

Fixed Locations

Was this page helpful?
Previous

Device & payment gateway

Next
Built with
First-pass draft inferred from the product site and API behaviour. Confirm specifics with the AURA team before publishing.

Fixed Locations (“Property Protect”) applies AURA’s Guard Response to a managed site — a store, branch, or property — rather than an individual person. You register sites up front, then raise site-based callouts when an alarm or incident occurs at that location.

When to use this

  • Business or property security: alarm response and on-site emergencies.
  • Many sites under one integration, each identified by your own reference.

How it works

  1. Register each site as a predefined (fixed) location with its coordinates and your externalReferenceId.
  2. Raise a callout against a site by that external reference — AURA resolves the stored coordinates and dispatches a responder. No live GPS from a device is required.
  3. Track and resolve the callout through the standard callout lifecycle.

A callout can take a live latitude/longitude or a predefinedLocationId — for sites you use the predefined location so you don’t pass coordinates each time.

In the API Reference

  • Fixed Locations — manage sites and raise a callout by external reference.
  • Callouts