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

# Customer registration

Register each protected user as an AURA customer before they can create live
callouts. The customer profile stores the contact details and response context
that the control centre and responders use during an emergency.

## Choose an onboarding model

Use one of two models:

* **Hosted signup** - create a customer signup session and send the user through
  the AURA-hosted flow for profile, payment, and subscription setup.
* **API registration** - create and update the customer from your backend, then
  manage the subscription separately.

Hosted signup is usually best when your product does not want to own every
profile, payment, and subscription step. API registration is best when your
backend already owns account creation and billing state.

## Store your identifiers

After registration, store the AURA `customerId` against your own user record.
If you provide an `externalReferenceId`, keep it stable so support and reporting
can reconcile AURA records back to your system.

## In the API Reference

* [Customer sessions](/api-reference/customer-sessions) -
  create and retrieve hosted signup sessions.
* [Customers](/api-reference/customers) - create, retrieve,
  update, and retire customer profiles.