Invent one of your own words, and map a key onto it

POST 
/api/integrations/crm/:provider/status-mapping/labels

The tenant's own vocabulary, made from the screen that needed it — the same round-trip the extra-field mapping removed.

The meaning is mandatory. A word with no core status behind it is a word the platform cannot reason about: reminders would not know to skip it, the constraint that frees a room would not fire, reports would not count it. So the form refuses to save until one is chosen, and no meaning is pre-selected — a default here would be the screen guessing.

Created and mapped in ONE action, and merged rather than overwriting: the full PUT above is authoritative for a domain, this is not.

The new word is never made the default for new records. A word invented while mapping somebody else's CRM says nothing about what this workspace's own new bookings should be called.

Request

Responses

201

Created and mapped; the whole screen comes back.

403

Authenticated but not allowed.

404

Resource not found (or not visible to the current tenant).

422

Machine keys: invalid_status_token, invalid_status_label_name, invalid_status_label_color, invalid_status_domain, duplicate_status_label.