Skip to main content

Pull the CRM's branches and staff in as bookable things

POST 
/api/locations/import-definitions/:provider

Definitions, not transactions. A workspace whose CRM owns its sales ledger still needs its sites and its people to exist HERE, because availability is worked out here: the CRM cannot be asked whether a device is free, since it publishes no device at all.

Three promises, the same ones the catalogue import makes:

  • matched by link, never by name — a rename upstream updates the row it already created rather than making a second one;
  • what a person typed here survives — a site's timezone is never overwritten by a sync, only its name is refreshed;
  • a branch that closed, or somebody who left, is deactivated and kept — every appointment they ever held still points at the row.

Sites and people created here by hand have no link, so an import can never switch them off.

A member of staff arrives as a resource with kind: person that does not occupy its container: two masseuses in one room is exactly the case the resource axis exists for.

Request​

Responses​

What changed, per kind.