> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.aurasos.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.aurasos.com/_mcp/server.

# Scheduled services

AURA services come in two modes:

* **On-demand** — triggered instantly via app, button, phone, or API. A
  [callout](/overview/core-concepts/callout-lifecycle) *is* the on-demand request:
  alarm response, security escort, keyholding, or guarding created in the moment.
* **Scheduled** — planned in advance: patrols, lock-ups, or site inspections
  arranged ahead of time.

This page covers the **scheduled** mode. For an immediate response, see the
[Callout lifecycle](/overview/core-concepts/callout-lifecycle) instead.

## What you can schedule

Scheduled services are arranged ahead of time rather than triggered in the
moment. Typical examples:

* **Mobile patrols** — regular internal or perimeter checks of a site.
* **Locks and unlocks** — managed property openings and closings.
* **Vacant property protection** — patrols and inspections of empty sites.
* **Occupied property inspections** — routine checks of active sites.
* **Guarding and escorting** — also available as scheduled options.

## Scheduling a request

Create a scheduled request with
[`POST /panic-api/v2/scheduled/{serviceType}`](/api-reference/scheduled-services/create-scheduled-service),
where the **service type is part of the path** — for example
`/panic-api/v2/scheduled/guarding`. Confirm the service types enabled for your
customer source with your AURA contact.

The request body carries:

* `customerId` — the customer the service is for.
* `scheduledRequestConfig` — the schedule itself: a `name`, optional
  `specialInstructions`, service `details` (e.g. `numberOfGuards`,
  `armedPreference`, on-site `contacts`), the `dateFrom`/`dateTo` window, and a
  `repeatsConfig` (`single` or repeating, with a start time and window period).
* `initialLocation` — where the service happens (`latitude`/`longitude` and/or
  `formattedAddress`).

Requests must be **future-dated by at least 5 minutes** — backdated or
immediate requests are rejected with `400`. The response returns the created
`scheduledRequest`, including its `id` and a computed `nextOccurrence`.

Store the returned `scheduledRequest.id`: cancelling uses it as the path
parameter on
[`DELETE /panic-api/v2/scheduled/{scheduledRequestId}`](/api-reference/scheduled-services/delete-scheduled-service)
— note the create and cancel operations interpret the same path position
differently (service type vs request ID).