Resident Move-in Canceled

Overview

·Event key:

lease.resident_move_in_canceled

This event enables real-time tracking when move-ins are canceled or reversed. Use it to update occupancy records, synchronize property management systems, trigger cancellation workflows, update resident status, release unit reservations, and maintain accurate move-in status across your platform.

When This Event Triggers

This event fires when a previously confirmed move-in is reversed or undone. This event only fires for communities that have the "Manual Move-In Workflow" feature enabled, which allows leasing agents to manage move-in status manually. The event fires in the following scenario:

• Move-In Reversed — When a leasing agent reverses a move-in that was previously confirmed. This might happen if a move-in was marked in error, if the resident didn't actually take possession of the unit, or if there was a last-minute change in circumstances. This is a deliberate action taken by property staff to undo a previous move-in confirmation. It reverts the lease back to its pre-move-in state.

When this event fires:

• The lease status changes from "Active" back to "Upcoming"
• A "Move-In Needs Attention" action item is created to remind staff that the move-in still needs to be completed
• The system records that the move-in was reversed

The event payload includes details about the lease such as:

• The lease ID
• The move-in date that was originally scheduled
• PMS identifiers for the tenant, unit, and community

This event is useful for integrating with external systems that need to know when a move-in has been reversed, such as utility services that may need to be put on hold, access control systems that should revoke access, or Property Management Systems that track occupancy status.

Event Payload

Example payloadJSON200 · application/json

{
  "id": "8cc87045-7777-4a16-a882-454044e6762a",
  "event": "lease.resident_move_in_canceled",
  "timestamp": "2024-10-09T13:49:31.658518+00:00",
  "data": {
    "lease_id": 74827,
    "tenant_pms_identifier": "t1234",
    "unit_id": 4355,
    "unit_pms_identifier": "u1234",
    "community_id": 435245,
    "community_pms_identifier": "c1234",
    "move_in_date": "2023-05-01"
  }
}