> 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.

# Creating callouts

A People Protect callout starts from a protected user's live location. Create the
callout from your trusted backend when the user requests help, then keep the
location current while the callout is active.

## Before creating a callout

Confirm that:

* The user has an AURA `customerId`.
* The customer has an active subscription.
* Your app has a recent latitude/longitude fix.
* You know which response type to request.

If parts of your app can be used before login, use a
[callout-scoped token](/overview/core-concepts/authentication#token-types) rather
than exposing full server credentials to the client.

## After creation

Store the returned callout `id` against your own incident or request record.
Use webhooks where possible, and keep polling as a fallback for active callouts.
When polling, note that the read endpoint returns a richer, **nested** shape
than the creation response — incident and dispatch detail live under
`incidentInformation[]`. The creation response includes the hosted tracking
link in its `url` field; open it in your app or browser so the customer can
track the response.

## In the API Reference

* [Create a customer callout](/api-reference/callouts/create-customer-callout)
* [Update callout location](/api-reference/callouts/update-callout-location)
* [Get a callout](/api-reference/callouts/get-callout-by-id)
* [Cancel a callout](/api-reference/callouts/cancel-callout)