Skip to main content
PATCH
Updates the settings of one routing form and returns it in the shape that Get a Routing Form returns. Every field is optional and takes the same values as Create a Routing Form.

The update is partial

A field that the body leaves out keeps its stored value. A body that names headline 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.
The dashboard’s own internal API flattens the same three colours to the top level. That surface is not this one. Send the nested styleSettings object here.
The questions and the routes have their own endpoints: Replace Routing Form Questions and Replace Routing Form Routes. This endpoint changes neither.
The id is a UUID. A malformed id answers 404, not 422. A routing form outside your workspace answers 404 as well.

Authorizations

Authorization
string
header
required

Path Parameters

id
string<uuid>
required

UUID of the routing form.

Body

application/json

The body that updates a routing form. Every field is optional. A field that the body leaves out keeps its stored value.

name
string

The internal name of the routing form. If you send it, it must not be empty.

Maximum string length: 200
Example:

"Enterprise Lead Qualification"

headline
string | null

The headline above the questions. Send null to clear it.

Example:

"Tell us about your team"

body
string | null

The body text below the headline. Send null to clear it.

Example:

null

submitBtnText
string | null

The label of the submit button.

Maximum string length: 200
Example:

"Continue"

isActive
boolean

An inactive routing form accepts no submission.

Example:

false

styleSettings
object

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.

Response

OK

success
boolean
Example:

true

status
integer
Example:

200

routingForm
object

A routing form with its questions and its routes, as returned when you fetch one routing form.

Last modified on September 9, 2026