Onboarding Flows

Update an onboarding flow

PATCH/onboarding-flows/{id}

Changes what you send and returns the flow. routes replaces the whole routing graph, and [] clears it; send it as GET returns it, listing each route after the route that reaches its from_form_id. A graph that cannot be read back exactly is refused with 422. definition is kept unless sent. A published flow can still be changed. dry_run shows the result without saving it. Emits onboarding_flow.updated and sends no email. Sending the old values undoes it.

Path parameters

  • idstring (uuid)Required#

    The onboarding flow's id, a uuid. An unknown or deleted id returns 404.

Query parameters

  • dry_runboolean#

    Validate and run the call without committing it, returning what the real call would return with meta.dry_run set.

Request body

application/json, required · OnboardingFlowUpdate

  • namestring#

    The flow's display name.

  • expiry_typestring#

    How often a respondent completes the flow again: daily, one_month, three_month, six_month, twelve_month or never_expire.

    One of: daily, one_month, three_month, six_month, twelve_month, never_expire
  • mode_typestring#

    continuous lets a respondent change answers at any time; versioned keeps each completion as it was.

    One of: continuous, versioned
  • user_typesstring[]#

    The user types the flow can onboard: investor, advisor or both.

    One of: investor, advisor
  • definitionobject | null#

    The editor's layout for the flow. It is kept as sent and never read by the API. Left alone when you do not send it.

  • The whole routing graph. It replaces the stored one, and an empty list clears it. List each route after the route that reaches its from_form_id; the start form is the only form no route has to reach. Left alone when you do not send it.

{
  "name": "Investor suitability v2",
  "routes": [
    {
      "from_form_id": "0b6c7c0e-1f0a-4b6c-8d0e-5f0f4a7a3c21",
      "to_form_id": "6d8f3a52-9a41-4d6c-b7a1-2c9e5d1b7f33",
      "condition_sets": [
        {
          "condition_type": "AND",
          "condition_value": null,
          "conditions": [
            {
              "form_field_id": "2f1d9a77-3c1e-4e85-a0b3-7d6c4e8b9a55",
              "operator": "=",
              "value": "yes"
            }
          ],
          "custom_conditions": []
        },
        {
          "condition_type": "OTHER",
          "condition_value": null,
          "conditions": [],
          "custom_conditions": []
        }
      ]
    }
  ]
}

Responses

200

The updated onboarding flow.

OnboardingFlow
{
  "data": {
    "id": "48e0c1a6-6f3b-4d44-9d49-0a5a0b8f2d11",
    "name": "Investor suitability",
    "status": "draft",
    "expiry_type": "twelve_month",
    "mode_type": "continuous",
    "user_types": [
      "investor"
    ],
    "routes": [
      {
        "from_form_id": "0b6c7c0e-1f0a-4b6c-8d0e-5f0f4a7a3c21",
        "to_form_id": "6d8f3a52-9a41-4d6c-b7a1-2c9e5d1b7f33",
        "condition_sets": [
          {
            "condition_type": "AND",
            "condition_value": null,
            "conditions": [
              {
                "form_field_id": "2f1d9a77-3c1e-4e85-a0b3-7d6c4e8b9a55",
                "operator": "=",
                "value": "yes"
              }
            ],
            "custom_conditions": []
          },
          {
            "condition_type": "OTHER",
            "condition_value": null,
            "conditions": [],
            "custom_conditions": []
          }
        ]
      }
    ],
    "definition": null,
    "form_count": 2,
    "start_form_id": "0b6c7c0e-1f0a-4b6c-8d0e-5f0f4a7a3c21",
    "created_at": "2026-11-08T10:30:00Z",
    "updated_at": "2026-11-08T10:30:00Z"
  }
}
401

Authentication failed. error.code is one of invalid_token, expired, revoked.

Error
403

Authorization failed. error.code is one of org_disabled, ip_blocked, missing_scope, scope_disabled, user_disabled.

Error
404

Resource not found (error.code = not_found).

Error
409

The request conflicts with existing state (error.code = conflict), e.g. a compliance flow with the requested name already exists.

Error
422

The request can't be processed (HTTP 422): validation_failed with one ErrorDetail per problem, or a code documented on the operation.

Error
429

Rate limit exceeded (error.code = rate_limited).

Error

Examples

curl -X PATCH https://your-org-domain/kong/core/api/v2/onboarding-flows/{id}\
  -H "Authorization: Bearer $HELM_API_KEY"\
  -H "Content-Type: application/json"\
  -d '{
  "name": "Investor suitability v2",
  "routes": [
    {
      "from_form_id": "0b6c7c0e-1f0a-4b6c-8d0e-5f0f4a7a3c21",
      "to_form_id": "6d8f3a52-9a41-4d6c-b7a1-2c9e5d1b7f33",
      "condition_sets": [
        {
          "condition_type": "AND",
          "condition_value": null,
          "conditions": [
            {
              "form_field_id": "2f1d9a77-3c1e-4e85-a0b3-7d6c4e8b9a55",
              "operator": "=",
              "value": "yes"
            }
          ],
          "custom_conditions": []
        },
        {
          "condition_type": "OTHER",
          "condition_value": null,
          "conditions": [],
          "custom_conditions": []
        }
      ]
    }
  ]
}'