@zitadel/api 0.0.0

package/src/generated/model/createFlowBodyHint.ts

@@ -0,0 +1,18 @@
+/**
+ * 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
+ */
+
+export type CreateFlowBodyHint = {
+  /** Auto-submits identifier step (maps to OIDC login_hint). */
+  login_name?: string;
+  /** Scopes flow resolution to a team. */
+  team_id?: string;
+  /** Scopes to a specific user type. */
+  user_schema_id?: string;
+  /** Scopes to a specific application. */
+  app_id?: string;
+};

package/src/generated/model/createFlowBodyPurpose.ts

@@ -0,0 +1,19 @@
+/**
+ * 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
+ */
+
+export type CreateFlowBodyPurpose =
+  (typeof CreateFlowBodyPurpose)[keyof typeof CreateFlowBodyPurpose];
+
+export const CreateFlowBodyPurpose = {
+  login: "login",
+  register: "register",
+  recovery: "recovery",
+  profiling: "profiling",
+  reauth: "reauth",
+  link_account: "link_account",
+} as const;

package/src/generated/model/createFlowDefault.ts

@@ -0,0 +1,20 @@
+/**
+ * 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 { CreateFlowDefaultDetails } from "./createFlowDefaultDetails";
+
+/**
+ * Standard error payload returned for failed API requests.
+ */
+export type CreateFlowDefault = {
+  /** Stable machine-readable error code. */
+  code: string;
+  /** Human-readable explanation of the error. */
+  message: string;
+  /** Additional error-specific context. */
+  details?: CreateFlowDefaultDetails;
+};

package/src/generated/model/createFlowDefaultDetails.ts

@@ -0,0 +1,12 @@
+/**
+ * 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
+ */
+
+/**
+ * Additional error-specific context.
+ */
+export type CreateFlowDefaultDetails = { [key: string]: unknown };

package/src/generated/model/createFlowDefinition201.ts

@@ -0,0 +1,162 @@
+/**
+ * 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
+ */
+
+export type CreateFlowDefinition201 = {
+  /**
+     * Stable identifier for this flow, used as the target of cross-flow
+  `switch` and `pivot` transitions. Renaming is not supported — the
+  `name` is part of the public contract another definition may
+  reference. Acts as the human display label as well; no separate slug.
+
+     * @pattern ^[a-z][a-z0-9-]*$
+     */
+  name: string;
+  /** User schema this flow operates on. Step `fields` reference properties
+  defined in this schema. The engine resolves field types, validation,
+  and implicit outcomes from schema annotations at runtime.
+   */
+  user_schema: string;
+  /** Maps each purpose this definition handles to its entry-point step.
+  Keys are purpose names; values must match a `name` in `steps`. A
+  definition can serve multiple purposes (e.g. a combined login/register
+  flow) by listing one entry per purpose.
+   */
+  purposes: Partial<
+    Record<"login" | "register" | "recovery" | "profiling" | "reauth" | "link_account", string>
+  >;
+  /** Scopes which teams or apps this flow definition applies to. Empty or
+  omitted fields mean "no restriction"; when both are empty the definition
+  matches every request in the project. The engine picks the most specific
+  matching definition: app > team > project-wide.
+   */
+  audience?: {
+    /** Restrict to specific teams (organizations). Empty means no team restriction. */
+    team_ids?: string[];
+    /** Restrict to specific applications. Empty means no app restriction. */
+    app_ids?: string[];
+  };
+  /**
+     * Ordered list of steps in this flow. The order is for human readability —
+  actual step sequencing is determined by transitions.
+
+     * @minItems 1
+     */
+  steps: {
+    /** Unique step identifier within this flow. Used as transition targets
+  and returned in the API response as `step.name`.
+   */
+    name: string;
+    /** Schema property names to collect from the user. Each entry references
+  a property in the flow's user schema. The engine resolves field type,
+  validation rules, and implicit outcomes from schema annotations
+  (e.g. a property with `x-unique` set implies a `user_not_found`
+  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.
+   */
+    actions?: {
+      [key: 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;
+      };
+    };
+    /** 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
+  policy.
+   */
+    gates?: {
+      [key: string]: {
+        /** The gate category. Only `captcha` is currently defined. Authenticator
+  ceremonies (e.g. passkey) are modelled as credential auth_attempts via
+  `x-credential` on a field, not as gates.
+   */
+        kind: "captcha";
+        /** Provider identifier within the gate kind — e.g. `altcha`, `turnstile`,
+  `hcaptcha`. The engine looks up an implementation in its provider
+  registry.
+   */
+        provider: string;
+        /** Provider-specific configuration consumed by the implementation when
+  issuing the per-render challenge. Opaque to the engine.
+   */
+        config?: { [key: string]: unknown };
+      };
+    };
+    /** Available SSO identity providers for this step. */
+    sso_providers?: {
+      /** Provider instance identifier. */
+      id: string;
+      /** Display name for the provider. */
+      name: string;
+      /** Template hint for rendering (logo, colors). */
+      template: string;
+    }[];
+    /** Server-side mutation to execute when this step completes successfully.
+  Runs after field validation passes, before the transition fires.
+
+  - create_user: creates the user record (registration flows)
+   */
+    on_success?: "create_user";
+    /** Marks this as a terminal step. Tells the frontend what to do:
+  - redirect: navigate to redirect_uri (OIDC/SAML callback done)
+  - show: render as a success/info screen
+   */
+    complete?: "redirect" | "show";
+    /** Maps action/outcome names to their transition descriptor.
+
+  Keys match action names from the `actions` dict. 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`).
+   */
+    transitions?: {
+      [key: string]: {
+        /** Step name within this flow (when `action` is null), or the name
+  of another flow (when `action` is `switch` or `pivot`).
+   */
+        target: string;
+        /** How to interpret `target`:
+  - null (omitted): transition to a step in the current flow.
+  - switch: replace the current flow with the target flow.
+    No return — the current flow is discarded.
+    Example: login ↔ register.
+  - pivot: push the target flow onto the stack. The current flow
+    is paused and resumes when the target flow completes (auto-pop).
+    Example: login → recovery → back to login.
+   */
+        action?: "switch" | "pivot" | null;
+      };
+    };
+  }[];
+} & {
+  /** Unique identifier for the flow definition. */
+  id: string;
+  /** Identifier of the project this flow definition belongs to. */
+  project_id: string;
+  /** URI of the flow definition schema this definition was authored against.
+  If the schema_uri was not provided in the request, the flow definition is validated against the latest version of the schema, and the response includes the schema_uri of the latest version.
+   */
+  schema_uri: string;
+  /** Status of the flow definition. */
+  status: string;
+  created_at: string;
+  updated_at: string;
+};

package/src/generated/model/createFlowDefinition400.ts

@@ -0,0 +1,20 @@
+/**
+ * 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 { CreateFlowDefinition400Details } from "./createFlowDefinition400Details";
+
+/**
+ * Standard error payload returned for failed API requests.
+ */
+export type CreateFlowDefinition400 = {
+  /** Stable machine-readable error code. */
+  code: string;
+  /** Human-readable explanation of the error. */
+  message: string;
+  /** Additional error-specific context. */
+  details?: CreateFlowDefinition400Details;
+};

package/src/generated/model/createFlowDefinition400Details.ts

@@ -0,0 +1,12 @@
+/**
+ * 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
+ */
+
+/**
+ * Additional error-specific context.
+ */
+export type CreateFlowDefinition400Details = { [key: string]: unknown };

package/src/generated/model/createFlowDefinition409.ts

@@ -0,0 +1,20 @@
+/**
+ * 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 { CreateFlowDefinition409Details } from "./createFlowDefinition409Details";
+
+/**
+ * Standard error payload returned for failed API requests.
+ */
+export type CreateFlowDefinition409 = {
+  /** Stable machine-readable error code. */
+  code: string;
+  /** Human-readable explanation of the error. */
+  message: string;
+  /** Additional error-specific context. */
+  details?: CreateFlowDefinition409Details;
+};

package/src/generated/model/createFlowDefinition409Details.ts

@@ -0,0 +1,12 @@
+/**
+ * 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
+ */
+
+/**
+ * Additional error-specific context.
+ */
+export type CreateFlowDefinition409Details = { [key: string]: unknown };

package/src/generated/model/createFlowDefinitionBody.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
+ */
+import type { CreateFlowDefinitionBodyFlowDefinition } from "./createFlowDefinitionBodyFlowDefinition";
+
+export type CreateFlowDefinitionBody = {
+  /** @pattern ^[a-zA-Z0-9_-]+$ */
+  project_id: string;
+  /** URI of the server-published flow definition schema this definition was
+  authored against. The server uses this to validate the definition.
+  If not provided, the engine will use the latest schema version for validation.
+   */
+  schema_uri?: string;
+  /** A flow definition is the server-side configuration that describes a complete
+  authentication or identity flow. It is NOT sent to the frontend — the flow
+  engine evaluates it and produces FlowResponse payloads (steps with capability
+  dictionaries) for the client.
+
+  Flow definitions are created by administrators and stored in the project/team
+  configuration hierarchy. The engine selects the matching definition based on
+  the purpose + audience when a flow is created via POST /flow.
+   */
+  flow_definition: CreateFlowDefinitionBodyFlowDefinition;
+};

package/src/generated/model/createFlowDefinitionBodyFlowDefinition.ts

@@ -0,0 +1,58 @@
+/**
+ * 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 { CreateFlowDefinitionBodyFlowDefinitionAudience } from "./createFlowDefinitionBodyFlowDefinitionAudience";
+import type { CreateFlowDefinitionBodyFlowDefinitionStepsItem } from "./createFlowDefinitionBodyFlowDefinitionStepsItem";
+
+/**
+ * A flow definition is the server-side configuration that describes a complete
+authentication or identity flow. It is NOT sent to the frontend — the flow
+engine evaluates it and produces FlowResponse payloads (steps with capability
+dictionaries) for the client.
+
+Flow definitions are created by administrators and stored in the project/team
+configuration hierarchy. The engine selects the matching definition based on
+the purpose + audience when a flow is created via POST /flow.
+
+ */
+export type CreateFlowDefinitionBodyFlowDefinition = {
+  /**
+     * Stable identifier for this flow, used as the target of cross-flow
+  `switch` and `pivot` transitions. Renaming is not supported — the
+  `name` is part of the public contract another definition may
+  reference. Acts as the human display label as well; no separate slug.
+
+     * @pattern ^[a-z][a-z0-9-]*$
+     */
+  name: string;
+  /** User schema this flow operates on. Step `fields` reference properties
+  defined in this schema. The engine resolves field types, validation,
+  and implicit outcomes from schema annotations at runtime.
+   */
+  user_schema: string;
+  /** Maps each purpose this definition handles to its entry-point step.
+  Keys are purpose names; values must match a `name` in `steps`. A
+  definition can serve multiple purposes (e.g. a combined login/register
+  flow) by listing one entry per purpose.
+   */
+  purposes: Partial<
+    Record<"login" | "register" | "recovery" | "profiling" | "reauth" | "link_account", string>
+  >;
+  /** Scopes which teams or apps this flow definition applies to. Empty or
+  omitted fields mean "no restriction"; when both are empty the definition
+  matches every request in the project. The engine picks the most specific
+  matching definition: app > team > project-wide.
+   */
+  audience?: CreateFlowDefinitionBodyFlowDefinitionAudience;
+  /**
+     * Ordered list of steps in this flow. The order is for human readability —
+  actual step sequencing is determined by transitions.
+
+     * @minItems 1
+     */
+  steps: CreateFlowDefinitionBodyFlowDefinitionStepsItem[];
+};

package/src/generated/model/createFlowDefinitionBodyFlowDefinitionAudience.ts

@@ -0,0 +1,21 @@
+/**
+ * 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
+ */
+
+/**
+ * Scopes which teams or apps this flow definition applies to. Empty or
+omitted fields mean "no restriction"; when both are empty the definition
+matches every request in the project. The engine picks the most specific
+matching definition: app > team > project-wide.
+
+ */
+export type CreateFlowDefinitionBodyFlowDefinitionAudience = {
+  /** Restrict to specific teams (organizations). Empty means no team restriction. */
+  team_ids?: string[];
+  /** Restrict to specific applications. Empty means no app restriction. */
+  app_ids?: string[];
+};

package/src/generated/model/createFlowDefinitionBodyFlowDefinitionStepsItem.ts

@@ -0,0 +1,71 @@
+/**
+ * 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 { CreateFlowDefinitionBodyFlowDefinitionStepsItemActions } from "./createFlowDefinitionBodyFlowDefinitionStepsItemActions";
+import type { CreateFlowDefinitionBodyFlowDefinitionStepsItemComplete } from "./createFlowDefinitionBodyFlowDefinitionStepsItemComplete";
+import type { CreateFlowDefinitionBodyFlowDefinitionStepsItemGates } from "./createFlowDefinitionBodyFlowDefinitionStepsItemGates";
+import type { CreateFlowDefinitionBodyFlowDefinitionStepsItemOnSuccess } from "./createFlowDefinitionBodyFlowDefinitionStepsItemOnSuccess";
+import type { CreateFlowDefinitionBodyFlowDefinitionStepsItemSsoProvidersItem } from "./createFlowDefinitionBodyFlowDefinitionStepsItemSsoProvidersItem";
+import type { CreateFlowDefinitionBodyFlowDefinitionStepsItemTransitions } from "./createFlowDefinitionBodyFlowDefinitionStepsItemTransitions";
+
+/**
+ * A step in a flow definition. This is the admin-authored configuration,
+not the runtime payload sent to the frontend.
+
+Steps are schema-driven: `fields` references properties from the flow's
+user schema, and the engine resolves field metadata (type, validation,
+implicit outcomes) from schema annotations at runtime.
+
+A step with only `complete` set is a terminal step. All other steps are
+rendered to the frontend as capability payloads.
+
+ */
+export type CreateFlowDefinitionBodyFlowDefinitionStepsItem = {
+  /** Unique step identifier within this flow. Used as transition targets
+  and returned in the API response as `step.name`.
+   */
+  name: string;
+  /** Schema property names to collect from the user. Each entry references
+  a property in the flow's user schema. The engine resolves field type,
+  validation rules, and implicit outcomes from schema annotations
+  (e.g. a property with `x-unique` set implies a `user_not_found`
+  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.
+   */
+  actions?: CreateFlowDefinitionBodyFlowDefinitionStepsItemActions;
+  /** 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
+  policy.
+   */
+  gates?: CreateFlowDefinitionBodyFlowDefinitionStepsItemGates;
+  /** Available SSO identity providers for this step. */
+  sso_providers?: CreateFlowDefinitionBodyFlowDefinitionStepsItemSsoProvidersItem[];
+  /** Server-side mutation to execute when this step completes successfully.
+  Runs after field validation passes, before the transition fires.
+
+  - create_user: creates the user record (registration flows)
+   */
+  on_success?: CreateFlowDefinitionBodyFlowDefinitionStepsItemOnSuccess;
+  /** Marks this as a terminal step. Tells the frontend what to do:
+  - redirect: navigate to redirect_uri (OIDC/SAML callback done)
+  - show: render as a success/info screen
+   */
+  complete?: CreateFlowDefinitionBodyFlowDefinitionStepsItemComplete;
+  /** Maps action/outcome names to their transition descriptor.
+
+  Keys match action names from the `actions` dict. 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`).
+   */
+  transitions?: CreateFlowDefinitionBodyFlowDefinitionStepsItemTransitions;
+};

package/src/generated/model/createFlowDefinitionBodyFlowDefinitionStepsItemActions.ts

@@ -0,0 +1,29 @@
+/**
+ * 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
+ */
+
+/**
+ * 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.
+
+ */
+export type CreateFlowDefinitionBodyFlowDefinitionStepsItemActions = {
+  [key: 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/createFlowDefinitionBodyFlowDefinitionStepsItemComplete.ts

@@ -0,0 +1,21 @@
+/**
+ * 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
+ */
+
+/**
+ * Marks this as a terminal step. Tells the frontend what to do:
+- redirect: navigate to redirect_uri (OIDC/SAML callback done)
+- show: render as a success/info screen
+
+ */
+export type CreateFlowDefinitionBodyFlowDefinitionStepsItemComplete =
+  (typeof CreateFlowDefinitionBodyFlowDefinitionStepsItemComplete)[keyof typeof CreateFlowDefinitionBodyFlowDefinitionStepsItemComplete];
+
+export const CreateFlowDefinitionBodyFlowDefinitionStepsItemComplete = {
+  redirect: "redirect",
+  show: "show",
+} as const;

package/src/generated/model/createFlowDefinitionBodyFlowDefinitionStepsItemGates.ts

@@ -0,0 +1,35 @@
+/**
+ * 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 { CreateFlowDefinitionBodyFlowDefinitionStepsItemGatesConfig } from "./createFlowDefinitionBodyFlowDefinitionStepsItemGatesConfig";
+import type { CreateFlowDefinitionBodyFlowDefinitionStepsItemGatesKind } from "./createFlowDefinitionBodyFlowDefinitionStepsItemGatesKind";
+
+/**
+ * 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
+policy.
+
+ */
+export type CreateFlowDefinitionBodyFlowDefinitionStepsItemGates = {
+  [key: string]: {
+    /** The gate category. Only `captcha` is currently defined. Authenticator
+  ceremonies (e.g. passkey) are modelled as credential auth_attempts via
+  `x-credential` on a field, not as gates.
+   */
+    kind: CreateFlowDefinitionBodyFlowDefinitionStepsItemGatesKind;
+    /** Provider identifier within the gate kind — e.g. `altcha`, `turnstile`,
+  `hcaptcha`. The engine looks up an implementation in its provider
+  registry.
+   */
+    provider: string;
+    /** Provider-specific configuration consumed by the implementation when
+  issuing the per-render challenge. Opaque to the engine.
+   */
+    config?: CreateFlowDefinitionBodyFlowDefinitionStepsItemGatesConfig;
+  };
+};

package/src/generated/model/createFlowDefinitionBodyFlowDefinitionStepsItemGatesConfig.ts

@@ -0,0 +1,14 @@
+/**
+ * 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
+ */
+
+/**
+ * Provider-specific configuration consumed by the implementation when
+issuing the per-render challenge. Opaque to the engine.
+
+ */
+export type CreateFlowDefinitionBodyFlowDefinitionStepsItemGatesConfig = { [key: string]: unknown };

package/src/generated/model/createFlowDefinitionBodyFlowDefinitionStepsItemGatesKind.ts

@@ -0,0 +1,20 @@
+/**
+ * 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 gate category. Only `captcha` is currently defined. Authenticator
+ceremonies (e.g. passkey) are modelled as credential auth_attempts via
+`x-credential` on a field, not as gates.
+
+ */
+export type CreateFlowDefinitionBodyFlowDefinitionStepsItemGatesKind =
+  (typeof CreateFlowDefinitionBodyFlowDefinitionStepsItemGatesKind)[keyof typeof CreateFlowDefinitionBodyFlowDefinitionStepsItemGatesKind];
+
+export const CreateFlowDefinitionBodyFlowDefinitionStepsItemGatesKind = {
+  captcha: "captcha",
+} as const;

package/src/generated/model/createFlowDefinitionBodyFlowDefinitionStepsItemOnSuccess.ts

@@ -0,0 +1,21 @@
+/**
+ * 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
+ */
+
+/**
+ * Server-side mutation to execute when this step completes successfully.
+Runs after field validation passes, before the transition fires.
+
+- create_user: creates the user record (registration flows)
+
+ */
+export type CreateFlowDefinitionBodyFlowDefinitionStepsItemOnSuccess =
+  (typeof CreateFlowDefinitionBodyFlowDefinitionStepsItemOnSuccess)[keyof typeof CreateFlowDefinitionBodyFlowDefinitionStepsItemOnSuccess];
+
+export const CreateFlowDefinitionBodyFlowDefinitionStepsItemOnSuccess = {
+  create_user: "create_user",
+} as const;

package/src/generated/model/createFlowDefinitionBodyFlowDefinitionStepsItemSsoProvidersItem.ts

@@ -0,0 +1,19 @@
+/**
+ * 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
+ */
+
+/**
+ * An available SSO identity provider.
+ */
+export type CreateFlowDefinitionBodyFlowDefinitionStepsItemSsoProvidersItem = {
+  /** Provider instance identifier. */
+  id: string;
+  /** Display name for the provider. */
+  name: string;
+  /** Template hint for rendering (logo, colors). */
+  template: string;
+};