Skip to main content

Monitorable Lifecycle

Every monitorable has two status fields that reflect where it is in its lifecycle:

  • verificationStatus — whether the monitorable has met all compliance requirements
  • systemStatus — whether the monitorable is active and how events will be handled

Verification Status​

Creation and Fulfillment​

When a monitorable is created, the platform checks whether compliance requirements apply to its location. If no requirements exist, the monitorable is immediately set to VERIFIED. If requirements exist, it starts in PENDING_REQUIREMENTS and moves to VERIFIED only once all requirements are fulfilled.

  • A monitorable in INVALID_ADDRESS or FAILED verification status cannot have events created against it.
  • Both PENDING_REQUIREMENTS and VERIFIED monitorables are eligible for activation, subject to pre-activation requirement checks.
  • To create a monitorable, use the Create Monitorable endpoint.

Regression​

A VERIFIED monitorable can move back to PENDING_REQUIREMENTS if a permit expires or new requirements are added by the jurisdiction.

  • Once requirements are fulfilled again, the monitorable returns to VERIFIED (see the fulfillment diagram above).

System Status​

Activation​

When a monitorable is activated, all PRE_ACTIVATION requirements must be complete. If they are, the system status moves to ACTIVE and the monitorable is fully operational.

  • When systemStatus is ACTIVE, events can be created and will be handled by emergency services and agents.
  • To activate a monitorable, use the Activate Monitorable endpoint.

Activation with Familiarization Period​

Some jurisdictions require a familiarization period after activation. During this time, the system status is FAMILIARIZATION — a time-bounded override that automatically transitions to ACTIVE once the period expires.

  • During FAMILIARIZATION, events can be created but will not be handled by emergency responders or agents.
  • Once the familiarization period expires, the system status transitions to ACTIVE and events are handled normally.
  • To activate a monitorable, use the Activate Monitorable endpoint.

Customer Test Mode​

A CUSTOMER_TEST system status can be created manually via the API on any active monitorable. This puts the monitorable into test mode without affecting its underlying ACTIVE status. The monitorable returns to ACTIVE when the test status is deleted or expires.

  • During CUSTOMER_TEST, events can be created but will not be handled by emergency responders or agents.
  • CUSTOMER_TEST is the only system status that can be created manually via the API.
  • To enter test mode, use the Create System Status endpoint.
  • To exit test mode early, use the Delete System Status endpoint. The system status will also automatically expire and return to ACTIVE when the scheduled expiry time is reached.

Cancellation​

Cancelling a monitorable moves it to a terminal CANCELLED state. This is irreversible.

  • A CANCELLED monitorable is effectively read-only — events cannot be created against it.
  • When a monitorable is cancelled, the cancelledAt timestamp is set on the monitorable response.
  • Cancellation is irreversible.
  • To cancel a monitorable, use the Cancel Monitorable endpoint.

Concepts​

  • Monitorables - Overview of monitorable types and fields
  • Compliance - How jurisdiction requirements affect monitorables

Guides​

API Reference​