Sign in
Locations

Delete a location

Changed on

Refused while anybody works there — 409, location_in_use — counting both the location on a person's record and the several they may also be assigned to.

Refused while anything sits beneath it — 409, location_has_children. Deleting a parent detaches its whole subtree and destroys the rows describing the ancestry, and this API cannot express a hierarchy at all, so you would not be able to see what you had taken apart.

Once it goes, so do its managers, its device assignments and any auto-scheduler configured for it; devices, schedules, tasks and approval routes keep working with the location set to null. None of that is recoverable and none of it is logged.

Move the people first, then delete.

delete/company/v3/locations/{id}

Request

  • Base URL: https://api.clockster.com
  • URL: https://api.clockster.com/company/v3/locations/{id}
  • Auth: HTTP bearer

Path parameters

idinteger required

The id of the row, as this API issued it.

Response

Success

Changes