ory-client 1.1.22 → 1.1.24

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f0bbd43896c812426eec21268e2d71f08ebf671a97b3dec2d25892b2ea43198e
-  data.tar.gz: e6db48183e390ee6e5c55fa59d9eb503bb66ffebf181c57712a399625b217a63
+  metadata.gz: 2d05c2225430d38e12cd1e903511ff8ed7982c13033bfe44a89332e521930b41
+  data.tar.gz: 31a746d232364b16c355258b0e13c3b3c93747e74c612b41a7ced1fe9c9115ad
 SHA512:
-  metadata.gz: 1fdbf8a79f4089708ef5991662d99c34c66420f56e1211a8906bdf645456b88c019a46086bad9b7ddd9555432e343601bc9e33f4770216e992e0276b64d32d29
-  data.tar.gz: 9e1c2136df889471151cd1d6553b32327e312b7d2f3696f8752936efb78155cd8149fe65edba52ec1b6fb6a7b50352334884eb9587146d90694a525790348763
+  metadata.gz: efac28e0ddb58e68b6e85653c990d1a0de5178d60a4759bb12bfe3f1b807729cae2d8b85eab69512173dc8827f4a18244c67ef6b28b61bf4c7e07271f79902e2
+  data.tar.gz: fa0a68ea04f6976711985c2013e12a8bbb461aec10fcfe751d204193c372aca6f3376f79e86f739b6f4c52f9b07c5de92cdb93e48ed253db6e0dd49b5f0880df

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    ory-client (1.1.22)
+    ory-client (1.1.24)
       typhoeus (~> 1.0, >= 1.0.1)
 
 GEM
@@ -17,7 +17,7 @@ GEM
     jaro_winkler (1.5.4)
     method_source (1.0.0)
     parallel (1.22.1)
-    parser (3.2.1.1)
+    parser (3.2.2.0)
       ast (~> 2.4.1)
     pry (0.13.1)
       coderay (~> 1.1)
@@ -38,7 +38,7 @@ GEM
     rspec-expectations (3.12.2)
       diff-lcs (>= 1.2.0, < 2.0)
       rspec-support (~> 3.12.0)
-    rspec-mocks (3.12.4)
+    rspec-mocks (3.12.5)
       diff-lcs (>= 1.2.0, < 2.0)
       rspec-support (~> 3.12.0)
     rspec-support (3.12.0)

data/README.md

@@ -8,8 +8,8 @@ with a valid Personal Access Token. Public APIs are mostly used in browsers.
 
 This SDK is automatically generated by the [OpenAPI Generator](https://openapi-generator.tech) project:
 
-- API version: v1.1.22
-- Package version: v1.1.22
+- API version: v1.1.24
+- Package version: v1.1.24
 - Build package: org.openapitools.codegen.languages.RubyClientCodegen
 
 ## Installation
@@ -25,16 +25,16 @@ gem build ory-client.gemspec
 Then either install the gem locally:
 
 ```shell
-gem install ./ory-client-v1.1.22.gem
+gem install ./ory-client-v1.1.24.gem
 ```
 
-(for development, run `gem install --dev ./ory-client-v1.1.22.gem` to install the development dependencies)
+(for development, run `gem install --dev ./ory-client-v1.1.24.gem` to install the development dependencies)
 
 or publish the gem to a gem hosting service, e.g. [RubyGems](https://rubygems.org/).
 
 Finally add this to the Gemfile:
 
-    gem 'ory-client', '~> v1.1.22'
+    gem 'ory-client', '~> v1.1.24'
 
 ### Install from Git
 
@@ -114,6 +114,7 @@ Class | Method | HTTP request | Description
 *OryClient::FrontendApi* | [**update_registration_flow**](docs/FrontendApi.md#update_registration_flow) | **POST** /self-service/registration | Update Registration Flow
 *OryClient::FrontendApi* | [**update_settings_flow**](docs/FrontendApi.md#update_settings_flow) | **POST** /self-service/settings | Complete Settings Flow
 *OryClient::FrontendApi* | [**update_verification_flow**](docs/FrontendApi.md#update_verification_flow) | **POST** /self-service/verification | Complete Verification Flow
+*OryClient::IdentityApi* | [**batch_patch_identities**](docs/IdentityApi.md#batch_patch_identities) | **PATCH** /admin/identities | Create and deletes multiple identities
 *OryClient::IdentityApi* | [**create_identity**](docs/IdentityApi.md#create_identity) | **POST** /admin/identities | Create an Identity
 *OryClient::IdentityApi* | [**create_recovery_code_for_identity**](docs/IdentityApi.md#create_recovery_code_for_identity) | **POST** /admin/recovery/code | Create a Recovery Code
 *OryClient::IdentityApi* | [**create_recovery_link_for_identity**](docs/IdentityApi.md#create_recovery_link_for_identity) | **POST** /admin/recovery/link | Create a Recovery Link
@@ -210,9 +211,14 @@ Class | Method | HTTP request | Description
  - [OryClient::AcceptOAuth2LoginRequest](docs/AcceptOAuth2LoginRequest.md)
  - [OryClient::ActiveProjectInConsole](docs/ActiveProjectInConsole.md)
  - [OryClient::AuthenticatorAssuranceLevel](docs/AuthenticatorAssuranceLevel.md)
+ - [OryClient::BatchPatchIdentitiesResponse](docs/BatchPatchIdentitiesResponse.md)
  - [OryClient::CheckOplSyntaxResult](docs/CheckOplSyntaxResult.md)
  - [OryClient::CheckPermissionResult](docs/CheckPermissionResult.md)
  - [OryClient::CloudAccount](docs/CloudAccount.md)
+ - [OryClient::ContinueWith](docs/ContinueWith.md)
+ - [OryClient::ContinueWithSetOrySessionToken](docs/ContinueWithSetOrySessionToken.md)
+ - [OryClient::ContinueWithVerificationUi](docs/ContinueWithVerificationUi.md)
+ - [OryClient::ContinueWithVerificationUiFlow](docs/ContinueWithVerificationUiFlow.md)
  - [OryClient::CourierMessageStatus](docs/CourierMessageStatus.md)
  - [OryClient::CourierMessageType](docs/CourierMessageType.md)
  - [OryClient::CreateCustomDomainBody](docs/CreateCustomDomainBody.md)
@@ -248,6 +254,8 @@ Class | Method | HTTP request | Description
  - [OryClient::IdentityCredentialsOidcProvider](docs/IdentityCredentialsOidcProvider.md)
  - [OryClient::IdentityCredentialsPassword](docs/IdentityCredentialsPassword.md)
  - [OryClient::IdentityCredentialsType](docs/IdentityCredentialsType.md)
+ - [OryClient::IdentityPatch](docs/IdentityPatch.md)
+ - [OryClient::IdentityPatchResponse](docs/IdentityPatchResponse.md)
  - [OryClient::IdentitySchemaContainer](docs/IdentitySchemaContainer.md)
  - [OryClient::IdentitySchemaPreset](docs/IdentitySchemaPreset.md)
  - [OryClient::IdentityState](docs/IdentityState.md)
@@ -259,6 +267,7 @@ Class | Method | HTTP request | Description
  - [OryClient::IdentityWithCredentialsPasswordConfig](docs/IdentityWithCredentialsPasswordConfig.md)
  - [OryClient::InternalGetProjectBrandingBody](docs/InternalGetProjectBrandingBody.md)
  - [OryClient::InternalIsOwnerForProjectBySlugBody](docs/InternalIsOwnerForProjectBySlugBody.md)
+ - [OryClient::InternalIsOwnerForProjectBySlugResponse](docs/InternalIsOwnerForProjectBySlugResponse.md)
  - [OryClient::InternalProvisionMockSubscription](docs/InternalProvisionMockSubscription.md)
  - [OryClient::IntrospectedOAuth2Token](docs/IntrospectedOAuth2Token.md)
  - [OryClient::IsOwnerForProjectBySlug](docs/IsOwnerForProjectBySlug.md)
@@ -296,6 +305,7 @@ Class | Method | HTTP request | Description
  - [OryClient::Pagination](docs/Pagination.md)
  - [OryClient::PaginationHeaders](docs/PaginationHeaders.md)
  - [OryClient::ParseError](docs/ParseError.md)
+ - [OryClient::PatchIdentitiesBody](docs/PatchIdentitiesBody.md)
  - [OryClient::PerformNativeLogoutBody](docs/PerformNativeLogoutBody.md)
  - [OryClient::Plan](docs/Plan.md)
  - [OryClient::PlanDetails](docs/PlanDetails.md)

data/docs/BatchPatchIdentitiesResponse.md

@@ -0,0 +1,18 @@
+# OryClient::BatchPatchIdentitiesResponse
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **identities** | [**Array<IdentityPatchResponse>**](IdentityPatchResponse.md) | The patch responses for the individual identities. | [optional] |
+
+## Example
+
+```ruby
+require 'ory-client'
+
+instance = OryClient::BatchPatchIdentitiesResponse.new(
+  identities: null
+)
+```
+

data/docs/ContinueWith.md

@@ -0,0 +1,78 @@
+# OryClient::ContinueWith
+
+## Class instance methods
+
+### `openapi_one_of`
+
+Returns the list of classes defined in oneOf.
+
+#### Example
+
+```ruby
+require 'ory-client'
+
+OryClient::ContinueWith.openapi_one_of
+# =>
+# [
+#   :'ContinueWithSetOrySessionToken',
+#   :'ContinueWithVerificationUi'
+# ]
+```
+
+### `openapi_discriminator_name`
+
+Returns the discriminator's property name.
+
+#### Example
+
+```ruby
+require 'ory-client'
+
+OryClient::ContinueWith.openapi_discriminator_name
+# => :'action'
+```
+
+### `openapi_discriminator_name`
+
+Returns the discriminator's mapping.
+
+#### Example
+
+```ruby
+require 'ory-client'
+
+OryClient::ContinueWith.openapi_discriminator_mapping
+# =>
+# {
+#   :'set_ory_session_token' => :'ContinueWithSetOrySessionToken',
+#   :'show_verification_ui' => :'ContinueWithVerificationUi'
+# }
+
+### build
+
+Find the appropriate object from the `openapi_one_of` list and casts the data into it.
+
+#### Example
+
+```ruby
+require 'ory-client'
+
+OryClient::ContinueWith.build(data)
+# => #<ContinueWithSetOrySessionToken:0x00007fdd4aab02a0>
+
+OryClient::ContinueWith.build(data_that_doesnt_match)
+# => nil
+```
+
+#### Parameters
+
+| Name | Type | Description |
+| ---- | ---- | ----------- |
+| **data** | **Mixed** | data to be matched against the list of oneOf items |
+
+#### Return type
+
+- `ContinueWithSetOrySessionToken`
+- `ContinueWithVerificationUi`
+- `nil` (if no type matches)
+

data/docs/ContinueWithSetOrySessionToken.md

@@ -0,0 +1,20 @@
+# OryClient::ContinueWithSetOrySessionToken
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **action** | **String** | Action will always be `set_ory_session_token` set_ory_session_token ContinueWithActionSetOrySessionToken show_verification_ui ContinueWithActionShowVerificationUI |  |
+| **ory_session_token** | **String** | Token is the token of the session |  |
+
+## Example
+
+```ruby
+require 'ory-client'
+
+instance = OryClient::ContinueWithSetOrySessionToken.new(
+  action: null,
+  ory_session_token: null
+)
+```
+

data/docs/ContinueWithVerificationUi.md

@@ -0,0 +1,20 @@
+# OryClient::ContinueWithVerificationUi
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **action** | **String** | Action will always be `show_verification_ui` set_ory_session_token ContinueWithActionSetOrySessionToken show_verification_ui ContinueWithActionShowVerificationUI |  |
+| **flow** | [**ContinueWithVerificationUiFlow**](ContinueWithVerificationUiFlow.md) |  |  |
+
+## Example
+
+```ruby
+require 'ory-client'
+
+instance = OryClient::ContinueWithVerificationUi.new(
+  action: null,
+  flow: null
+)
+```
+

data/docs/ContinueWithVerificationUiFlow.md

@@ -0,0 +1,22 @@
+# OryClient::ContinueWithVerificationUiFlow
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **id** | **String** | The ID of the verification flow |  |
+| **url** | **String** | The URL of the verification flow | [optional] |
+| **verifiable_address** | **String** | The address that should be verified in this flow |  |
+
+## Example
+
+```ruby
+require 'ory-client'
+
+instance = OryClient::ContinueWithVerificationUiFlow.new(
+  id: null,
+  url: null,
+  verifiable_address: null
+)
+```
+

data/docs/FrontendApi.md

@@ -385,7 +385,7 @@ No authorization required
 
 Create Verification Flow for Browser Clients
 
-This endpoint initializes a browser-based account verification flow. Once initialized, the browser will be redirected to `selfservice.flows.verification.ui_url` with the flow ID set as the query parameter `?flow=`.  If this endpoint is called via an AJAX request, the response contains the recovery flow without any redirects.  This endpoint is NOT INTENDED for API clients and only works with browsers (Chrome, Firefox, ...).  More information can be found at [Ory Kratos Email and Phone Verification Documentation](https://www.ory.sh/docs/kratos/selfservice/flows/verify-email-account-activation).
+This endpoint initializes a browser-based account verification flow. Once initialized, the browser will be redirected to `selfservice.flows.verification.ui_url` with the flow ID set as the query parameter `?flow=`.  If this endpoint is called via an AJAX request, the response contains the recovery flow without any redirects.  This endpoint is NOT INTENDED for API clients and only works with browsers (Chrome, Firefox, ...).  More information can be found at [Ory Kratos Email and Phone Verification Documentation](https://www.ory.sh/docs/kratos/self-service/flows/verify-email-account-activation).
 
 ### Examples
 
@@ -1245,7 +1245,7 @@ No authorization required
 
 Get Verification Flow
 
-This endpoint returns a verification flow's context with, for example, error details and other information.  Browser flows expect the anti-CSRF cookie to be included in the request's HTTP Cookie Header. For AJAX requests you must ensure that cookies are included in the request or requests will fail.  If you use the browser-flow for server-side apps, the services need to run on a common top-level-domain and you need to forward the incoming HTTP Cookie header to this endpoint:  ```js pseudo-code example router.get('/recovery', async function (req, res) { const flow = await client.getVerificationFlow(req.header('cookie'), req.query['flow'])  res.render('verification', flow) })  More information can be found at [Ory Kratos Email and Phone Verification Documentation](https://www.ory.sh/docs/kratos/selfservice/flows/verify-email-account-activation).
+This endpoint returns a verification flow's context with, for example, error details and other information.  Browser flows expect the anti-CSRF cookie to be included in the request's HTTP Cookie Header. For AJAX requests you must ensure that cookies are included in the request or requests will fail.  If you use the browser-flow for server-side apps, the services need to run on a common top-level-domain and you need to forward the incoming HTTP Cookie header to this endpoint:  ```js pseudo-code example router.get('/recovery', async function (req, res) { const flow = await client.getVerificationFlow(req.header('cookie'), req.query['flow'])  res.render('verification', flow) }) ```  More information can be found at [Ory Kratos Email and Phone Verification Documentation](https://www.ory.sh/docs/kratos/self-service/flows/verify-email-account-activation).
 
 ### Examples
 
@@ -1930,7 +1930,7 @@ No authorization required
 
 Complete Verification Flow
 
-Use this endpoint to complete a verification flow. This endpoint behaves differently for API and browser flows and has several states:  `choose_method` expects `flow` (in the URL query) and `email` (in the body) to be sent and works with API- and Browser-initiated flows. For API clients and Browser clients with HTTP Header `Accept: application/json` it either returns a HTTP 200 OK when the form is valid and HTTP 400 OK when the form is invalid and a HTTP 303 See Other redirect with a fresh verification flow if the flow was otherwise invalid (e.g. expired). For Browser clients without HTTP Header `Accept` or with `Accept: text/*` it returns a HTTP 303 See Other redirect to the Verification UI URL with the Verification Flow ID appended. `sent_email` is the success state after `choose_method` when using the `link` method and allows the user to request another verification email. It works for both API and Browser-initiated flows and returns the same responses as the flow in `choose_method` state. `passed_challenge` expects a `token` to be sent in the URL query and given the nature of the flow (\"sending a verification link\") does not have any API capabilities. The server responds with a HTTP 303 See Other redirect either to the Settings UI URL (if the link was valid) and instructs the user to update their password, or a redirect to the Verification UI URL with a new Verification Flow ID which contains an error message that the verification link was invalid.  More information can be found at [Ory Kratos Email and Phone Verification Documentation](https://www.ory.sh/docs/kratos/selfservice/flows/verify-email-account-activation).
+Use this endpoint to complete a verification flow. This endpoint behaves differently for API and browser flows and has several states:  `choose_method` expects `flow` (in the URL query) and `email` (in the body) to be sent and works with API- and Browser-initiated flows. For API clients and Browser clients with HTTP Header `Accept: application/json` it either returns a HTTP 200 OK when the form is valid and HTTP 400 OK when the form is invalid and a HTTP 303 See Other redirect with a fresh verification flow if the flow was otherwise invalid (e.g. expired). For Browser clients without HTTP Header `Accept` or with `Accept: text/*` it returns a HTTP 303 See Other redirect to the Verification UI URL with the Verification Flow ID appended. `sent_email` is the success state after `choose_method` when using the `link` method and allows the user to request another verification email. It works for both API and Browser-initiated flows and returns the same responses as the flow in `choose_method` state. `passed_challenge` expects a `token` to be sent in the URL query and given the nature of the flow (\"sending a verification link\") does not have any API capabilities. The server responds with a HTTP 303 See Other redirect either to the Settings UI URL (if the link was valid) and instructs the user to update their password, or a redirect to the Verification UI URL with a new Verification Flow ID which contains an error message that the verification link was invalid.  More information can be found at [Ory Kratos Email and Phone Verification Documentation](https://www.ory.sh/docs/kratos/self-service/flows/verify-email-account-activation).
 
 ### Examples
 

data/docs/IdentityApi.md

@@ -4,6 +4,7 @@ All URIs are relative to *https://playground.projects.oryapis.com*
 
 | Method | HTTP request | Description |
 | ------ | ------------ | ----------- |
+| [**batch_patch_identities**](IdentityApi.md#batch_patch_identities) | **PATCH** /admin/identities | Create and deletes multiple identities |
 | [**create_identity**](IdentityApi.md#create_identity) | **POST** /admin/identities | Create an Identity |
 | [**create_recovery_code_for_identity**](IdentityApi.md#create_recovery_code_for_identity) | **POST** /admin/recovery/code | Create a Recovery Code |
 | [**create_recovery_link_for_identity**](IdentityApi.md#create_recovery_link_for_identity) | **POST** /admin/recovery/link | Create a Recovery Link |
@@ -23,6 +24,77 @@ All URIs are relative to *https://playground.projects.oryapis.com*
 | [**update_identity**](IdentityApi.md#update_identity) | **PUT** /admin/identities/{id} | Update an Identity |
 
 
+## batch_patch_identities
+
+> <BatchPatchIdentitiesResponse> batch_patch_identities(opts)
+
+Create and deletes multiple identities
+
+Creates or delete multiple [identities](https://www.ory.sh/docs/kratos/concepts/identity-user-model). This endpoint can also be used to [import credentials](https://www.ory.sh/docs/kratos/manage-identities/import-user-accounts-identities) for instance passwords, social sign in configurations or multifactor methods.
+
+### Examples
+
+```ruby
+require 'time'
+require 'ory-client'
+# setup authorization
+OryClient.configure do |config|
+  # Configure Bearer authorization: oryAccessToken
+  config.access_token = 'YOUR_BEARER_TOKEN'
+end
+
+api_instance = OryClient::IdentityApi.new
+opts = {
+  patch_identities_body: OryClient::PatchIdentitiesBody.new # PatchIdentitiesBody | 
+}
+
+begin
+  # Create and deletes multiple identities
+  result = api_instance.batch_patch_identities(opts)
+  p result
+rescue OryClient::ApiError => e
+  puts "Error when calling IdentityApi->batch_patch_identities: #{e}"
+end
+```
+
+#### Using the batch_patch_identities_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<BatchPatchIdentitiesResponse>, Integer, Hash)> batch_patch_identities_with_http_info(opts)
+
+```ruby
+begin
+  # Create and deletes multiple identities
+  data, status_code, headers = api_instance.batch_patch_identities_with_http_info(opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <BatchPatchIdentitiesResponse>
+rescue OryClient::ApiError => e
+  puts "Error when calling IdentityApi->batch_patch_identities_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **patch_identities_body** | [**PatchIdentitiesBody**](PatchIdentitiesBody.md) |  | [optional] |
+
+### Return type
+
+[**BatchPatchIdentitiesResponse**](BatchPatchIdentitiesResponse.md)
+
+### Authorization
+
+[oryAccessToken](../README.md#oryAccessToken)
+
+### HTTP request headers
+
+- **Content-Type**: application/json
+- **Accept**: application/json
+
+
 ## create_identity
 
 > <Identity> create_identity(opts)

data/docs/IdentityPatch.md

@@ -0,0 +1,20 @@
+# OryClient::IdentityPatch
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **create** | [**CreateIdentityBody**](CreateIdentityBody.md) |  | [optional] |
+| **patch_id** | **String** | The ID of this patch.  The patch ID is optional. If specified, the ID will be returned in the response, so consumers of this API can correlate the response with the patch. | [optional] |
+
+## Example
+
+```ruby
+require 'ory-client'
+
+instance = OryClient::IdentityPatch.new(
+  create: null,
+  patch_id: null
+)
+```
+

data/docs/IdentityPatchResponse.md

@@ -0,0 +1,22 @@
+# OryClient::IdentityPatchResponse
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **action** | **String** | The action for this specific patch create ActionCreate  Create this identity. | [optional] |
+| **identity** | **String** | The identity ID payload of this patch | [optional] |
+| **patch_id** | **String** | The ID of this patch response, if an ID was specified in the patch. | [optional] |
+
+## Example
+
+```ruby
+require 'ory-client'
+
+instance = OryClient::IdentityPatchResponse.new(
+  action: null,
+  identity: null,
+  patch_id: null
+)
+```
+

data/docs/InternalIsOwnerForProjectBySlugBody.md

@@ -4,9 +4,10 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
+| **namespace** | **String** | Namespace is the namespace of the subject. |  |
 | **project_scope** | **String** | ProjectScope is the project_id resolved from the API Token. | [optional] |
 | **project_slug** | **String** | ProjectSlug is the project's slug. |  |
-| **subject** | **String** | Subject is the subject from the API Token. |  |
+| **subject** | **String** | Subject is the subject acting (user or API key). |  |
 
 ## Example
 
@@ -14,6 +15,7 @@
 require 'ory-client'
 
 instance = OryClient::InternalIsOwnerForProjectBySlugBody.new(
+  namespace: null,
   project_scope: null,
   project_slug: null,
   subject: null

data/docs/InternalIsOwnerForProjectBySlugResponse.md

@@ -0,0 +1,18 @@
+# OryClient::InternalIsOwnerForProjectBySlugResponse
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **project_id** | **String** | ProjectID is the project's ID. |  |
+
+## Example
+
+```ruby
+require 'ory-client'
+
+instance = OryClient::InternalIsOwnerForProjectBySlugResponse.new(
+  project_id: null
+)
+```
+

data/docs/PatchIdentitiesBody.md

@@ -0,0 +1,18 @@
+# OryClient::PatchIdentitiesBody
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **identities** | [**Array<IdentityPatch>**](IdentityPatch.md) | Identities holds the list of patches to apply  required | [optional] |
+
+## Example
+
+```ruby
+require 'ory-client'
+
+instance = OryClient::PatchIdentitiesBody.new(
+  identities: null
+)
+```
+

data/docs/SettingsFlow.md

@@ -5,6 +5,7 @@
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
 | **active** | **String** | Active, if set, contains the registration method that is being used. It is initially not set. | [optional] |
+| **continue_with** | [**Array<ContinueWith>**](ContinueWith.md) | Contains a list of actions, that could follow this flow  It can, for example, contain a reference to the verification flow, created as part of the user's registration. | [optional] |
 | **expires_at** | **Time** | ExpiresAt is the time (UTC) when the flow expires. If the user still wishes to update the setting, a new flow has to be initiated. |  |
 | **id** | **String** | ID represents the flow's unique ID. When performing the settings flow, this represents the id in the settings ui's query parameter: http://<selfservice.flows.settings.ui_url>?flow=<id> |  |
 | **identity** | [**Identity**](Identity.md) |  |  |
@@ -22,6 +23,7 @@ require 'ory-client'
 
 instance = OryClient::SettingsFlow.new(
   active: null,
+  continue_with: null,
   expires_at: null,
   id: null,
   identity: null,

data/docs/SuccessfulNativeRegistration.md

@@ -4,6 +4,7 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
+| **continue_with** | [**Array<ContinueWith>**](ContinueWith.md) | Contains a list of actions, that could follow this flow  It can, for example, this will contain a reference to the verification flow, created as part of the user's registration or the token of the session. | [optional] |
 | **identity** | [**Identity**](Identity.md) |  |  |
 | **session** | [**Session**](Session.md) |  | [optional] |
 | **session_token** | **String** | The Session Token  This field is only set when the session hook is configured as a post-registration hook.  A session token is equivalent to a session cookie, but it can be sent in the HTTP Authorization Header:  Authorization: bearer ${session-token}  The session token is only issued for API flows, not for Browser flows! | [optional] |
@@ -14,6 +15,7 @@
 require 'ory-client'
 
 instance = OryClient::SuccessfulNativeRegistration.new(
+  continue_with: null,
   identity: null,
   session: null,
   session_token: null

data/lib/ory-client/api/courier_api.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers. 
 
-The version of the OpenAPI document: v1.1.22
+The version of the OpenAPI document: v1.1.24
 Contact: support@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.0.1

data/lib/ory-client/api/frontend_api.rb

@@ -3,7 +3,7 @@
 
 #Documentation for all public and administrative Ory APIs. Administrative APIs can only be accessed with a valid Personal Access Token. Public APIs are mostly used in browsers. 
 
-The version of the OpenAPI document: v1.1.22
+The version of the OpenAPI document: v1.1.24
 Contact: support@ory.sh
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.0.1
@@ -341,7 +341,7 @@ module OryClient
     end
 
     # Create Verification Flow for Browser Clients
-    # This endpoint initializes a browser-based account verification flow. Once initialized, the browser will be redirected to `selfservice.flows.verification.ui_url` with the flow ID set as the query parameter `?flow=`.  If this endpoint is called via an AJAX request, the response contains the recovery flow without any redirects.  This endpoint is NOT INTENDED for API clients and only works with browsers (Chrome, Firefox, ...).  More information can be found at [Ory Kratos Email and Phone Verification Documentation](https://www.ory.sh/docs/kratos/selfservice/flows/verify-email-account-activation).
+    # This endpoint initializes a browser-based account verification flow. Once initialized, the browser will be redirected to `selfservice.flows.verification.ui_url` with the flow ID set as the query parameter `?flow=`.  If this endpoint is called via an AJAX request, the response contains the recovery flow without any redirects.  This endpoint is NOT INTENDED for API clients and only works with browsers (Chrome, Firefox, ...).  More information can be found at [Ory Kratos Email and Phone Verification Documentation](https://www.ory.sh/docs/kratos/self-service/flows/verify-email-account-activation).
     # @param [Hash] opts the optional parameters
     # @option opts [String] :return_to The URL to return the browser to after the flow was completed.
     # @return [VerificationFlow]
@@ -351,7 +351,7 @@ module OryClient
     end
 
     # Create Verification Flow for Browser Clients
-    # This endpoint initializes a browser-based account verification flow. Once initialized, the browser will be redirected to `selfservice.flows.verification.ui_url` with the flow ID set as the query parameter `?flow=`.  If this endpoint is called via an AJAX request, the response contains the recovery flow without any redirects.  This endpoint is NOT INTENDED for API clients and only works with browsers (Chrome, Firefox, ...).  More information can be found at [Ory Kratos Email and Phone Verification Documentation](https://www.ory.sh/docs/kratos/selfservice/flows/verify-email-account-activation).
+    # This endpoint initializes a browser-based account verification flow. Once initialized, the browser will be redirected to `selfservice.flows.verification.ui_url` with the flow ID set as the query parameter `?flow=`.  If this endpoint is called via an AJAX request, the response contains the recovery flow without any redirects.  This endpoint is NOT INTENDED for API clients and only works with browsers (Chrome, Firefox, ...).  More information can be found at [Ory Kratos Email and Phone Verification Documentation](https://www.ory.sh/docs/kratos/self-service/flows/verify-email-account-activation).
     # @param [Hash] opts the optional parameters
     # @option opts [String] :return_to The URL to return the browser to after the flow was completed.
     # @return [Array<(VerificationFlow, Integer, Hash)>] VerificationFlow data, response status code and response headers
@@ -1165,7 +1165,7 @@ module OryClient
     end
 
     # Get Verification Flow
-    # This endpoint returns a verification flow's context with, for example, error details and other information.  Browser flows expect the anti-CSRF cookie to be included in the request's HTTP Cookie Header. For AJAX requests you must ensure that cookies are included in the request or requests will fail.  If you use the browser-flow for server-side apps, the services need to run on a common top-level-domain and you need to forward the incoming HTTP Cookie header to this endpoint:  ```js pseudo-code example router.get('/recovery', async function (req, res) { const flow = await client.getVerificationFlow(req.header('cookie'), req.query['flow'])  res.render('verification', flow) })  More information can be found at [Ory Kratos Email and Phone Verification Documentation](https://www.ory.sh/docs/kratos/selfservice/flows/verify-email-account-activation).
+    # This endpoint returns a verification flow's context with, for example, error details and other information.  Browser flows expect the anti-CSRF cookie to be included in the request's HTTP Cookie Header. For AJAX requests you must ensure that cookies are included in the request or requests will fail.  If you use the browser-flow for server-side apps, the services need to run on a common top-level-domain and you need to forward the incoming HTTP Cookie header to this endpoint:  ```js pseudo-code example router.get('/recovery', async function (req, res) { const flow = await client.getVerificationFlow(req.header('cookie'), req.query['flow'])  res.render('verification', flow) }) ```  More information can be found at [Ory Kratos Email and Phone Verification Documentation](https://www.ory.sh/docs/kratos/self-service/flows/verify-email-account-activation).
     # @param id [String] The Flow ID  The value for this parameter comes from &#x60;request&#x60; URL Query parameter sent to your application (e.g. &#x60;/verification?flow&#x3D;abcde&#x60;).
     # @param [Hash] opts the optional parameters
     # @option opts [String] :cookie HTTP Cookies  When using the SDK on the server side you must include the HTTP Cookie Header originally sent to your HTTP handler here.
@@ -1176,7 +1176,7 @@ module OryClient
     end
 
     # Get Verification Flow
-    # This endpoint returns a verification flow&#39;s context with, for example, error details and other information.  Browser flows expect the anti-CSRF cookie to be included in the request&#39;s HTTP Cookie Header. For AJAX requests you must ensure that cookies are included in the request or requests will fail.  If you use the browser-flow for server-side apps, the services need to run on a common top-level-domain and you need to forward the incoming HTTP Cookie header to this endpoint:  &#x60;&#x60;&#x60;js pseudo-code example router.get(&#39;/recovery&#39;, async function (req, res) { const flow &#x3D; await client.getVerificationFlow(req.header(&#39;cookie&#39;), req.query[&#39;flow&#39;])  res.render(&#39;verification&#39;, flow) })  More information can be found at [Ory Kratos Email and Phone Verification Documentation](https://www.ory.sh/docs/kratos/selfservice/flows/verify-email-account-activation).
+    # This endpoint returns a verification flow&#39;s context with, for example, error details and other information.  Browser flows expect the anti-CSRF cookie to be included in the request&#39;s HTTP Cookie Header. For AJAX requests you must ensure that cookies are included in the request or requests will fail.  If you use the browser-flow for server-side apps, the services need to run on a common top-level-domain and you need to forward the incoming HTTP Cookie header to this endpoint:  &#x60;&#x60;&#x60;js pseudo-code example router.get(&#39;/recovery&#39;, async function (req, res) { const flow &#x3D; await client.getVerificationFlow(req.header(&#39;cookie&#39;), req.query[&#39;flow&#39;])  res.render(&#39;verification&#39;, flow) }) &#x60;&#x60;&#x60;  More information can be found at [Ory Kratos Email and Phone Verification Documentation](https://www.ory.sh/docs/kratos/self-service/flows/verify-email-account-activation).
     # @param id [String] The Flow ID  The value for this parameter comes from &#x60;request&#x60; URL Query parameter sent to your application (e.g. &#x60;/verification?flow&#x3D;abcde&#x60;).
     # @param [Hash] opts the optional parameters
     # @option opts [String] :cookie HTTP Cookies  When using the SDK on the server side you must include the HTTP Cookie Header originally sent to your HTTP handler here.
@@ -1885,7 +1885,7 @@ module OryClient
     end
 
     # Complete Verification Flow
-    # Use this endpoint to complete a verification flow. This endpoint behaves differently for API and browser flows and has several states:  `choose_method` expects `flow` (in the URL query) and `email` (in the body) to be sent and works with API- and Browser-initiated flows. For API clients and Browser clients with HTTP Header `Accept: application/json` it either returns a HTTP 200 OK when the form is valid and HTTP 400 OK when the form is invalid and a HTTP 303 See Other redirect with a fresh verification flow if the flow was otherwise invalid (e.g. expired). For Browser clients without HTTP Header `Accept` or with `Accept: text/*` it returns a HTTP 303 See Other redirect to the Verification UI URL with the Verification Flow ID appended. `sent_email` is the success state after `choose_method` when using the `link` method and allows the user to request another verification email. It works for both API and Browser-initiated flows and returns the same responses as the flow in `choose_method` state. `passed_challenge` expects a `token` to be sent in the URL query and given the nature of the flow (\"sending a verification link\") does not have any API capabilities. The server responds with a HTTP 303 See Other redirect either to the Settings UI URL (if the link was valid) and instructs the user to update their password, or a redirect to the Verification UI URL with a new Verification Flow ID which contains an error message that the verification link was invalid.  More information can be found at [Ory Kratos Email and Phone Verification Documentation](https://www.ory.sh/docs/kratos/selfservice/flows/verify-email-account-activation).
+    # Use this endpoint to complete a verification flow. This endpoint behaves differently for API and browser flows and has several states:  `choose_method` expects `flow` (in the URL query) and `email` (in the body) to be sent and works with API- and Browser-initiated flows. For API clients and Browser clients with HTTP Header `Accept: application/json` it either returns a HTTP 200 OK when the form is valid and HTTP 400 OK when the form is invalid and a HTTP 303 See Other redirect with a fresh verification flow if the flow was otherwise invalid (e.g. expired). For Browser clients without HTTP Header `Accept` or with `Accept: text/*` it returns a HTTP 303 See Other redirect to the Verification UI URL with the Verification Flow ID appended. `sent_email` is the success state after `choose_method` when using the `link` method and allows the user to request another verification email. It works for both API and Browser-initiated flows and returns the same responses as the flow in `choose_method` state. `passed_challenge` expects a `token` to be sent in the URL query and given the nature of the flow (\"sending a verification link\") does not have any API capabilities. The server responds with a HTTP 303 See Other redirect either to the Settings UI URL (if the link was valid) and instructs the user to update their password, or a redirect to the Verification UI URL with a new Verification Flow ID which contains an error message that the verification link was invalid.  More information can be found at [Ory Kratos Email and Phone Verification Documentation](https://www.ory.sh/docs/kratos/self-service/flows/verify-email-account-activation).
     # @param flow [String] The Verification Flow ID  The value for this parameter comes from &#x60;flow&#x60; URL Query parameter sent to your application (e.g. &#x60;/verification?flow&#x3D;abcde&#x60;).
     # @param update_verification_flow_body [UpdateVerificationFlowBody] 
     # @param [Hash] opts the optional parameters
@@ -1898,7 +1898,7 @@ module OryClient
     end
 
     # Complete Verification Flow
-    # Use this endpoint to complete a verification flow. This endpoint behaves differently for API and browser flows and has several states:  &#x60;choose_method&#x60; expects &#x60;flow&#x60; (in the URL query) and &#x60;email&#x60; (in the body) to be sent and works with API- and Browser-initiated flows. For API clients and Browser clients with HTTP Header &#x60;Accept: application/json&#x60; it either returns a HTTP 200 OK when the form is valid and HTTP 400 OK when the form is invalid and a HTTP 303 See Other redirect with a fresh verification flow if the flow was otherwise invalid (e.g. expired). For Browser clients without HTTP Header &#x60;Accept&#x60; or with &#x60;Accept: text/*&#x60; it returns a HTTP 303 See Other redirect to the Verification UI URL with the Verification Flow ID appended. &#x60;sent_email&#x60; is the success state after &#x60;choose_method&#x60; when using the &#x60;link&#x60; method and allows the user to request another verification email. It works for both API and Browser-initiated flows and returns the same responses as the flow in &#x60;choose_method&#x60; state. &#x60;passed_challenge&#x60; expects a &#x60;token&#x60; to be sent in the URL query and given the nature of the flow (\&quot;sending a verification link\&quot;) does not have any API capabilities. The server responds with a HTTP 303 See Other redirect either to the Settings UI URL (if the link was valid) and instructs the user to update their password, or a redirect to the Verification UI URL with a new Verification Flow ID which contains an error message that the verification link was invalid.  More information can be found at [Ory Kratos Email and Phone Verification Documentation](https://www.ory.sh/docs/kratos/selfservice/flows/verify-email-account-activation).
+    # Use this endpoint to complete a verification flow. This endpoint behaves differently for API and browser flows and has several states:  &#x60;choose_method&#x60; expects &#x60;flow&#x60; (in the URL query) and &#x60;email&#x60; (in the body) to be sent and works with API- and Browser-initiated flows. For API clients and Browser clients with HTTP Header &#x60;Accept: application/json&#x60; it either returns a HTTP 200 OK when the form is valid and HTTP 400 OK when the form is invalid and a HTTP 303 See Other redirect with a fresh verification flow if the flow was otherwise invalid (e.g. expired). For Browser clients without HTTP Header &#x60;Accept&#x60; or with &#x60;Accept: text/*&#x60; it returns a HTTP 303 See Other redirect to the Verification UI URL with the Verification Flow ID appended. &#x60;sent_email&#x60; is the success state after &#x60;choose_method&#x60; when using the &#x60;link&#x60; method and allows the user to request another verification email. It works for both API and Browser-initiated flows and returns the same responses as the flow in &#x60;choose_method&#x60; state. &#x60;passed_challenge&#x60; expects a &#x60;token&#x60; to be sent in the URL query and given the nature of the flow (\&quot;sending a verification link\&quot;) does not have any API capabilities. The server responds with a HTTP 303 See Other redirect either to the Settings UI URL (if the link was valid) and instructs the user to update their password, or a redirect to the Verification UI URL with a new Verification Flow ID which contains an error message that the verification link was invalid.  More information can be found at [Ory Kratos Email and Phone Verification Documentation](https://www.ory.sh/docs/kratos/self-service/flows/verify-email-account-activation).
     # @param flow [String] The Verification Flow ID  The value for this parameter comes from &#x60;flow&#x60; URL Query parameter sent to your application (e.g. &#x60;/verification?flow&#x3D;abcde&#x60;).
     # @param update_verification_flow_body [UpdateVerificationFlowBody] 
     # @param [Hash] opts the optional parameters