Fixed Locations

Fixed Locations are pre-registered properties that AURA can respond to — stores, branches, commercial premises, residential properties, or other managed sites. They provide rapid, location-verified security response to secure physical assets when an alarm sounds or an incident occurs.

You register Fixed Locations up front, then create Fixed Location callouts to request response. Since coordinates and details are pre-registered, no live device GPS is required at dispatch time.

When to use this

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

How it works

  1. Authenticate with a server token using your integration credentials.
  2. Register each Fixed Location with its coordinates and your externalReferenceId.
  3. Keep the Fixed Location list in sync by listing, updating, and deleting Fixed Locations as your source system changes.
  4. Create a callout against a Fixed Location by externalReferenceId. AURA resolves the stored location and dispatches a responder. No live GPS from a device is required.
  5. Track and resolve the callout through the standard callout lifecycle, using webhooks where possible.

A callout can take a live latitude/longitude or a predefinedLocationId — for Fixed Locations you use the stored Fixed Location so you don’t pass coordinates each time.

Fixed Location identifiers

Use a stable externalReferenceId from your own system for each Fixed Location. Treat this as the integration key you use to reconcile records, create Fixed Location callouts, and connect AURA activity back to your platform.

If your platform groups Fixed Locations by client, installer, branch, or portfolio, encode that grouping in your own reference data. AURA can then report on the resulting records without requiring operators to re-key location details during an alarm.

Syncing Fixed Locations

For most integrations, use the fixed-location REST endpoints to create, list, update, and delete Fixed Locations. For large Fixed Location portfolios, AURA also supports a bulk CSV import flow on the Panic API host.

Note that each CSV upload is a full sync — active Fixed Locations missing from the file are marked as deleted — so use CSV either as a one-off seed (maintaining sites via REST afterwards) or as the ongoing source of truth, not both at once. See Bulk CSV import for the upload, callback, and reconciliation flow.

Deleting a Fixed Location removes it from active service. After deletion, do not create new callouts against that reference unless you first recreate the Fixed Location.

Creating a Fixed Location callout

Create the callout with Create a fixed-location callout. Store the returned callout id against your incident, alarm, or job record; you will use that ID for cancellation, chat/events, and polling, and to match the callout to its post-incident resolution report in the AURA portal.

For central-station or alarm-monitoring use cases, see Monitoring Platforms.

Tracking and cancellation

Use Webhooks to receive callout lifecycle events in your backend. If you cannot receive webhooks, poll the callout while it is active and stop polling once it reaches closed.

If the alarm is confirmed as a false alarm or no response is needed, cancel the callout from your trusted backend. For more detail, see Cancel a callout.

In the API Reference