Update a Routing Form
Update the settings of a routing form with the Zeeg API. The update is partial, so every field the body leaves out keeps its stored value.
The update is partial
A field that the body leaves out keeps its stored value. A body that namesheadline alone changes the headline and nothing else.
To clear headline or body, send the field with the value null. An omitted field is not a cleared field.
styleSettings merges colour by colour. A body that names bgColor alone leaves the two button colours as they stand.
The colours round-trip
styleSettings is nested on both sides. The read endpoints return the object with its three keys, and this endpoint accepts that same object, so a routing form that you read goes straight back here without reshaping. A routing form that sets no colour returns the three keys as null rather than omitting the object.
styleSettings object here.404, not 422. A routing form outside your workspace answers 404 as well.Authorizations
Path Parameters
UUID of the routing form.
Body
The body that updates a routing form. Every field is optional. A field that the body leaves out keeps its stored value.
The internal name of the routing form. If you send it, it must not be empty.
200"Enterprise Lead Qualification"
The headline above the questions. Send null to clear it.
"Tell us about your team"
The body text below the headline. Send null to clear it.
null
The label of the submit button.
200"Continue"
An inactive routing form accepts no submission.
false
The colours of the public routing form page. Each value is a CSS colour of at most 20 characters, or null when the routing form sets no colour. A response always carries the object with all three keys. The write endpoints accept the same shape, so a routing form that you read goes straight back to PATCH /routing-forms/{id} without reshaping.