@zitadel/api 0.1.0-alpha.4 → 0.1.0-alpha.8

package/src/generated/model/createFlow201StepFieldsItemType.ts

@@ -0,0 +1,31 @@
+/**
+ * Generated by orval v8.10.0 🍺
+ * Do not edit manually.
+ * Zitadel NextGen
+ * This is the next generation of the Zitadel identity platform.
+ * OpenAPI spec version: 0.0.1
+ */
+
+/**
+ * The input kind the client should render. Encodes the formats and
+JSON types that map to a familiar HTML input: `email`, `url`,
+`date` come from `format`; `checkbox` from JSON `type: boolean`;
+`select` from a closed `enum`. For other formats (e.g. uuid) the
+type is `text` and `validation.format` carries the rule.
+
+ */
+export type CreateFlow201StepFieldsItemType =
+  (typeof CreateFlow201StepFieldsItemType)[keyof typeof CreateFlow201StepFieldsItemType];
+
+export const CreateFlow201StepFieldsItemType = {
+  text: "text",
+  email: "email",
+  password: "password",
+  tel: "tel",
+  number: "number",
+  url: "url",
+  date: "date",
+  hidden: "hidden",
+  checkbox: "checkbox",
+  select: "select",
+} as const;

package/src/generated/model/{createFlow201StepFieldsValidation.ts → createFlow201StepFieldsItemValidation.ts}

@@ -5,7 +5,7 @@
  * This is the next generation of the Zitadel identity platform.
  * OpenAPI spec version: 0.0.1
  */
-import type { CreateFlow201StepFieldsValidationFormat } from "./createFlow201StepFieldsValidationFormat";
+import type { CreateFlow201StepFieldsItemValidationFormat } from "./createFlow201StepFieldsItemValidationFormat";
 
 /**
  * Schema-derived rules the frontend SHOULD apply at input time. The
@@ -18,14 +18,14 @@ Each key mirrors a JSON Schema keyword on the underlying user
 property; absent keys mean no rule.
 
  */
-export type CreateFlow201StepFieldsValidation = {
+export type CreateFlow201StepFieldsItemValidation = {
   /** Semantic format the value must match. Values mirror the user
   meta-schema. When `type` already encodes the format (email,
   url, date), this key is informative and the input type is
   sufficient for client-side validation. When `type` is `text`
   (e.g. `format: uuid`), this key is the only signal.
    */
-  format?: CreateFlow201StepFieldsValidationFormat;
+  format?: CreateFlow201StepFieldsItemValidationFormat;
   /**
    * Minimum length in characters (inclusive). Mirrors `minLength`.
    * @minimum 0
@@ -36,4 +36,10 @@ export type CreateFlow201StepFieldsValidation = {
    * @minimum 0
    */
   max_length?: number;
+  /** Closed list of allowed values. Mirrors the JSON Schema `enum`
+  keyword on the underlying user property. When `type` is
+  `select` the client renders these as options; for other types
+  the rule still applies as a membership check.
+   */
+  enum?: string[];
 };

package/src/generated/model/{submitFlowStep400StepFieldsValidationFormat.ts → createFlow201StepFieldsItemValidationFormat.ts}

@@ -14,10 +14,10 @@ sufficient for client-side validation. When `type` is `text`
 (e.g. `format: uuid`), this key is the only signal.
 
  */
-export type SubmitFlowStep400StepFieldsValidationFormat =
-  (typeof SubmitFlowStep400StepFieldsValidationFormat)[keyof typeof SubmitFlowStep400StepFieldsValidationFormat];
+export type CreateFlow201StepFieldsItemValidationFormat =
+  (typeof CreateFlow201StepFieldsItemValidationFormat)[keyof typeof CreateFlow201StepFieldsItemValidationFormat];
 
-export const SubmitFlowStep400StepFieldsValidationFormat = {
+export const CreateFlow201StepFieldsItemValidationFormat = {
   email: "email",
   "date-time": "date-time",
   uuid: "uuid",

package/src/generated/model/createFlowDefinition201FlowDefinitionStepsItem.ts

@@ -5,7 +5,7 @@
  * This is the next generation of the Zitadel identity platform.
  * OpenAPI spec version: 0.0.1
  */
-import type { CreateFlowDefinition201FlowDefinitionStepsItemActions } from "./createFlowDefinition201FlowDefinitionStepsItemActions";
+import type { CreateFlowDefinition201FlowDefinitionStepsItemActionsItem } from "./createFlowDefinition201FlowDefinitionStepsItemActionsItem";
 import type { CreateFlowDefinition201FlowDefinitionStepsItemComplete } from "./createFlowDefinition201FlowDefinitionStepsItemComplete";
 import type { CreateFlowDefinition201FlowDefinitionStepsItemGates } from "./createFlowDefinition201FlowDefinitionStepsItemGates";
 import type { CreateFlowDefinition201FlowDefinitionStepsItemOnSuccess } from "./createFlowDefinition201FlowDefinitionStepsItemOnSuccess";
@@ -36,11 +36,11 @@ export type CreateFlowDefinition201FlowDefinitionStepsItem = {
   transition outcome).
    */
   fields?: string[];
-  /** Actions the user can take. Keyed by action name.
-  The action name is what the frontend sends back in the submit request.
-  If omitted, the engine provides a default `submit` action.
+  /** Ordered list of actions the user can take. The action name is what the
+  frontend sends back in the submit request. If omitted, the engine
+  provides a default `submit` action.
    */
-  actions?: CreateFlowDefinition201FlowDefinitionStepsItemActions;
+  actions?: CreateFlowDefinition201FlowDefinitionStepsItemActionsItem[];
   /** Security gates that must be satisfied before submission. Keyed by gate
   name. Each gate selects a kind (e.g. "captcha") and provider-specific
   configuration. The engine may also inject gates dynamically based on
@@ -62,7 +62,7 @@ export type CreateFlowDefinition201FlowDefinitionStepsItem = {
   complete?: CreateFlowDefinition201FlowDefinitionStepsItemComplete;
   /** Maps action/outcome names to their transition descriptor.
 
-  Keys match action names from the `actions` dict. Additional keys
+  Keys match action names from the `actions` array. Additional keys
   come from implicit outcomes based on schema annotations
   (e.g. `user_not_found` from `x-unique` fields) and engine
   events (e.g. `sso`, `callback`).

package/src/generated/model/{createFlowDefinition201FlowDefinitionStepsItemActions.ts → createFlowDefinition201FlowDefinitionStepsItemActionsItem.ts}

@@ -7,23 +7,22 @@
  */
 
 /**
- * Actions the user can take. Keyed by action name.
-The action name is what the frontend sends back in the submit request.
-If omitted, the engine provides a default `submit` action.
+ * Configuration for a user-invokable action on a step. The `name` is sent
+back in the submit request as `action`.
 
  */
-export type CreateFlowDefinition201FlowDefinitionStepsItemActions = {
-  [key: string]: {
-    /** Marks this as the default/primary action. The runtime template uses
+export type CreateFlowDefinition201FlowDefinitionStepsItemActionsItem = {
+  /** Action identifier. Sent back in the submit request as `action`. */
+  name: string;
+  /** Marks this as the default/primary action. The runtime template uses
   this hint to choose visual emphasis. At most one action per step
   should be primary; this is not enforced here.
    */
-    primary?: boolean;
-    /** Optional localization key override for the action's label. When
+  primary?: boolean;
+  /** Optional localization key override for the action's label. When
   omitted, the engine derives a key from the step and action names.
   Display text is resolved client-side from a locale dictionary, never
   by the engine.
    */
-    text_key?: string;
-  };
+  text_key?: string;
 };

package/src/generated/model/createFlowDefinition201FlowDefinitionStepsItemTransitions.ts

@@ -9,7 +9,7 @@
 /**
  * Maps action/outcome names to their transition descriptor.
 
-Keys match action names from the `actions` dict. Additional keys
+Keys match action names from the `actions` array. Additional keys
 come from implicit outcomes based on schema annotations
 (e.g. `user_not_found` from `x-unique` fields) and engine
 events (e.g. `sso`, `callback`).

package/src/generated/model/createFlowDefinitionBodyFlowDefinitionStepsItem.ts

@@ -5,7 +5,7 @@
  * This is the next generation of the Zitadel identity platform.
  * OpenAPI spec version: 0.0.1
  */
-import type { CreateFlowDefinitionBodyFlowDefinitionStepsItemActions } from "./createFlowDefinitionBodyFlowDefinitionStepsItemActions";
+import type { CreateFlowDefinitionBodyFlowDefinitionStepsItemActionsItem } from "./createFlowDefinitionBodyFlowDefinitionStepsItemActionsItem";
 import type { CreateFlowDefinitionBodyFlowDefinitionStepsItemComplete } from "./createFlowDefinitionBodyFlowDefinitionStepsItemComplete";
 import type { CreateFlowDefinitionBodyFlowDefinitionStepsItemGates } from "./createFlowDefinitionBodyFlowDefinitionStepsItemGates";
 import type { CreateFlowDefinitionBodyFlowDefinitionStepsItemOnSuccess } from "./createFlowDefinitionBodyFlowDefinitionStepsItemOnSuccess";
@@ -36,11 +36,11 @@ export type CreateFlowDefinitionBodyFlowDefinitionStepsItem = {
   transition outcome).
    */
   fields?: string[];
-  /** Actions the user can take. Keyed by action name.
-  The action name is what the frontend sends back in the submit request.
-  If omitted, the engine provides a default `submit` action.
+  /** Ordered list of actions the user can take. The action name is what the
+  frontend sends back in the submit request. If omitted, the engine
+  provides a default `submit` action.
    */
-  actions?: CreateFlowDefinitionBodyFlowDefinitionStepsItemActions;
+  actions?: CreateFlowDefinitionBodyFlowDefinitionStepsItemActionsItem[];
   /** Security gates that must be satisfied before submission. Keyed by gate
   name. Each gate selects a kind (e.g. "captcha") and provider-specific
   configuration. The engine may also inject gates dynamically based on
@@ -62,7 +62,7 @@ export type CreateFlowDefinitionBodyFlowDefinitionStepsItem = {
   complete?: CreateFlowDefinitionBodyFlowDefinitionStepsItemComplete;
   /** Maps action/outcome names to their transition descriptor.
 
-  Keys match action names from the `actions` dict. Additional keys
+  Keys match action names from the `actions` array. Additional keys
   come from implicit outcomes based on schema annotations
   (e.g. `user_not_found` from `x-unique` fields) and engine
   events (e.g. `sso`, `callback`).

package/src/generated/model/{createFlowDefinitionBodyFlowDefinitionStepsItemActions.ts → createFlowDefinitionBodyFlowDefinitionStepsItemActionsItem.ts}

@@ -7,23 +7,22 @@
  */
 
 /**
- * Actions the user can take. Keyed by action name.
-The action name is what the frontend sends back in the submit request.
-If omitted, the engine provides a default `submit` action.
+ * Configuration for a user-invokable action on a step. The `name` is sent
+back in the submit request as `action`.
 
  */
-export type CreateFlowDefinitionBodyFlowDefinitionStepsItemActions = {
-  [key: string]: {
-    /** Marks this as the default/primary action. The runtime template uses
+export type CreateFlowDefinitionBodyFlowDefinitionStepsItemActionsItem = {
+  /** Action identifier. Sent back in the submit request as `action`. */
+  name: string;
+  /** Marks this as the default/primary action. The runtime template uses
   this hint to choose visual emphasis. At most one action per step
   should be primary; this is not enforced here.
    */
-    primary?: boolean;
-    /** Optional localization key override for the action's label. When
+  primary?: boolean;
+  /** Optional localization key override for the action's label. When
   omitted, the engine derives a key from the step and action names.
   Display text is resolved client-side from a locale dictionary, never
   by the engine.
    */
-    text_key?: string;
-  };
+  text_key?: string;
 };

package/src/generated/model/createFlowDefinitionBodyFlowDefinitionStepsItemTransitions.ts

@@ -9,7 +9,7 @@
 /**
  * Maps action/outcome names to their transition descriptor.
 
-Keys match action names from the `actions` dict. Additional keys
+Keys match action names from the `actions` array. Additional keys
 come from implicit outcomes based on schema annotations
 (e.g. `user_not_found` from `x-unique` fields) and engine
 events (e.g. `sso`, `callback`).

package/src/generated/model/getFlowDefinition200FlowDefinitionStepsItem.ts

@@ -5,7 +5,7 @@
  * This is the next generation of the Zitadel identity platform.
  * OpenAPI spec version: 0.0.1
  */
-import type { GetFlowDefinition200FlowDefinitionStepsItemActions } from "./getFlowDefinition200FlowDefinitionStepsItemActions";
+import type { GetFlowDefinition200FlowDefinitionStepsItemActionsItem } from "./getFlowDefinition200FlowDefinitionStepsItemActionsItem";
 import type { GetFlowDefinition200FlowDefinitionStepsItemComplete } from "./getFlowDefinition200FlowDefinitionStepsItemComplete";
 import type { GetFlowDefinition200FlowDefinitionStepsItemGates } from "./getFlowDefinition200FlowDefinitionStepsItemGates";
 import type { GetFlowDefinition200FlowDefinitionStepsItemOnSuccess } from "./getFlowDefinition200FlowDefinitionStepsItemOnSuccess";
@@ -36,11 +36,11 @@ export type GetFlowDefinition200FlowDefinitionStepsItem = {
   transition outcome).
    */
   fields?: string[];
-  /** Actions the user can take. Keyed by action name.
-  The action name is what the frontend sends back in the submit request.
-  If omitted, the engine provides a default `submit` action.
+  /** Ordered list of actions the user can take. The action name is what the
+  frontend sends back in the submit request. If omitted, the engine
+  provides a default `submit` action.
    */
-  actions?: GetFlowDefinition200FlowDefinitionStepsItemActions;
+  actions?: GetFlowDefinition200FlowDefinitionStepsItemActionsItem[];
   /** Security gates that must be satisfied before submission. Keyed by gate
   name. Each gate selects a kind (e.g. "captcha") and provider-specific
   configuration. The engine may also inject gates dynamically based on
@@ -62,7 +62,7 @@ export type GetFlowDefinition200FlowDefinitionStepsItem = {
   complete?: GetFlowDefinition200FlowDefinitionStepsItemComplete;
   /** Maps action/outcome names to their transition descriptor.
 
-  Keys match action names from the `actions` dict. Additional keys
+  Keys match action names from the `actions` array. Additional keys
   come from implicit outcomes based on schema annotations
   (e.g. `user_not_found` from `x-unique` fields) and engine
   events (e.g. `sso`, `callback`).

package/src/generated/model/getFlowDefinition200FlowDefinitionStepsItemActionsItem.ts

@@ -0,0 +1,28 @@
+/**
+ * Generated by orval v8.10.0 🍺
+ * Do not edit manually.
+ * Zitadel NextGen
+ * This is the next generation of the Zitadel identity platform.
+ * OpenAPI spec version: 0.0.1
+ */
+
+/**
+ * Configuration for a user-invokable action on a step. The `name` is sent
+back in the submit request as `action`.
+
+ */
+export type GetFlowDefinition200FlowDefinitionStepsItemActionsItem = {
+  /** Action identifier. Sent back in the submit request as `action`. */
+  name: string;
+  /** Marks this as the default/primary action. The runtime template uses
+  this hint to choose visual emphasis. At most one action per step
+  should be primary; this is not enforced here.
+   */
+  primary?: boolean;
+  /** Optional localization key override for the action's label. When
+  omitted, the engine derives a key from the step and action names.
+  Display text is resolved client-side from a locale dictionary, never
+  by the engine.
+   */
+  text_key?: string;
+};

package/src/generated/model/getFlowDefinition200FlowDefinitionStepsItemTransitions.ts

@@ -9,7 +9,7 @@
 /**
  * Maps action/outcome names to their transition descriptor.
 
-Keys match action names from the `actions` dict. Additional keys
+Keys match action names from the `actions` array. Additional keys
 come from implicit outcomes based on schema annotations
 (e.g. `user_not_found` from `x-unique` fields) and engine
 events (e.g. `sso`, `callback`).

package/src/generated/model/getFlowStep200.ts

@@ -18,9 +18,10 @@ export type GetFlowStep200 = {
   session_id: string;
   /** Reserved for future rotation. The sealed `_zflow` cookie carries the flow state today. */
   session_token?: string;
-  /** A step contains unordered capability dictionaries: what to collect (fields),
+  /** A step contains ordered capability arrays: what to collect (fields),
   what the user can do (actions), and what security gates must be satisfied (gates).
-  Layout and element ordering are controlled by the LiquidJS template in `branding.liquid_template`.
+  The LiquidJS template in `branding.liquid_template` iterates these arrays in order
+  and builds name-keyed indexes locally for lookup.
    */
   step: GetFlowStep200Step;
   /** Resolved branding configuration. Inherited from the app → team → project

package/src/generated/model/getFlowStep200Step.ts

@@ -5,18 +5,19 @@
  * This is the next generation of the Zitadel identity platform.
  * OpenAPI spec version: 0.0.1
  */
-import type { GetFlowStep200StepActions } from "./getFlowStep200StepActions";
+import type { GetFlowStep200StepActionsItem } from "./getFlowStep200StepActionsItem";
 import type { GetFlowStep200StepChallenge } from "./getFlowStep200StepChallenge";
 import type { GetFlowStep200StepComplete } from "./getFlowStep200StepComplete";
-import type { GetFlowStep200StepFields } from "./getFlowStep200StepFields";
+import type { GetFlowStep200StepFieldsItem } from "./getFlowStep200StepFieldsItem";
 import type { GetFlowStep200StepGates } from "./getFlowStep200StepGates";
 import type { GetFlowStep200StepSsoProvidersItem } from "./getFlowStep200StepSsoProvidersItem";
 import type { GetFlowStep200StepTexts } from "./getFlowStep200StepTexts";
 
 /**
- * A step contains unordered capability dictionaries: what to collect (fields),
+ * A step contains ordered capability arrays: what to collect (fields),
 what the user can do (actions), and what security gates must be satisfied (gates).
-Layout and element ordering are controlled by the LiquidJS template in `branding.liquid_template`.
+The LiquidJS template in `branding.liquid_template` iterates these arrays in order
+and builds name-keyed indexes locally for lookup.
 
  */
 export type GetFlowStep200Step = {
@@ -35,16 +36,16 @@ export type GetFlowStep200Step = {
   complete?: GetFlowStep200StepComplete;
   /** URL to navigate to (e.g., SSO provider redirect). */
   redirect_url?: string;
-  /** Unordered dictionary of input fields to collect. Keyed by field name.
-  The LiquidJS template controls which fields appear and in what order.
-  Field metadata (type, validation) is resolved by the engine from the
-  flow's user schema.
+  /** Ordered list of input fields to collect. Field metadata (type, validation)
+  is resolved by the engine from the flow's user schema. The LiquidJS
+  template iterates this array; for keyed lookup it builds a name-indexed
+  map locally.
    */
-  fields: GetFlowStep200StepFields;
-  /** Unordered dictionary of available user actions. Keyed by action name.
-  The LiquidJS template controls positioning and presentation.
+  fields: GetFlowStep200StepFieldsItem[];
+  /** Ordered list of available user actions. The LiquidJS template iterates
+  this array and builds a name-indexed map locally for keyed lookup.
    */
-  actions: GetFlowStep200StepActions;
+  actions: GetFlowStep200StepActionsItem[];
   /** Security gates that must be satisfied before the step can be submitted.
   The engine injects gates dynamically based on policy, even if they
   are not declared in the flow definition.

package/src/generated/model/{submitFlowStep200StepActions.ts → getFlowStep200StepActionsItem.ts}

@@ -7,22 +7,22 @@
  */
 
 /**
- * Unordered dictionary of available user actions. Keyed by action name.
-The LiquidJS template controls positioning and presentation.
+ * Configuration for a user-invokable action on a step. The `name` is sent
+back in the submit request as `action`.
 
  */
-export type SubmitFlowStep200StepActions = {
-  [key: string]: {
-    /** Marks this as the default/primary action. The runtime template uses
+export type GetFlowStep200StepActionsItem = {
+  /** Action identifier. Sent back in the submit request as `action`. */
+  name: string;
+  /** Marks this as the default/primary action. The runtime template uses
   this hint to choose visual emphasis. At most one action per step
   should be primary; this is not enforced here.
    */
-    primary?: boolean;
-    /** Optional localization key override for the action's label. When
+  primary?: boolean;
+  /** Optional localization key override for the action's label. When
   omitted, the engine derives a key from the step and action names.
   Display text is resolved client-side from a locale dictionary, never
   by the engine.
    */
-    text_key?: string;
-  };
+  text_key?: string;
 };

package/src/generated/model/getFlowStep200StepFieldsItem.ts

@@ -0,0 +1,46 @@
+/**
+ * Generated by orval v8.10.0 🍺
+ * Do not edit manually.
+ * Zitadel NextGen
+ * This is the next generation of the Zitadel identity platform.
+ * OpenAPI spec version: 0.0.1
+ */
+import type { GetFlowStep200StepFieldsItemType } from "./getFlowStep200StepFieldsItemType";
+import type { GetFlowStep200StepFieldsItemValidation } from "./getFlowStep200StepFieldsItemValidation";
+
+/**
+ * A data input capability. Describes what the user must provide.
+Does not contain display text — only a `text_key` resolved client-side.
+
+ */
+export type GetFlowStep200StepFieldsItem = {
+  /** Field name, matching a property in the flow's user schema. Carries
+  the submitted value back to the engine.
+   */
+  name: string;
+  /** The input kind the client should render. Encodes the formats and
+  JSON types that map to a familiar HTML input: `email`, `url`,
+  `date` come from `format`; `checkbox` from JSON `type: boolean`;
+  `select` from a closed `enum`. For other formats (e.g. uuid) the
+  type is `text` and `validation.format` carries the rule.
+   */
+  type: GetFlowStep200StepFieldsItemType;
+  /** Localization key for the field label. */
+  text_key: string;
+  /** The field MUST be present and non-empty on submit. Mirrors the
+  schema's top-level `required` array.
+   */
+  required?: boolean;
+  /** Pre-filled value (e.g., an identifier carried over from a pivot). */
+  value?: unknown;
+  /** Schema-derived rules the frontend SHOULD apply at input time. The
+  server runs the same rules on submit and is the only authority on
+  whether the step advances — these rules are a UX hint to reduce
+  round trips, not a contract guarantee.
+
+  Omitted entirely when the field has no rules beyond its `type`.
+  Each key mirrors a JSON Schema keyword on the underlying user
+  property; absent keys mean no rule.
+   */
+  validation?: GetFlowStep200StepFieldsItemValidation;
+};

package/src/generated/model/getFlowStep200StepFieldsItemType.ts

@@ -0,0 +1,31 @@
+/**
+ * Generated by orval v8.10.0 🍺
+ * Do not edit manually.
+ * Zitadel NextGen
+ * This is the next generation of the Zitadel identity platform.
+ * OpenAPI spec version: 0.0.1
+ */
+
+/**
+ * The input kind the client should render. Encodes the formats and
+JSON types that map to a familiar HTML input: `email`, `url`,
+`date` come from `format`; `checkbox` from JSON `type: boolean`;
+`select` from a closed `enum`. For other formats (e.g. uuid) the
+type is `text` and `validation.format` carries the rule.
+
+ */
+export type GetFlowStep200StepFieldsItemType =
+  (typeof GetFlowStep200StepFieldsItemType)[keyof typeof GetFlowStep200StepFieldsItemType];
+
+export const GetFlowStep200StepFieldsItemType = {
+  text: "text",
+  email: "email",
+  password: "password",
+  tel: "tel",
+  number: "number",
+  url: "url",
+  date: "date",
+  hidden: "hidden",
+  checkbox: "checkbox",
+  select: "select",
+} as const;

package/src/generated/model/{getFlowStep200StepFieldsValidation.ts → getFlowStep200StepFieldsItemValidation.ts}

@@ -5,7 +5,7 @@
  * This is the next generation of the Zitadel identity platform.
  * OpenAPI spec version: 0.0.1
  */
-import type { GetFlowStep200StepFieldsValidationFormat } from "./getFlowStep200StepFieldsValidationFormat";
+import type { GetFlowStep200StepFieldsItemValidationFormat } from "./getFlowStep200StepFieldsItemValidationFormat";
 
 /**
  * Schema-derived rules the frontend SHOULD apply at input time. The
@@ -18,14 +18,14 @@ Each key mirrors a JSON Schema keyword on the underlying user
 property; absent keys mean no rule.
 
  */
-export type GetFlowStep200StepFieldsValidation = {
+export type GetFlowStep200StepFieldsItemValidation = {
   /** Semantic format the value must match. Values mirror the user
   meta-schema. When `type` already encodes the format (email,
   url, date), this key is informative and the input type is
   sufficient for client-side validation. When `type` is `text`
   (e.g. `format: uuid`), this key is the only signal.
    */
-  format?: GetFlowStep200StepFieldsValidationFormat;
+  format?: GetFlowStep200StepFieldsItemValidationFormat;
   /**
    * Minimum length in characters (inclusive). Mirrors `minLength`.
    * @minimum 0
@@ -36,4 +36,10 @@ export type GetFlowStep200StepFieldsValidation = {
    * @minimum 0
    */
   max_length?: number;
+  /** Closed list of allowed values. Mirrors the JSON Schema `enum`
+  keyword on the underlying user property. When `type` is
+  `select` the client renders these as options; for other types
+  the rule still applies as a membership check.
+   */
+  enum?: string[];
 };

package/src/generated/model/{submitFlowStep200StepFieldsValidationFormat.ts → getFlowStep200StepFieldsItemValidationFormat.ts}

@@ -14,10 +14,10 @@ sufficient for client-side validation. When `type` is `text`
 (e.g. `format: uuid`), this key is the only signal.
 
  */
-export type SubmitFlowStep200StepFieldsValidationFormat =
-  (typeof SubmitFlowStep200StepFieldsValidationFormat)[keyof typeof SubmitFlowStep200StepFieldsValidationFormat];
+export type GetFlowStep200StepFieldsItemValidationFormat =
+  (typeof GetFlowStep200StepFieldsItemValidationFormat)[keyof typeof GetFlowStep200StepFieldsItemValidationFormat];
 
-export const SubmitFlowStep200StepFieldsValidationFormat = {
+export const GetFlowStep200StepFieldsItemValidationFormat = {
   email: "email",
   "date-time": "date-time",
   uuid: "uuid",