ory-hydra-client 1.9.0.alpha3 → 1.10.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 6fc3feab8ceac23be59e1cc2ada34435556480a971f08df6e6a70db6050e6795
-  data.tar.gz: 74a6991933d11341ca2f5c0bd340b6b1ee7dbb0d60bc8e6ab990b09568b9d87f
+  metadata.gz: 1efb3a82132599def96fdfc67c815fbd7b4ef02eadf8af2dafee974645940aa1
+  data.tar.gz: 791e34b0dc8bfc819c4899eeffa13b44ece11192e96b4aa33a8a9444b854dd13
 SHA512:
-  metadata.gz: 94db7b387872dc48ce234d471a09550e80574a5501c55a592f0596d6f9c7db20854d5e124316496c975975fd3cd7f95da6c20d81f05d17c224314d2ee0db9f72
-  data.tar.gz: ba73bee6c707fbc351d79e0a0b5c06a0cecde1e2bbbc1449f9f3233a2b33f56d772bce923d1494c18372be152212bf0ea5c689116257d5bce74e85006eb1ea0e
+  metadata.gz: 4ca26f02b1e07372b0dbfd43b098aa9636c687b9878897432b101abc65d7367f91f7ead11205ee9722f9ca4edcfb880da5b8905a26a2801c2de1db51b07251cd
+  data.tar.gz: bb980cb227f164d85427c52be786cffd5fb9ab8bb02efb02262deca8a2379eeb6ca2c4887b918d9a9b6d6d4b82062a11dc2838f1bd601be252c8bc86d2dcfa9b

data/README.md

@@ -6,8 +6,8 @@ Welcome to the ORY Hydra HTTP API documentation. You will find documentation for
 
 This SDK is automatically generated by the [OpenAPI Generator](https://openapi-generator.tech) project:
 
-- API version: v1.9.0-alpha.3
-- Package version: v1.9.0-alpha.3
+- API version: v1.10.3
+- Package version: v1.10.3
 - Build package: org.openapitools.codegen.languages.RubyClientCodegen
 
 ## Installation
@@ -23,16 +23,16 @@ gem build ory-hydra-client.gemspec
 Then either install the gem locally:
 
 ```shell
-gem install ./ory-hydra-client-v1.9.0-alpha.3.gem
+gem install ./ory-hydra-client-v1.10.3.gem
 ```
 
-(for development, run `gem install --dev ./ory-hydra-client-v1.9.0-alpha.3.gem` to install the development dependencies)
+(for development, run `gem install --dev ./ory-hydra-client-v1.10.3.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-hydra-client', '~> v1.9.0-alpha.3'
+    gem 'ory-hydra-client', '~> v1.10.3'
 
 ### Install from Git
 
@@ -99,6 +99,7 @@ Class | Method | HTTP request | Description
 *OryHydraClient::AdminApi* | [**is_instance_alive**](docs/AdminApi.md#is_instance_alive) | **GET** /health/alive | Check Alive Status
 *OryHydraClient::AdminApi* | [**list_o_auth2_clients**](docs/AdminApi.md#list_o_auth2_clients) | **GET** /clients | List OAuth 2.0 Clients
 *OryHydraClient::AdminApi* | [**list_subject_consent_sessions**](docs/AdminApi.md#list_subject_consent_sessions) | **GET** /oauth2/auth/sessions/consent | Lists All Consent Sessions of a Subject
+*OryHydraClient::AdminApi* | [**patch_o_auth2_client**](docs/AdminApi.md#patch_o_auth2_client) | **PATCH** /clients/{id} | Patch an OAuth 2.0 Client
 *OryHydraClient::AdminApi* | [**prometheus**](docs/AdminApi.md#prometheus) | **GET** /metrics/prometheus | Get Snapshot Metrics from the Hydra Service.
 *OryHydraClient::AdminApi* | [**reject_consent_request**](docs/AdminApi.md#reject_consent_request) | **PUT** /oauth2/auth/requests/consent/reject | Reject a Consent Request
 *OryHydraClient::AdminApi* | [**reject_login_request**](docs/AdminApi.md#reject_login_request) | **PUT** /oauth2/auth/requests/login/reject | Reject a Login Request
@@ -139,6 +140,7 @@ Class | Method | HTTP request | Description
  - [OryHydraClient::OAuth2TokenIntrospection](docs/OAuth2TokenIntrospection.md)
  - [OryHydraClient::Oauth2TokenResponse](docs/Oauth2TokenResponse.md)
  - [OryHydraClient::OpenIDConnectContext](docs/OpenIDConnectContext.md)
+ - [OryHydraClient::PatchDocument](docs/PatchDocument.md)
  - [OryHydraClient::PluginConfig](docs/PluginConfig.md)
  - [OryHydraClient::PluginConfigArgs](docs/PluginConfigArgs.md)
  - [OryHydraClient::PluginConfigInterface](docs/PluginConfigInterface.md)
@@ -153,8 +155,10 @@ Class | Method | HTTP request | Description
  - [OryHydraClient::PluginSettings](docs/PluginSettings.md)
  - [OryHydraClient::PreviousConsentSession](docs/PreviousConsentSession.md)
  - [OryHydraClient::RejectRequest](docs/RejectRequest.md)
+ - [OryHydraClient::RequestWasHandledResponse](docs/RequestWasHandledResponse.md)
  - [OryHydraClient::UserinfoResponse](docs/UserinfoResponse.md)
  - [OryHydraClient::Version](docs/Version.md)
+ - [OryHydraClient::Volume](docs/Volume.md)
  - [OryHydraClient::VolumeUsageData](docs/VolumeUsageData.md)
  - [OryHydraClient::WellKnown](docs/WellKnown.md)
 

data/docs/AcceptConsentRequest.md

@@ -2,26 +2,27 @@
 
 ## Properties
 
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**grant_access_token_audience** | **Array<String>** |  | [optional] 
-**grant_scope** | **Array<String>** |  | [optional] 
-**handled_at** | **DateTime** |  | [optional] 
-**remember** | **Boolean** | Remember, if set to true, tells ORY Hydra to remember this consent authorization and reuse it if the same client asks the same user for the same, or a subset of, scope. | [optional] 
-**remember_for** | **Integer** | RememberFor sets how long the consent authorization should be remembered for in seconds. If set to `0`, the authorization will be remembered indefinitely. | [optional] 
-**session** | [**ConsentRequestSession**](ConsentRequestSession.md) |  | [optional] 
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **grant_access_token_audience** | **Array<String>** |  | [optional] |
+| **grant_scope** | **Array<String>** |  | [optional] |
+| **handled_at** | **Time** |  | [optional] |
+| **remember** | **Boolean** | Remember, if set to true, tells ORY Hydra to remember this consent authorization and reuse it if the same client asks the same user for the same, or a subset of, scope. | [optional] |
+| **remember_for** | **Integer** | RememberFor sets how long the consent authorization should be remembered for in seconds. If set to `0`, the authorization will be remembered indefinitely. | [optional] |
+| **session** | [**ConsentRequestSession**](ConsentRequestSession.md) |  | [optional] |
 
-## Code Sample
+## Example
 
 ```ruby
-require 'OryHydraClient'
+require 'ory-hydra-client'
 
-instance = OryHydraClient::AcceptConsentRequest.new(grant_access_token_audience: null,
-                                 grant_scope: null,
-                                 handled_at: null,
-                                 remember: null,
-                                 remember_for: null,
-                                 session: null)
+instance = OryHydraClient::AcceptConsentRequest.new(
+  grant_access_token_audience: null,
+  grant_scope: null,
+  handled_at: null,
+  remember: null,
+  remember_for: null,
+  session: null
+)
 ```
 
-

data/docs/AcceptLoginRequest.md

@@ -2,26 +2,27 @@
 
 ## Properties
 
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**acr** | **String** | ACR sets the Authentication AuthorizationContext Class Reference value for this authentication session. You can use it to express that, for example, a user authenticated using two factor authentication. | [optional] 
-**context** | [**Object**](.md) |  | [optional] 
-**force_subject_identifier** | **String** | ForceSubjectIdentifier forces the \"pairwise\" user ID of the end-user that authenticated. The \"pairwise\" user ID refers to the (Pairwise Identifier Algorithm)[http://openid.net/specs/openid-connect-core-1_0.html#PairwiseAlg] of the OpenID Connect specification. It allows you to set an obfuscated subject (\"user\") identifier that is unique to the client.  Please note that this changes the user ID on endpoint /userinfo and sub claim of the ID Token. It does not change the sub claim in the OAuth 2.0 Introspection.  Per default, ORY Hydra handles this value with its own algorithm. In case you want to set this yourself you can use this field. Please note that setting this field has no effect if `pairwise` is not configured in ORY Hydra or the OAuth 2.0 Client does not expect a pairwise identifier (set via `subject_type` key in the client's configuration).  Please also be aware that ORY Hydra is unable to properly compute this value during authentication. This implies that you have to compute this value on every authentication process (probably depending on the client ID or some other unique value).  If you fail to compute the proper value, then authentication processes which have id_token_hint set might fail. | [optional] 
-**remember** | **Boolean** | Remember, if set to true, tells ORY Hydra to remember this user by telling the user agent (browser) to store a cookie with authentication data. If the same user performs another OAuth 2.0 Authorization Request, he/she will not be asked to log in again. | [optional] 
-**remember_for** | **Integer** | RememberFor sets how long the authentication should be remembered for in seconds. If set to `0`, the authorization will be remembered for the duration of the browser session (using a session cookie). | [optional] 
-**subject** | **String** | Subject is the user ID of the end-user that authenticated. | 
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **acr** | **String** | ACR sets the Authentication AuthorizationContext Class Reference value for this authentication session. You can use it to express that, for example, a user authenticated using two factor authentication. | [optional] |
+| **context** | **Object** |  | [optional] |
+| **force_subject_identifier** | **String** | ForceSubjectIdentifier forces the \"pairwise\" user ID of the end-user that authenticated. The \"pairwise\" user ID refers to the (Pairwise Identifier Algorithm)[http://openid.net/specs/openid-connect-core-1_0.html#PairwiseAlg] of the OpenID Connect specification. It allows you to set an obfuscated subject (\"user\") identifier that is unique to the client.  Please note that this changes the user ID on endpoint /userinfo and sub claim of the ID Token. It does not change the sub claim in the OAuth 2.0 Introspection.  Per default, ORY Hydra handles this value with its own algorithm. In case you want to set this yourself you can use this field. Please note that setting this field has no effect if `pairwise` is not configured in ORY Hydra or the OAuth 2.0 Client does not expect a pairwise identifier (set via `subject_type` key in the client's configuration).  Please also be aware that ORY Hydra is unable to properly compute this value during authentication. This implies that you have to compute this value on every authentication process (probably depending on the client ID or some other unique value).  If you fail to compute the proper value, then authentication processes which have id_token_hint set might fail. | [optional] |
+| **remember** | **Boolean** | Remember, if set to true, tells ORY Hydra to remember this user by telling the user agent (browser) to store a cookie with authentication data. If the same user performs another OAuth 2.0 Authorization Request, he/she will not be asked to log in again. | [optional] |
+| **remember_for** | **Integer** | RememberFor sets how long the authentication should be remembered for in seconds. If set to `0`, the authorization will be remembered for the duration of the browser session (using a session cookie). | [optional] |
+| **subject** | **String** | Subject is the user ID of the end-user that authenticated. |  |
 
-## Code Sample
+## Example
 
 ```ruby
-require 'OryHydraClient'
+require 'ory-hydra-client'
 
-instance = OryHydraClient::AcceptLoginRequest.new(acr: null,
-                                 context: null,
-                                 force_subject_identifier: null,
-                                 remember: null,
-                                 remember_for: null,
-                                 subject: null)
+instance = OryHydraClient::AcceptLoginRequest.new(
+  acr: null,
+  context: null,
+  force_subject_identifier: null,
+  remember: null,
+  remember_for: null,
+  subject: null
+)
 ```
 
-

data/docs/AdminApi.md

@@ -2,53 +2,53 @@
 
 All URIs are relative to *http://localhost*
 
-Method | HTTP request | Description
-------------- | ------------- | -------------
-[**accept_consent_request**](AdminApi.md#accept_consent_request) | **PUT** /oauth2/auth/requests/consent/accept | Accept a Consent Request
-[**accept_login_request**](AdminApi.md#accept_login_request) | **PUT** /oauth2/auth/requests/login/accept | Accept a Login Request
-[**accept_logout_request**](AdminApi.md#accept_logout_request) | **PUT** /oauth2/auth/requests/logout/accept | Accept a Logout Request
-[**create_json_web_key_set**](AdminApi.md#create_json_web_key_set) | **POST** /keys/{set} | Generate a New JSON Web Key
-[**create_o_auth2_client**](AdminApi.md#create_o_auth2_client) | **POST** /clients | Create an OAuth 2.0 Client
-[**delete_json_web_key**](AdminApi.md#delete_json_web_key) | **DELETE** /keys/{set}/{kid} | Delete a JSON Web Key
-[**delete_json_web_key_set**](AdminApi.md#delete_json_web_key_set) | **DELETE** /keys/{set} | Delete a JSON Web Key Set
-[**delete_o_auth2_client**](AdminApi.md#delete_o_auth2_client) | **DELETE** /clients/{id} | Deletes an OAuth 2.0 Client
-[**delete_o_auth2_token**](AdminApi.md#delete_o_auth2_token) | **DELETE** /oauth2/tokens | Delete OAuth2 Access Tokens from a Client
-[**flush_inactive_o_auth2_tokens**](AdminApi.md#flush_inactive_o_auth2_tokens) | **POST** /oauth2/flush | Flush Expired OAuth2 Access Tokens
-[**get_consent_request**](AdminApi.md#get_consent_request) | **GET** /oauth2/auth/requests/consent | Get Consent Request Information
-[**get_json_web_key**](AdminApi.md#get_json_web_key) | **GET** /keys/{set}/{kid} | Fetch a JSON Web Key
-[**get_json_web_key_set**](AdminApi.md#get_json_web_key_set) | **GET** /keys/{set} | Retrieve a JSON Web Key Set
-[**get_login_request**](AdminApi.md#get_login_request) | **GET** /oauth2/auth/requests/login | Get a Login Request
-[**get_logout_request**](AdminApi.md#get_logout_request) | **GET** /oauth2/auth/requests/logout | Get a Logout Request
-[**get_o_auth2_client**](AdminApi.md#get_o_auth2_client) | **GET** /clients/{id} | Get an OAuth 2.0 Client.
-[**get_version**](AdminApi.md#get_version) | **GET** /version | Get Service Version
-[**introspect_o_auth2_token**](AdminApi.md#introspect_o_auth2_token) | **POST** /oauth2/introspect | Introspect OAuth2 Tokens
-[**is_instance_alive**](AdminApi.md#is_instance_alive) | **GET** /health/alive | Check Alive Status
-[**list_o_auth2_clients**](AdminApi.md#list_o_auth2_clients) | **GET** /clients | List OAuth 2.0 Clients
-[**list_subject_consent_sessions**](AdminApi.md#list_subject_consent_sessions) | **GET** /oauth2/auth/sessions/consent | Lists All Consent Sessions of a Subject
-[**prometheus**](AdminApi.md#prometheus) | **GET** /metrics/prometheus | Get Snapshot Metrics from the Hydra Service.
-[**reject_consent_request**](AdminApi.md#reject_consent_request) | **PUT** /oauth2/auth/requests/consent/reject | Reject a Consent Request
-[**reject_login_request**](AdminApi.md#reject_login_request) | **PUT** /oauth2/auth/requests/login/reject | Reject a Login Request
-[**reject_logout_request**](AdminApi.md#reject_logout_request) | **PUT** /oauth2/auth/requests/logout/reject | Reject a Logout Request
-[**revoke_authentication_session**](AdminApi.md#revoke_authentication_session) | **DELETE** /oauth2/auth/sessions/login | Invalidates All Login Sessions of a Certain User Invalidates a Subject's Authentication Session
-[**revoke_consent_sessions**](AdminApi.md#revoke_consent_sessions) | **DELETE** /oauth2/auth/sessions/consent | Revokes Consent Sessions of a Subject for a Specific OAuth 2.0 Client
-[**update_json_web_key**](AdminApi.md#update_json_web_key) | **PUT** /keys/{set}/{kid} | Update a JSON Web Key
-[**update_json_web_key_set**](AdminApi.md#update_json_web_key_set) | **PUT** /keys/{set} | Update a JSON Web Key Set
-[**update_o_auth2_client**](AdminApi.md#update_o_auth2_client) | **PUT** /clients/{id} | Update an OAuth 2.0 Client
-
+| Method | HTTP request | Description |
+| ------ | ------------ | ----------- |
+| [**accept_consent_request**](AdminApi.md#accept_consent_request) | **PUT** /oauth2/auth/requests/consent/accept | Accept a Consent Request |
+| [**accept_login_request**](AdminApi.md#accept_login_request) | **PUT** /oauth2/auth/requests/login/accept | Accept a Login Request |
+| [**accept_logout_request**](AdminApi.md#accept_logout_request) | **PUT** /oauth2/auth/requests/logout/accept | Accept a Logout Request |
+| [**create_json_web_key_set**](AdminApi.md#create_json_web_key_set) | **POST** /keys/{set} | Generate a New JSON Web Key |
+| [**create_o_auth2_client**](AdminApi.md#create_o_auth2_client) | **POST** /clients | Create an OAuth 2.0 Client |
+| [**delete_json_web_key**](AdminApi.md#delete_json_web_key) | **DELETE** /keys/{set}/{kid} | Delete a JSON Web Key |
+| [**delete_json_web_key_set**](AdminApi.md#delete_json_web_key_set) | **DELETE** /keys/{set} | Delete a JSON Web Key Set |
+| [**delete_o_auth2_client**](AdminApi.md#delete_o_auth2_client) | **DELETE** /clients/{id} | Deletes an OAuth 2.0 Client |
+| [**delete_o_auth2_token**](AdminApi.md#delete_o_auth2_token) | **DELETE** /oauth2/tokens | Delete OAuth2 Access Tokens from a Client |
+| [**flush_inactive_o_auth2_tokens**](AdminApi.md#flush_inactive_o_auth2_tokens) | **POST** /oauth2/flush | Flush Expired OAuth2 Access Tokens |
+| [**get_consent_request**](AdminApi.md#get_consent_request) | **GET** /oauth2/auth/requests/consent | Get Consent Request Information |
+| [**get_json_web_key**](AdminApi.md#get_json_web_key) | **GET** /keys/{set}/{kid} | Fetch a JSON Web Key |
+| [**get_json_web_key_set**](AdminApi.md#get_json_web_key_set) | **GET** /keys/{set} | Retrieve a JSON Web Key Set |
+| [**get_login_request**](AdminApi.md#get_login_request) | **GET** /oauth2/auth/requests/login | Get a Login Request |
+| [**get_logout_request**](AdminApi.md#get_logout_request) | **GET** /oauth2/auth/requests/logout | Get a Logout Request |
+| [**get_o_auth2_client**](AdminApi.md#get_o_auth2_client) | **GET** /clients/{id} | Get an OAuth 2.0 Client. |
+| [**get_version**](AdminApi.md#get_version) | **GET** /version | Get Service Version |
+| [**introspect_o_auth2_token**](AdminApi.md#introspect_o_auth2_token) | **POST** /oauth2/introspect | Introspect OAuth2 Tokens |
+| [**is_instance_alive**](AdminApi.md#is_instance_alive) | **GET** /health/alive | Check Alive Status |
+| [**list_o_auth2_clients**](AdminApi.md#list_o_auth2_clients) | **GET** /clients | List OAuth 2.0 Clients |
+| [**list_subject_consent_sessions**](AdminApi.md#list_subject_consent_sessions) | **GET** /oauth2/auth/sessions/consent | Lists All Consent Sessions of a Subject |
+| [**patch_o_auth2_client**](AdminApi.md#patch_o_auth2_client) | **PATCH** /clients/{id} | Patch an OAuth 2.0 Client |
+| [**prometheus**](AdminApi.md#prometheus) | **GET** /metrics/prometheus | Get Snapshot Metrics from the Hydra Service. |
+| [**reject_consent_request**](AdminApi.md#reject_consent_request) | **PUT** /oauth2/auth/requests/consent/reject | Reject a Consent Request |
+| [**reject_login_request**](AdminApi.md#reject_login_request) | **PUT** /oauth2/auth/requests/login/reject | Reject a Login Request |
+| [**reject_logout_request**](AdminApi.md#reject_logout_request) | **PUT** /oauth2/auth/requests/logout/reject | Reject a Logout Request |
+| [**revoke_authentication_session**](AdminApi.md#revoke_authentication_session) | **DELETE** /oauth2/auth/sessions/login | Invalidates All Login Sessions of a Certain User Invalidates a Subject's Authentication Session |
+| [**revoke_consent_sessions**](AdminApi.md#revoke_consent_sessions) | **DELETE** /oauth2/auth/sessions/consent | Revokes Consent Sessions of a Subject for a Specific OAuth 2.0 Client |
+| [**update_json_web_key**](AdminApi.md#update_json_web_key) | **PUT** /keys/{set}/{kid} | Update a JSON Web Key |
+| [**update_json_web_key_set**](AdminApi.md#update_json_web_key_set) | **PUT** /keys/{set} | Update a JSON Web Key Set |
+| [**update_o_auth2_client**](AdminApi.md#update_o_auth2_client) | **PUT** /clients/{id} | Update an OAuth 2.0 Client |
 
 
 ## accept_consent_request
 
-> CompletedRequest accept_consent_request(consent_challenge, opts)
+> <CompletedRequest> accept_consent_request(consent_challenge, opts)
 
 Accept a Consent Request
 
 When an authorization code, hybrid, or implicit OAuth 2.0 Flow is initiated, ORY Hydra asks the login provider to authenticate the subject and then tell ORY Hydra now about it. If the subject authenticated, he/she must now be asked if the OAuth 2.0 Client which initiated the flow should be allowed to access the resources on the subject's behalf.  The consent provider which handles this request and is a web app implemented and hosted by you. It shows a subject interface which asks the subject to grant or deny the client access to the requested scope (\"Application my-dropbox-app wants write access to all your private files\").  The consent challenge is appended to the consent provider's URL to which the subject's user-agent (browser) is redirected to. The consent provider uses that challenge to fetch information on the OAuth2 request and then tells ORY Hydra if the subject accepted or rejected the request.  This endpoint tells ORY Hydra that the subject has authorized the OAuth 2.0 client to access resources on his/her behalf. The consent provider includes additional information, such as session data for access and ID tokens, and if the consent request should be used as basis for future requests.  The response contains a redirect URL which the consent provider should redirect the user-agent to.
 
-### Example
+### Examples
 
 ```ruby
-# load the gem
+require 'time'
 require 'ory-hydra-client'
 
 api_instance = OryHydraClient::AdminApi.new
@@ -58,21 +58,38 @@ opts = {
 }
 
 begin
-  #Accept a Consent Request
+  # Accept a Consent Request
   result = api_instance.accept_consent_request(consent_challenge, opts)
   p result
 rescue OryHydraClient::ApiError => e
-  puts "Exception when calling AdminApi->accept_consent_request: #{e}"
+  puts "Error when calling AdminApi->accept_consent_request: #{e}"
 end
 ```
 
-### Parameters
+#### Using the accept_consent_request_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
 
+> <Array(<CompletedRequest>, Integer, Hash)> accept_consent_request_with_http_info(consent_challenge, opts)
+
+```ruby
+begin
+  # Accept a Consent Request
+  data, status_code, headers = api_instance.accept_consent_request_with_http_info(consent_challenge, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <CompletedRequest>
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->accept_consent_request_with_http_info: #{e}"
+end
+```
+
+### Parameters
 
-Name | Type | Description  | Notes
-------------- | ------------- | ------------- | -------------
- **consent_challenge** | **String**|  | 
- **body** | [**AcceptConsentRequest**](AcceptConsentRequest.md)|  | [optional] 
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **consent_challenge** | **String** |  |  |
+| **body** | [**AcceptConsentRequest**](AcceptConsentRequest.md) |  | [optional] |
 
 ### Return type
 
@@ -90,40 +107,57 @@ No authorization required
 
 ## accept_login_request
 
-> CompletedRequest accept_login_request(login_challenge, opts)
+> <CompletedRequest> accept_login_request(login_challenge, opts)
 
 Accept a Login Request
 
 When an authorization code, hybrid, or implicit OAuth 2.0 Flow is initiated, ORY Hydra asks the login provider (sometimes called \"identity provider\") to authenticate the subject and then tell ORY Hydra now about it. The login provider is an web-app you write and host, and it must be able to authenticate (\"show the subject a login screen\") a subject (in OAuth2 the proper name for subject is \"resource owner\").  The authentication challenge is appended to the login provider URL to which the subject's user-agent (browser) is redirected to. The login provider uses that challenge to fetch information on the OAuth2 request and then accept or reject the requested authentication process.  This endpoint tells ORY Hydra that the subject has successfully authenticated and includes additional information such as the subject's ID and if ORY Hydra should remember the subject's subject agent for future authentication attempts by setting a cookie.  The response contains a redirect URL which the login provider should redirect the user-agent to.
 
-### Example
+### Examples
 
 ```ruby
-# load the gem
+require 'time'
 require 'ory-hydra-client'
 
 api_instance = OryHydraClient::AdminApi.new
 login_challenge = 'login_challenge_example' # String | 
 opts = {
-  body: OryHydraClient::AcceptLoginRequest.new # AcceptLoginRequest | 
+  body: OryHydraClient::AcceptLoginRequest.new({subject: 'subject_example'}) # AcceptLoginRequest | 
 }
 
 begin
-  #Accept a Login Request
+  # Accept a Login Request
   result = api_instance.accept_login_request(login_challenge, opts)
   p result
 rescue OryHydraClient::ApiError => e
-  puts "Exception when calling AdminApi->accept_login_request: #{e}"
+  puts "Error when calling AdminApi->accept_login_request: #{e}"
 end
 ```
 
-### Parameters
+#### Using the accept_login_request_with_http_info variant
 
+This returns an Array which contains the response data, status code and headers.
 
-Name | Type | Description  | Notes
-------------- | ------------- | ------------- | -------------
- **login_challenge** | **String**|  | 
- **body** | [**AcceptLoginRequest**](AcceptLoginRequest.md)|  | [optional] 
+> <Array(<CompletedRequest>, Integer, Hash)> accept_login_request_with_http_info(login_challenge, opts)
+
+```ruby
+begin
+  # Accept a Login Request
+  data, status_code, headers = api_instance.accept_login_request_with_http_info(login_challenge, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <CompletedRequest>
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->accept_login_request_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **login_challenge** | **String** |  |  |
+| **body** | [**AcceptLoginRequest**](AcceptLoginRequest.md) |  | [optional] |
 
 ### Return type
 
@@ -141,36 +175,53 @@ No authorization required
 
 ## accept_logout_request
 
-> CompletedRequest accept_logout_request(logout_challenge)
+> <CompletedRequest> accept_logout_request(logout_challenge)
 
 Accept a Logout Request
 
 When a user or an application requests ORY Hydra to log out a user, this endpoint is used to confirm that logout request. No body is required.  The response contains a redirect URL which the consent provider should redirect the user-agent to.
 
-### Example
+### Examples
 
 ```ruby
-# load the gem
+require 'time'
 require 'ory-hydra-client'
 
 api_instance = OryHydraClient::AdminApi.new
 logout_challenge = 'logout_challenge_example' # String | 
 
 begin
-  #Accept a Logout Request
+  # Accept a Logout Request
   result = api_instance.accept_logout_request(logout_challenge)
   p result
 rescue OryHydraClient::ApiError => e
-  puts "Exception when calling AdminApi->accept_logout_request: #{e}"
+  puts "Error when calling AdminApi->accept_logout_request: #{e}"
 end
 ```
 
-### Parameters
+#### Using the accept_logout_request_with_http_info variant
 
+This returns an Array which contains the response data, status code and headers.
 
-Name | Type | Description  | Notes
-------------- | ------------- | ------------- | -------------
- **logout_challenge** | **String**|  | 
+> <Array(<CompletedRequest>, Integer, Hash)> accept_logout_request_with_http_info(logout_challenge)
+
+```ruby
+begin
+  # Accept a Logout Request
+  data, status_code, headers = api_instance.accept_logout_request_with_http_info(logout_challenge)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <CompletedRequest>
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->accept_logout_request_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **logout_challenge** | **String** |  |  |
 
 ### Return type
 
@@ -188,40 +239,57 @@ No authorization required
 
 ## create_json_web_key_set
 
-> JSONWebKeySet create_json_web_key_set(set, opts)
+> <JSONWebKeySet> create_json_web_key_set(set, opts)
 
 Generate a New JSON Web Key
 
 This endpoint is capable of generating JSON Web Key Sets for you. There a different strategies available, such as symmetric cryptographic keys (HS256, HS512) and asymetric cryptographic keys (RS256, ECDSA). If the specified JSON Web Key Set does not exist, it will be created.  A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) data structure that represents a cryptographic key. A JWK Set is a JSON data structure that represents a set of JWKs. A JSON Web Key is identified by its set and key id. ORY Hydra uses this functionality to store cryptographic keys used for TLS and JSON Web Tokens (such as OpenID Connect ID tokens), and allows storing user-defined keys as well.
 
-### Example
+### Examples
 
 ```ruby
-# load the gem
+require 'time'
 require 'ory-hydra-client'
 
 api_instance = OryHydraClient::AdminApi.new
 set = 'set_example' # String | The set
 opts = {
-  body: OryHydraClient::JsonWebKeySetGeneratorRequest.new # JsonWebKeySetGeneratorRequest | 
+  body: OryHydraClient::JsonWebKeySetGeneratorRequest.new({alg: 'alg_example', kid: 'kid_example', use: 'use_example'}) # JsonWebKeySetGeneratorRequest | 
 }
 
 begin
-  #Generate a New JSON Web Key
+  # Generate a New JSON Web Key
   result = api_instance.create_json_web_key_set(set, opts)
   p result
 rescue OryHydraClient::ApiError => e
-  puts "Exception when calling AdminApi->create_json_web_key_set: #{e}"
+  puts "Error when calling AdminApi->create_json_web_key_set: #{e}"
 end
 ```
 
-### Parameters
+#### Using the create_json_web_key_set_with_http_info variant
 
+This returns an Array which contains the response data, status code and headers.
 
-Name | Type | Description  | Notes
-------------- | ------------- | ------------- | -------------
- **set** | **String**| The set | 
- **body** | [**JsonWebKeySetGeneratorRequest**](JsonWebKeySetGeneratorRequest.md)|  | [optional] 
+> <Array(<JSONWebKeySet>, Integer, Hash)> create_json_web_key_set_with_http_info(set, opts)
+
+```ruby
+begin
+  # Generate a New JSON Web Key
+  data, status_code, headers = api_instance.create_json_web_key_set_with_http_info(set, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <JSONWebKeySet>
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->create_json_web_key_set_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **set** | **String** | The set |  |
+| **body** | [**JsonWebKeySetGeneratorRequest**](JsonWebKeySetGeneratorRequest.md) |  | [optional] |
 
 ### Return type
 
@@ -239,36 +307,53 @@ No authorization required
 
 ## create_o_auth2_client
 
-> OAuth2Client create_o_auth2_client(body)
+> <OAuth2Client> create_o_auth2_client(body)
 
 Create an OAuth 2.0 Client
 
 Create a new OAuth 2.0 client If you pass `client_secret` the secret will be used, otherwise a random secret will be generated. The secret will be returned in the response and you will not be able to retrieve it later on. Write the secret down and keep it somwhere safe.  OAuth 2.0 clients are used to perform OAuth 2.0 and OpenID Connect flows. Usually, OAuth 2.0 clients are generated for applications which want to consume your OAuth 2.0 or OpenID Connect capabilities. To manage ORY Hydra, you will need an OAuth 2.0 Client as well. Make sure that this endpoint is well protected and only callable by first-party components.
 
-### Example
+### Examples
 
 ```ruby
-# load the gem
+require 'time'
 require 'ory-hydra-client'
 
 api_instance = OryHydraClient::AdminApi.new
 body = OryHydraClient::OAuth2Client.new # OAuth2Client | 
 
 begin
-  #Create an OAuth 2.0 Client
+  # Create an OAuth 2.0 Client
   result = api_instance.create_o_auth2_client(body)
   p result
 rescue OryHydraClient::ApiError => e
-  puts "Exception when calling AdminApi->create_o_auth2_client: #{e}"
+  puts "Error when calling AdminApi->create_o_auth2_client: #{e}"
 end
 ```
 
-### Parameters
+#### Using the create_o_auth2_client_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
 
+> <Array(<OAuth2Client>, Integer, Hash)> create_o_auth2_client_with_http_info(body)
 
-Name | Type | Description  | Notes
-------------- | ------------- | ------------- | -------------
- **body** | [**OAuth2Client**](OAuth2Client.md)|  | 
+```ruby
+begin
+  # Create an OAuth 2.0 Client
+  data, status_code, headers = api_instance.create_o_auth2_client_with_http_info(body)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <OAuth2Client>
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->create_o_auth2_client_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **body** | [**OAuth2Client**](OAuth2Client.md) |  |  |
 
 ### Return type
 
@@ -292,10 +377,10 @@ Delete a JSON Web Key
 
 Use this endpoint to delete a single JSON Web Key.  A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) data structure that represents a cryptographic key. A JWK Set is a JSON data structure that represents a set of JWKs. A JSON Web Key is identified by its set and key id. ORY Hydra uses this functionality to store cryptographic keys used for TLS and JSON Web Tokens (such as OpenID Connect ID tokens), and allows storing user-defined keys as well.
 
-### Example
+### Examples
 
 ```ruby
-# load the gem
+require 'time'
 require 'ory-hydra-client'
 
 api_instance = OryHydraClient::AdminApi.new
@@ -303,20 +388,37 @@ kid = 'kid_example' # String | The kid of the desired key
 set = 'set_example' # String | The set
 
 begin
-  #Delete a JSON Web Key
+  # Delete a JSON Web Key
   api_instance.delete_json_web_key(kid, set)
 rescue OryHydraClient::ApiError => e
-  puts "Exception when calling AdminApi->delete_json_web_key: #{e}"
+  puts "Error when calling AdminApi->delete_json_web_key: #{e}"
 end
 ```
 
-### Parameters
+#### Using the delete_json_web_key_with_http_info variant
+
+This returns an Array which contains the response data (`nil` in this case), status code and headers.
+
+> <Array(nil, Integer, Hash)> delete_json_web_key_with_http_info(kid, set)
 
+```ruby
+begin
+  # Delete a JSON Web Key
+  data, status_code, headers = api_instance.delete_json_web_key_with_http_info(kid, set)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => nil
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->delete_json_web_key_with_http_info: #{e}"
+end
+```
 
-Name | Type | Description  | Notes
-------------- | ------------- | ------------- | -------------
- **kid** | **String**| The kid of the desired key | 
- **set** | **String**| The set | 
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **kid** | **String** | The kid of the desired key |  |
+| **set** | **String** | The set |  |
 
 ### Return type
 
@@ -340,29 +442,46 @@ Delete a JSON Web Key Set
 
 Use this endpoint to delete a complete JSON Web Key Set and all the keys in that set.  A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) data structure that represents a cryptographic key. A JWK Set is a JSON data structure that represents a set of JWKs. A JSON Web Key is identified by its set and key id. ORY Hydra uses this functionality to store cryptographic keys used for TLS and JSON Web Tokens (such as OpenID Connect ID tokens), and allows storing user-defined keys as well.
 
-### Example
+### Examples
 
 ```ruby
-# load the gem
+require 'time'
 require 'ory-hydra-client'
 
 api_instance = OryHydraClient::AdminApi.new
 set = 'set_example' # String | The set
 
 begin
-  #Delete a JSON Web Key Set
+  # Delete a JSON Web Key Set
   api_instance.delete_json_web_key_set(set)
 rescue OryHydraClient::ApiError => e
-  puts "Exception when calling AdminApi->delete_json_web_key_set: #{e}"
+  puts "Error when calling AdminApi->delete_json_web_key_set: #{e}"
 end
 ```
 
-### Parameters
+#### Using the delete_json_web_key_set_with_http_info variant
 
+This returns an Array which contains the response data (`nil` in this case), status code and headers.
 
-Name | Type | Description  | Notes
-------------- | ------------- | ------------- | -------------
- **set** | **String**| The set | 
+> <Array(nil, Integer, Hash)> delete_json_web_key_set_with_http_info(set)
+
+```ruby
+begin
+  # Delete a JSON Web Key Set
+  data, status_code, headers = api_instance.delete_json_web_key_set_with_http_info(set)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => nil
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->delete_json_web_key_set_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **set** | **String** | The set |  |
 
 ### Return type
 
@@ -386,29 +505,46 @@ Deletes an OAuth 2.0 Client
 
 Delete an existing OAuth 2.0 Client by its ID.  OAuth 2.0 clients are used to perform OAuth 2.0 and OpenID Connect flows. Usually, OAuth 2.0 clients are generated for applications which want to consume your OAuth 2.0 or OpenID Connect capabilities. To manage ORY Hydra, you will need an OAuth 2.0 Client as well. Make sure that this endpoint is well protected and only callable by first-party components.
 
-### Example
+### Examples
 
 ```ruby
-# load the gem
+require 'time'
 require 'ory-hydra-client'
 
 api_instance = OryHydraClient::AdminApi.new
 id = 'id_example' # String | The id of the OAuth 2.0 Client.
 
 begin
-  #Deletes an OAuth 2.0 Client
+  # Deletes an OAuth 2.0 Client
   api_instance.delete_o_auth2_client(id)
 rescue OryHydraClient::ApiError => e
-  puts "Exception when calling AdminApi->delete_o_auth2_client: #{e}"
+  puts "Error when calling AdminApi->delete_o_auth2_client: #{e}"
 end
 ```
 
-### Parameters
+#### Using the delete_o_auth2_client_with_http_info variant
 
+This returns an Array which contains the response data (`nil` in this case), status code and headers.
 
-Name | Type | Description  | Notes
-------------- | ------------- | ------------- | -------------
- **id** | **String**| The id of the OAuth 2.0 Client. | 
+> <Array(nil, Integer, Hash)> delete_o_auth2_client_with_http_info(id)
+
+```ruby
+begin
+  # Deletes an OAuth 2.0 Client
+  data, status_code, headers = api_instance.delete_o_auth2_client_with_http_info(id)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => nil
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->delete_o_auth2_client_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **id** | **String** | The id of the OAuth 2.0 Client. |  |
 
 ### Return type
 
@@ -432,29 +568,46 @@ Delete OAuth2 Access Tokens from a Client
 
 This endpoint deletes OAuth2 access tokens issued for a client from the database
 
-### Example
+### Examples
 
 ```ruby
-# load the gem
+require 'time'
 require 'ory-hydra-client'
 
 api_instance = OryHydraClient::AdminApi.new
 client_id = 'client_id_example' # String | 
 
 begin
-  #Delete OAuth2 Access Tokens from a Client
+  # Delete OAuth2 Access Tokens from a Client
   api_instance.delete_o_auth2_token(client_id)
 rescue OryHydraClient::ApiError => e
-  puts "Exception when calling AdminApi->delete_o_auth2_token: #{e}"
+  puts "Error when calling AdminApi->delete_o_auth2_token: #{e}"
 end
 ```
 
-### Parameters
+#### Using the delete_o_auth2_token_with_http_info variant
 
+This returns an Array which contains the response data (`nil` in this case), status code and headers.
 
-Name | Type | Description  | Notes
-------------- | ------------- | ------------- | -------------
- **client_id** | **String**|  | 
+> <Array(nil, Integer, Hash)> delete_o_auth2_token_with_http_info(client_id)
+
+```ruby
+begin
+  # Delete OAuth2 Access Tokens from a Client
+  data, status_code, headers = api_instance.delete_o_auth2_token_with_http_info(client_id)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => nil
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->delete_o_auth2_token_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **client_id** | **String** |  |  |
 
 ### Return type
 
@@ -478,10 +631,10 @@ Flush Expired OAuth2 Access Tokens
 
 This endpoint flushes expired OAuth2 access tokens from the database. You can set a time after which no tokens will be not be touched, in case you want to keep recent tokens for auditing. Refresh tokens can not be flushed as they are deleted automatically when performing the refresh flow.
 
-### Example
+### Examples
 
 ```ruby
-# load the gem
+require 'time'
 require 'ory-hydra-client'
 
 api_instance = OryHydraClient::AdminApi.new
@@ -490,19 +643,36 @@ opts = {
 }
 
 begin
-  #Flush Expired OAuth2 Access Tokens
+  # Flush Expired OAuth2 Access Tokens
   api_instance.flush_inactive_o_auth2_tokens(opts)
 rescue OryHydraClient::ApiError => e
-  puts "Exception when calling AdminApi->flush_inactive_o_auth2_tokens: #{e}"
+  puts "Error when calling AdminApi->flush_inactive_o_auth2_tokens: #{e}"
 end
 ```
 
-### Parameters
+#### Using the flush_inactive_o_auth2_tokens_with_http_info variant
+
+This returns an Array which contains the response data (`nil` in this case), status code and headers.
+
+> <Array(nil, Integer, Hash)> flush_inactive_o_auth2_tokens_with_http_info(opts)
+
+```ruby
+begin
+  # Flush Expired OAuth2 Access Tokens
+  data, status_code, headers = api_instance.flush_inactive_o_auth2_tokens_with_http_info(opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => nil
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->flush_inactive_o_auth2_tokens_with_http_info: #{e}"
+end
+```
 
+### Parameters
 
-Name | Type | Description  | Notes
-------------- | ------------- | ------------- | -------------
- **body** | [**FlushInactiveOAuth2TokensRequest**](FlushInactiveOAuth2TokensRequest.md)|  | [optional] 
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **body** | [**FlushInactiveOAuth2TokensRequest**](FlushInactiveOAuth2TokensRequest.md) |  | [optional] |
 
 ### Return type
 
@@ -520,36 +690,53 @@ No authorization required
 
 ## get_consent_request
 
-> ConsentRequest get_consent_request(consent_challenge)
+> <ConsentRequest> get_consent_request(consent_challenge)
 
 Get Consent Request Information
 
 When an authorization code, hybrid, or implicit OAuth 2.0 Flow is initiated, ORY Hydra asks the login provider to authenticate the subject and then tell ORY Hydra now about it. If the subject authenticated, he/she must now be asked if the OAuth 2.0 Client which initiated the flow should be allowed to access the resources on the subject's behalf.  The consent provider which handles this request and is a web app implemented and hosted by you. It shows a subject interface which asks the subject to grant or deny the client access to the requested scope (\"Application my-dropbox-app wants write access to all your private files\").  The consent challenge is appended to the consent provider's URL to which the subject's user-agent (browser) is redirected to. The consent provider uses that challenge to fetch information on the OAuth2 request and then tells ORY Hydra if the subject accepted or rejected the request.
 
-### Example
+### Examples
 
 ```ruby
-# load the gem
+require 'time'
 require 'ory-hydra-client'
 
 api_instance = OryHydraClient::AdminApi.new
 consent_challenge = 'consent_challenge_example' # String | 
 
 begin
-  #Get Consent Request Information
+  # Get Consent Request Information
   result = api_instance.get_consent_request(consent_challenge)
   p result
 rescue OryHydraClient::ApiError => e
-  puts "Exception when calling AdminApi->get_consent_request: #{e}"
+  puts "Error when calling AdminApi->get_consent_request: #{e}"
 end
 ```
 
-### Parameters
+#### Using the get_consent_request_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
 
+> <Array(<ConsentRequest>, Integer, Hash)> get_consent_request_with_http_info(consent_challenge)
 
-Name | Type | Description  | Notes
-------------- | ------------- | ------------- | -------------
- **consent_challenge** | **String**|  | 
+```ruby
+begin
+  # Get Consent Request Information
+  data, status_code, headers = api_instance.get_consent_request_with_http_info(consent_challenge)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <ConsentRequest>
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->get_consent_request_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **consent_challenge** | **String** |  |  |
 
 ### Return type
 
@@ -567,16 +754,16 @@ No authorization required
 
 ## get_json_web_key
 
-> JSONWebKeySet get_json_web_key(kid, set)
+> <JSONWebKeySet> get_json_web_key(kid, set)
 
 Fetch a JSON Web Key
 
 This endpoint returns a singular JSON Web Key, identified by the set and the specific key ID (kid).
 
-### Example
+### Examples
 
 ```ruby
-# load the gem
+require 'time'
 require 'ory-hydra-client'
 
 api_instance = OryHydraClient::AdminApi.new
@@ -584,21 +771,38 @@ kid = 'kid_example' # String | The kid of the desired key
 set = 'set_example' # String | The set
 
 begin
-  #Fetch a JSON Web Key
+  # Fetch a JSON Web Key
   result = api_instance.get_json_web_key(kid, set)
   p result
 rescue OryHydraClient::ApiError => e
-  puts "Exception when calling AdminApi->get_json_web_key: #{e}"
+  puts "Error when calling AdminApi->get_json_web_key: #{e}"
 end
 ```
 
-### Parameters
+#### Using the get_json_web_key_with_http_info variant
 
+This returns an Array which contains the response data, status code and headers.
 
-Name | Type | Description  | Notes
-------------- | ------------- | ------------- | -------------
- **kid** | **String**| The kid of the desired key | 
- **set** | **String**| The set | 
+> <Array(<JSONWebKeySet>, Integer, Hash)> get_json_web_key_with_http_info(kid, set)
+
+```ruby
+begin
+  # Fetch a JSON Web Key
+  data, status_code, headers = api_instance.get_json_web_key_with_http_info(kid, set)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <JSONWebKeySet>
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->get_json_web_key_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **kid** | **String** | The kid of the desired key |  |
+| **set** | **String** | The set |  |
 
 ### Return type
 
@@ -616,36 +820,53 @@ No authorization required
 
 ## get_json_web_key_set
 
-> JSONWebKeySet get_json_web_key_set(set)
+> <JSONWebKeySet> get_json_web_key_set(set)
 
 Retrieve a JSON Web Key Set
 
 This endpoint can be used to retrieve JWK Sets stored in ORY Hydra.  A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) data structure that represents a cryptographic key. A JWK Set is a JSON data structure that represents a set of JWKs. A JSON Web Key is identified by its set and key id. ORY Hydra uses this functionality to store cryptographic keys used for TLS and JSON Web Tokens (such as OpenID Connect ID tokens), and allows storing user-defined keys as well.
 
-### Example
+### Examples
 
 ```ruby
-# load the gem
+require 'time'
 require 'ory-hydra-client'
 
 api_instance = OryHydraClient::AdminApi.new
 set = 'set_example' # String | The set
 
 begin
-  #Retrieve a JSON Web Key Set
+  # Retrieve a JSON Web Key Set
   result = api_instance.get_json_web_key_set(set)
   p result
 rescue OryHydraClient::ApiError => e
-  puts "Exception when calling AdminApi->get_json_web_key_set: #{e}"
+  puts "Error when calling AdminApi->get_json_web_key_set: #{e}"
 end
 ```
 
-### Parameters
+#### Using the get_json_web_key_set_with_http_info variant
 
+This returns an Array which contains the response data, status code and headers.
 
-Name | Type | Description  | Notes
-------------- | ------------- | ------------- | -------------
- **set** | **String**| The set | 
+> <Array(<JSONWebKeySet>, Integer, Hash)> get_json_web_key_set_with_http_info(set)
+
+```ruby
+begin
+  # Retrieve a JSON Web Key Set
+  data, status_code, headers = api_instance.get_json_web_key_set_with_http_info(set)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <JSONWebKeySet>
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->get_json_web_key_set_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **set** | **String** | The set |  |
 
 ### Return type
 
@@ -663,36 +884,53 @@ No authorization required
 
 ## get_login_request
 
-> LoginRequest get_login_request(login_challenge)
+> <LoginRequest> get_login_request(login_challenge)
 
 Get a Login Request
 
 When an authorization code, hybrid, or implicit OAuth 2.0 Flow is initiated, ORY Hydra asks the login provider (sometimes called \"identity provider\") to authenticate the subject and then tell ORY Hydra now about it. The login provider is an web-app you write and host, and it must be able to authenticate (\"show the subject a login screen\") a subject (in OAuth2 the proper name for subject is \"resource owner\").  The authentication challenge is appended to the login provider URL to which the subject's user-agent (browser) is redirected to. The login provider uses that challenge to fetch information on the OAuth2 request and then accept or reject the requested authentication process.
 
-### Example
+### Examples
 
 ```ruby
-# load the gem
+require 'time'
 require 'ory-hydra-client'
 
 api_instance = OryHydraClient::AdminApi.new
 login_challenge = 'login_challenge_example' # String | 
 
 begin
-  #Get a Login Request
+  # Get a Login Request
   result = api_instance.get_login_request(login_challenge)
   p result
 rescue OryHydraClient::ApiError => e
-  puts "Exception when calling AdminApi->get_login_request: #{e}"
+  puts "Error when calling AdminApi->get_login_request: #{e}"
 end
 ```
 
-### Parameters
+#### Using the get_login_request_with_http_info variant
 
+This returns an Array which contains the response data, status code and headers.
 
-Name | Type | Description  | Notes
-------------- | ------------- | ------------- | -------------
- **login_challenge** | **String**|  | 
+> <Array(<LoginRequest>, Integer, Hash)> get_login_request_with_http_info(login_challenge)
+
+```ruby
+begin
+  # Get a Login Request
+  data, status_code, headers = api_instance.get_login_request_with_http_info(login_challenge)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <LoginRequest>
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->get_login_request_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **login_challenge** | **String** |  |  |
 
 ### Return type
 
@@ -710,36 +948,53 @@ No authorization required
 
 ## get_logout_request
 
-> LogoutRequest get_logout_request(logout_challenge)
+> <LogoutRequest> get_logout_request(logout_challenge)
 
 Get a Logout Request
 
 Use this endpoint to fetch a logout request.
 
-### Example
+### Examples
 
 ```ruby
-# load the gem
+require 'time'
 require 'ory-hydra-client'
 
 api_instance = OryHydraClient::AdminApi.new
 logout_challenge = 'logout_challenge_example' # String | 
 
 begin
-  #Get a Logout Request
+  # Get a Logout Request
   result = api_instance.get_logout_request(logout_challenge)
   p result
 rescue OryHydraClient::ApiError => e
-  puts "Exception when calling AdminApi->get_logout_request: #{e}"
+  puts "Error when calling AdminApi->get_logout_request: #{e}"
 end
 ```
 
-### Parameters
+#### Using the get_logout_request_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<LogoutRequest>, Integer, Hash)> get_logout_request_with_http_info(logout_challenge)
+
+```ruby
+begin
+  # Get a Logout Request
+  data, status_code, headers = api_instance.get_logout_request_with_http_info(logout_challenge)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <LogoutRequest>
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->get_logout_request_with_http_info: #{e}"
+end
+```
 
+### Parameters
 
-Name | Type | Description  | Notes
-------------- | ------------- | ------------- | -------------
- **logout_challenge** | **String**|  | 
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **logout_challenge** | **String** |  |  |
 
 ### Return type
 
@@ -757,36 +1012,53 @@ No authorization required
 
 ## get_o_auth2_client
 
-> OAuth2Client get_o_auth2_client(id)
+> <OAuth2Client> get_o_auth2_client(id)
 
 Get an OAuth 2.0 Client.
 
 Get an OAUth 2.0 client by its ID. This endpoint never returns passwords.  OAuth 2.0 clients are used to perform OAuth 2.0 and OpenID Connect flows. Usually, OAuth 2.0 clients are generated for applications which want to consume your OAuth 2.0 or OpenID Connect capabilities. To manage ORY Hydra, you will need an OAuth 2.0 Client as well. Make sure that this endpoint is well protected and only callable by first-party components.
 
-### Example
+### Examples
 
 ```ruby
-# load the gem
+require 'time'
 require 'ory-hydra-client'
 
 api_instance = OryHydraClient::AdminApi.new
 id = 'id_example' # String | The id of the OAuth 2.0 Client.
 
 begin
-  #Get an OAuth 2.0 Client.
+  # Get an OAuth 2.0 Client.
   result = api_instance.get_o_auth2_client(id)
   p result
 rescue OryHydraClient::ApiError => e
-  puts "Exception when calling AdminApi->get_o_auth2_client: #{e}"
+  puts "Error when calling AdminApi->get_o_auth2_client: #{e}"
 end
 ```
 
-### Parameters
+#### Using the get_o_auth2_client_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
 
+> <Array(<OAuth2Client>, Integer, Hash)> get_o_auth2_client_with_http_info(id)
+
+```ruby
+begin
+  # Get an OAuth 2.0 Client.
+  data, status_code, headers = api_instance.get_o_auth2_client_with_http_info(id)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <OAuth2Client>
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->get_o_auth2_client_with_http_info: #{e}"
+end
+```
+
+### Parameters
 
-Name | Type | Description  | Notes
-------------- | ------------- | ------------- | -------------
- **id** | **String**| The id of the OAuth 2.0 Client. | 
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **id** | **String** | The id of the OAuth 2.0 Client. |  |
 
 ### Return type
 
@@ -804,26 +1076,44 @@ No authorization required
 
 ## get_version
 
-> Version get_version
+> <Version> get_version
 
 Get Service Version
 
 This endpoint returns the service version typically notated using semantic versioning.  If the service supports TLS Edge Termination, this endpoint does not require the `X-Forwarded-Proto` header to be set.
 
-### Example
+### Examples
 
 ```ruby
-# load the gem
+require 'time'
 require 'ory-hydra-client'
 
 api_instance = OryHydraClient::AdminApi.new
 
 begin
-  #Get Service Version
+  # Get Service Version
   result = api_instance.get_version
   p result
 rescue OryHydraClient::ApiError => e
-  puts "Exception when calling AdminApi->get_version: #{e}"
+  puts "Error when calling AdminApi->get_version: #{e}"
+end
+```
+
+#### Using the get_version_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<Version>, Integer, Hash)> get_version_with_http_info
+
+```ruby
+begin
+  # Get Service Version
+  data, status_code, headers = api_instance.get_version_with_http_info
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <Version>
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->get_version_with_http_info: #{e}"
 end
 ```
 
@@ -847,16 +1137,16 @@ No authorization required
 
 ## introspect_o_auth2_token
 
-> OAuth2TokenIntrospection introspect_o_auth2_token(token, opts)
+> <OAuth2TokenIntrospection> introspect_o_auth2_token(token, opts)
 
 Introspect OAuth2 Tokens
 
 The introspection endpoint allows to check if a token (both refresh and access) is active or not. An active token is neither expired nor revoked. If a token is active, additional information on the token will be included. You can set additional data for a token by setting `accessTokenExtra` during the consent flow.  For more information [read this blog post](https://www.oauth.com/oauth2-servers/token-introspection-endpoint/).
 
-### Example
+### Examples
 
 ```ruby
-# load the gem
+require 'time'
 require 'ory-hydra-client'
 
 api_instance = OryHydraClient::AdminApi.new
@@ -866,21 +1156,38 @@ opts = {
 }
 
 begin
-  #Introspect OAuth2 Tokens
+  # Introspect OAuth2 Tokens
   result = api_instance.introspect_o_auth2_token(token, opts)
   p result
 rescue OryHydraClient::ApiError => e
-  puts "Exception when calling AdminApi->introspect_o_auth2_token: #{e}"
+  puts "Error when calling AdminApi->introspect_o_auth2_token: #{e}"
 end
 ```
 
-### Parameters
+#### Using the introspect_o_auth2_token_with_http_info variant
 
+This returns an Array which contains the response data, status code and headers.
 
-Name | Type | Description  | Notes
-------------- | ------------- | ------------- | -------------
- **token** | **String**| The string value of the token. For access tokens, this is the \\\&quot;access_token\\\&quot; value returned from the token endpoint defined in OAuth 2.0. For refresh tokens, this is the \\\&quot;refresh_token\\\&quot; value returned. | 
- **scope** | **String**| An optional, space separated list of required scopes. If the access token was not granted one of the scopes, the result of active will be false. | [optional] 
+> <Array(<OAuth2TokenIntrospection>, Integer, Hash)> introspect_o_auth2_token_with_http_info(token, opts)
+
+```ruby
+begin
+  # Introspect OAuth2 Tokens
+  data, status_code, headers = api_instance.introspect_o_auth2_token_with_http_info(token, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <OAuth2TokenIntrospection>
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->introspect_o_auth2_token_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **token** | **String** | The string value of the token. For access tokens, this is the \\\&quot;access_token\\\&quot; value returned from the token endpoint defined in OAuth 2.0. For refresh tokens, this is the \\\&quot;refresh_token\\\&quot; value returned. |  |
+| **scope** | **String** | An optional, space separated list of required scopes. If the access token was not granted one of the scopes, the result of active will be false. | [optional] |
 
 ### Return type
 
@@ -898,26 +1205,44 @@ No authorization required
 
 ## is_instance_alive
 
-> HealthStatus is_instance_alive
+> <HealthStatus> is_instance_alive
 
 Check Alive Status
 
 This endpoint returns a 200 status code when the HTTP server is up running. This status does currently not include checks whether the database connection is working.  If the service supports TLS Edge Termination, this endpoint does not require the `X-Forwarded-Proto` header to be set.  Be aware that if you are running multiple nodes of this service, the health status will never refer to the cluster state, only to a single instance.
 
-### Example
+### Examples
 
 ```ruby
-# load the gem
+require 'time'
 require 'ory-hydra-client'
 
 api_instance = OryHydraClient::AdminApi.new
 
 begin
-  #Check Alive Status
+  # Check Alive Status
   result = api_instance.is_instance_alive
   p result
 rescue OryHydraClient::ApiError => e
-  puts "Exception when calling AdminApi->is_instance_alive: #{e}"
+  puts "Error when calling AdminApi->is_instance_alive: #{e}"
+end
+```
+
+#### Using the is_instance_alive_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<HealthStatus>, Integer, Hash)> is_instance_alive_with_http_info
+
+```ruby
+begin
+  # Check Alive Status
+  data, status_code, headers = api_instance.is_instance_alive_with_http_info
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <HealthStatus>
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->is_instance_alive_with_http_info: #{e}"
 end
 ```
 
@@ -941,40 +1266,57 @@ No authorization required
 
 ## list_o_auth2_clients
 
-> Array&lt;OAuth2Client&gt; list_o_auth2_clients(opts)
+> <Array<OAuth2Client>> list_o_auth2_clients(opts)
 
 List OAuth 2.0 Clients
 
-This endpoint lists all clients in the database, and never returns client secrets.  OAuth 2.0 clients are used to perform OAuth 2.0 and OpenID Connect flows. Usually, OAuth 2.0 clients are generated for applications which want to consume your OAuth 2.0 or OpenID Connect capabilities. To manage ORY Hydra, you will need an OAuth 2.0 Client as well. Make sure that this endpoint is well protected and only callable by first-party components. The \"Link\" header is also included in successful responses, which contains one or more links for pagination, formatted like so: '<https://hydra-url/admin/clients?limit={limit}&offset={offset}>; rel=\"{page}\"', where page is one of the following applicable pages: 'first', 'next', 'last', and 'previous'. Multiple links can be included in this header, and will be separated by a comma.
+This endpoint lists all clients in the database, and never returns client secrets. As a default it lists the first 100 clients. The `limit` parameter can be used to retrieve more clients, but it has an upper bound at 500 objects. Pagination should be used to retrieve more than 500 objects.  OAuth 2.0 clients are used to perform OAuth 2.0 and OpenID Connect flows. Usually, OAuth 2.0 clients are generated for applications which want to consume your OAuth 2.0 or OpenID Connect capabilities. To manage ORY Hydra, you will need an OAuth 2.0 Client as well. Make sure that this endpoint is well protected and only callable by first-party components. The \"Link\" header is also included in successful responses, which contains one or more links for pagination, formatted like so: '<https://hydra-url/admin/clients?limit={limit}&offset={offset}>; rel=\"{page}\"', where page is one of the following applicable pages: 'first', 'next', 'last', and 'previous'. Multiple links can be included in this header, and will be separated by a comma.
 
-### Example
+### Examples
 
 ```ruby
-# load the gem
+require 'time'
 require 'ory-hydra-client'
 
 api_instance = OryHydraClient::AdminApi.new
 opts = {
-  limit: 56, # Integer | The maximum amount of policies returned.
-  offset: 56 # Integer | The offset from where to start looking.
+  limit: 789, # Integer | The maximum amount of policies returned, upper bound is 500 policies
+  offset: 789 # Integer | The offset from where to start looking.
 }
 
 begin
-  #List OAuth 2.0 Clients
+  # List OAuth 2.0 Clients
   result = api_instance.list_o_auth2_clients(opts)
   p result
 rescue OryHydraClient::ApiError => e
-  puts "Exception when calling AdminApi->list_o_auth2_clients: #{e}"
+  puts "Error when calling AdminApi->list_o_auth2_clients: #{e}"
 end
 ```
 
-### Parameters
+#### Using the list_o_auth2_clients_with_http_info variant
 
+This returns an Array which contains the response data, status code and headers.
 
-Name | Type | Description  | Notes
-------------- | ------------- | ------------- | -------------
- **limit** | **Integer**| The maximum amount of policies returned. | [optional] 
- **offset** | **Integer**| The offset from where to start looking. | [optional] 
+> <Array(<Array<OAuth2Client>>, Integer, Hash)> list_o_auth2_clients_with_http_info(opts)
+
+```ruby
+begin
+  # List OAuth 2.0 Clients
+  data, status_code, headers = api_instance.list_o_auth2_clients_with_http_info(opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <Array<OAuth2Client>>
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->list_o_auth2_clients_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **limit** | **Integer** | The maximum amount of policies returned, upper bound is 500 policies | [optional] |
+| **offset** | **Integer** | The offset from where to start looking. | [optional] |
 
 ### Return type
 
@@ -992,36 +1334,53 @@ No authorization required
 
 ## list_subject_consent_sessions
 
-> Array&lt;PreviousConsentSession&gt; list_subject_consent_sessions(subject)
+> <Array<PreviousConsentSession>> list_subject_consent_sessions(subject)
 
 Lists All Consent Sessions of a Subject
 
 This endpoint lists all subject's granted consent sessions, including client and granted scope. If the subject is unknown or has not granted any consent sessions yet, the endpoint returns an empty JSON array with status code 200 OK.   The \"Link\" header is also included in successful responses, which contains one or more links for pagination, formatted like so: '<https://hydra-url/admin/oauth2/auth/sessions/consent?subject={user}&limit={limit}&offset={offset}>; rel=\"{page}\"', where page is one of the following applicable pages: 'first', 'next', 'last', and 'previous'. Multiple links can be included in this header, and will be separated by a comma.
 
-### Example
+### Examples
 
 ```ruby
-# load the gem
+require 'time'
 require 'ory-hydra-client'
 
 api_instance = OryHydraClient::AdminApi.new
 subject = 'subject_example' # String | 
 
 begin
-  #Lists All Consent Sessions of a Subject
+  # Lists All Consent Sessions of a Subject
   result = api_instance.list_subject_consent_sessions(subject)
   p result
 rescue OryHydraClient::ApiError => e
-  puts "Exception when calling AdminApi->list_subject_consent_sessions: #{e}"
+  puts "Error when calling AdminApi->list_subject_consent_sessions: #{e}"
 end
 ```
 
-### Parameters
+#### Using the list_subject_consent_sessions_with_http_info variant
 
+This returns an Array which contains the response data, status code and headers.
 
-Name | Type | Description  | Notes
-------------- | ------------- | ------------- | -------------
- **subject** | **String**|  | 
+> <Array(<Array<PreviousConsentSession>>, Integer, Hash)> list_subject_consent_sessions_with_http_info(subject)
+
+```ruby
+begin
+  # Lists All Consent Sessions of a Subject
+  data, status_code, headers = api_instance.list_subject_consent_sessions_with_http_info(subject)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <Array<PreviousConsentSession>>
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->list_subject_consent_sessions_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **subject** | **String** |  |  |
 
 ### Return type
 
@@ -1037,6 +1396,72 @@ No authorization required
 - **Accept**: application/json
 
 
+## patch_o_auth2_client
+
+> <OAuth2Client> patch_o_auth2_client(id, body)
+
+Patch an OAuth 2.0 Client
+
+Patch an existing OAuth 2.0 Client. If you pass `client_secret` the secret will be updated and returned via the API. This is the only time you will be able to retrieve the client secret, so write it down and keep it safe.  OAuth 2.0 clients are used to perform OAuth 2.0 and OpenID Connect flows. Usually, OAuth 2.0 clients are generated for applications which want to consume your OAuth 2.0 or OpenID Connect capabilities. To manage ORY Hydra, you will need an OAuth 2.0 Client as well. Make sure that this endpoint is well protected and only callable by first-party components.
+
+### Examples
+
+```ruby
+require 'time'
+require 'ory-hydra-client'
+
+api_instance = OryHydraClient::AdminApi.new
+id = 'id_example' # String | 
+body = [OryHydraClient::PatchDocument.new({op: '"replace"', path: '"/name"'})] # Array<PatchDocument> | 
+
+begin
+  # Patch an OAuth 2.0 Client
+  result = api_instance.patch_o_auth2_client(id, body)
+  p result
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->patch_o_auth2_client: #{e}"
+end
+```
+
+#### Using the patch_o_auth2_client_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<OAuth2Client>, Integer, Hash)> patch_o_auth2_client_with_http_info(id, body)
+
+```ruby
+begin
+  # Patch an OAuth 2.0 Client
+  data, status_code, headers = api_instance.patch_o_auth2_client_with_http_info(id, body)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <OAuth2Client>
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->patch_o_auth2_client_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **id** | **String** |  |  |
+| **body** | [**Array&lt;PatchDocument&gt;**](PatchDocument.md) |  |  |
+
+### Return type
+
+[**OAuth2Client**](OAuth2Client.md)
+
+### Authorization
+
+No authorization required
+
+### HTTP request headers
+
+- **Content-Type**: application/json
+- **Accept**: application/json
+
+
 ## prometheus
 
 > prometheus
@@ -1045,19 +1470,37 @@ Get Snapshot Metrics from the Hydra Service.
 
 If you're using k8s, you can then add annotations to your deployment like so:  ``` metadata: annotations: prometheus.io/port: \"4445\" prometheus.io/path: \"/metrics/prometheus\" ```  If the service supports TLS Edge Termination, this endpoint does not require the `X-Forwarded-Proto` header to be set.
 
-### Example
+### Examples
 
 ```ruby
-# load the gem
+require 'time'
 require 'ory-hydra-client'
 
 api_instance = OryHydraClient::AdminApi.new
 
 begin
-  #Get Snapshot Metrics from the Hydra Service.
+  # Get Snapshot Metrics from the Hydra Service.
   api_instance.prometheus
 rescue OryHydraClient::ApiError => e
-  puts "Exception when calling AdminApi->prometheus: #{e}"
+  puts "Error when calling AdminApi->prometheus: #{e}"
+end
+```
+
+#### Using the prometheus_with_http_info variant
+
+This returns an Array which contains the response data (`nil` in this case), status code and headers.
+
+> <Array(nil, Integer, Hash)> prometheus_with_http_info
+
+```ruby
+begin
+  # Get Snapshot Metrics from the Hydra Service.
+  data, status_code, headers = api_instance.prometheus_with_http_info
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => nil
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->prometheus_with_http_info: #{e}"
 end
 ```
 
@@ -1081,16 +1524,16 @@ No authorization required
 
 ## reject_consent_request
 
-> CompletedRequest reject_consent_request(consent_challenge, opts)
+> <CompletedRequest> reject_consent_request(consent_challenge, opts)
 
 Reject a Consent Request
 
 When an authorization code, hybrid, or implicit OAuth 2.0 Flow is initiated, ORY Hydra asks the login provider to authenticate the subject and then tell ORY Hydra now about it. If the subject authenticated, he/she must now be asked if the OAuth 2.0 Client which initiated the flow should be allowed to access the resources on the subject's behalf.  The consent provider which handles this request and is a web app implemented and hosted by you. It shows a subject interface which asks the subject to grant or deny the client access to the requested scope (\"Application my-dropbox-app wants write access to all your private files\").  The consent challenge is appended to the consent provider's URL to which the subject's user-agent (browser) is redirected to. The consent provider uses that challenge to fetch information on the OAuth2 request and then tells ORY Hydra if the subject accepted or rejected the request.  This endpoint tells ORY Hydra that the subject has not authorized the OAuth 2.0 client to access resources on his/her behalf. The consent provider must include a reason why the consent was not granted.  The response contains a redirect URL which the consent provider should redirect the user-agent to.
 
-### Example
+### Examples
 
 ```ruby
-# load the gem
+require 'time'
 require 'ory-hydra-client'
 
 api_instance = OryHydraClient::AdminApi.new
@@ -1100,21 +1543,38 @@ opts = {
 }
 
 begin
-  #Reject a Consent Request
+  # Reject a Consent Request
   result = api_instance.reject_consent_request(consent_challenge, opts)
   p result
 rescue OryHydraClient::ApiError => e
-  puts "Exception when calling AdminApi->reject_consent_request: #{e}"
+  puts "Error when calling AdminApi->reject_consent_request: #{e}"
 end
 ```
 
-### Parameters
+#### Using the reject_consent_request_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<CompletedRequest>, Integer, Hash)> reject_consent_request_with_http_info(consent_challenge, opts)
+
+```ruby
+begin
+  # Reject a Consent Request
+  data, status_code, headers = api_instance.reject_consent_request_with_http_info(consent_challenge, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <CompletedRequest>
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->reject_consent_request_with_http_info: #{e}"
+end
+```
 
+### Parameters
 
-Name | Type | Description  | Notes
-------------- | ------------- | ------------- | -------------
- **consent_challenge** | **String**|  | 
- **body** | [**RejectRequest**](RejectRequest.md)|  | [optional] 
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **consent_challenge** | **String** |  |  |
+| **body** | [**RejectRequest**](RejectRequest.md) |  | [optional] |
 
 ### Return type
 
@@ -1132,16 +1592,16 @@ No authorization required
 
 ## reject_login_request
 
-> CompletedRequest reject_login_request(login_challenge, opts)
+> <CompletedRequest> reject_login_request(login_challenge, opts)
 
 Reject a Login Request
 
 When an authorization code, hybrid, or implicit OAuth 2.0 Flow is initiated, ORY Hydra asks the login provider (sometimes called \"identity provider\") to authenticate the subject and then tell ORY Hydra now about it. The login provider is an web-app you write and host, and it must be able to authenticate (\"show the subject a login screen\") a subject (in OAuth2 the proper name for subject is \"resource owner\").  The authentication challenge is appended to the login provider URL to which the subject's user-agent (browser) is redirected to. The login provider uses that challenge to fetch information on the OAuth2 request and then accept or reject the requested authentication process.  This endpoint tells ORY Hydra that the subject has not authenticated and includes a reason why the authentication was be denied.  The response contains a redirect URL which the login provider should redirect the user-agent to.
 
-### Example
+### Examples
 
 ```ruby
-# load the gem
+require 'time'
 require 'ory-hydra-client'
 
 api_instance = OryHydraClient::AdminApi.new
@@ -1151,21 +1611,38 @@ opts = {
 }
 
 begin
-  #Reject a Login Request
+  # Reject a Login Request
   result = api_instance.reject_login_request(login_challenge, opts)
   p result
 rescue OryHydraClient::ApiError => e
-  puts "Exception when calling AdminApi->reject_login_request: #{e}"
+  puts "Error when calling AdminApi->reject_login_request: #{e}"
 end
 ```
 
-### Parameters
+#### Using the reject_login_request_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
 
+> <Array(<CompletedRequest>, Integer, Hash)> reject_login_request_with_http_info(login_challenge, opts)
 
-Name | Type | Description  | Notes
-------------- | ------------- | ------------- | -------------
- **login_challenge** | **String**|  | 
- **body** | [**RejectRequest**](RejectRequest.md)|  | [optional] 
+```ruby
+begin
+  # Reject a Login Request
+  data, status_code, headers = api_instance.reject_login_request_with_http_info(login_challenge, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <CompletedRequest>
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->reject_login_request_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **login_challenge** | **String** |  |  |
+| **body** | [**RejectRequest**](RejectRequest.md) |  | [optional] |
 
 ### Return type
 
@@ -1189,10 +1666,10 @@ Reject a Logout Request
 
 When a user or an application requests ORY Hydra to log out a user, this endpoint is used to deny that logout request. No body is required.  The response is empty as the logout provider has to chose what action to perform next.
 
-### Example
+### Examples
 
 ```ruby
-# load the gem
+require 'time'
 require 'ory-hydra-client'
 
 api_instance = OryHydraClient::AdminApi.new
@@ -1202,20 +1679,37 @@ opts = {
 }
 
 begin
-  #Reject a Logout Request
+  # Reject a Logout Request
   api_instance.reject_logout_request(logout_challenge, opts)
 rescue OryHydraClient::ApiError => e
-  puts "Exception when calling AdminApi->reject_logout_request: #{e}"
+  puts "Error when calling AdminApi->reject_logout_request: #{e}"
 end
 ```
 
-### Parameters
+#### Using the reject_logout_request_with_http_info variant
 
+This returns an Array which contains the response data (`nil` in this case), status code and headers.
 
-Name | Type | Description  | Notes
-------------- | ------------- | ------------- | -------------
- **logout_challenge** | **String**|  | 
- **body** | [**RejectRequest**](RejectRequest.md)|  | [optional] 
+> <Array(nil, Integer, Hash)> reject_logout_request_with_http_info(logout_challenge, opts)
+
+```ruby
+begin
+  # Reject a Logout Request
+  data, status_code, headers = api_instance.reject_logout_request_with_http_info(logout_challenge, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => nil
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->reject_logout_request_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **logout_challenge** | **String** |  |  |
+| **body** | [**RejectRequest**](RejectRequest.md) |  | [optional] |
 
 ### Return type
 
@@ -1239,29 +1733,46 @@ Invalidates All Login Sessions of a Certain User Invalidates a Subject's Authent
 
 This endpoint invalidates a subject's authentication session. After revoking the authentication session, the subject has to re-authenticate at ORY Hydra. This endpoint does not invalidate any tokens and does not work with OpenID Connect Front- or Back-channel logout.
 
-### Example
+### Examples
 
 ```ruby
-# load the gem
+require 'time'
 require 'ory-hydra-client'
 
 api_instance = OryHydraClient::AdminApi.new
 subject = 'subject_example' # String | 
 
 begin
-  #Invalidates All Login Sessions of a Certain User Invalidates a Subject's Authentication Session
+  # Invalidates All Login Sessions of a Certain User Invalidates a Subject's Authentication Session
   api_instance.revoke_authentication_session(subject)
 rescue OryHydraClient::ApiError => e
-  puts "Exception when calling AdminApi->revoke_authentication_session: #{e}"
+  puts "Error when calling AdminApi->revoke_authentication_session: #{e}"
 end
 ```
 
-### Parameters
+#### Using the revoke_authentication_session_with_http_info variant
 
+This returns an Array which contains the response data (`nil` in this case), status code and headers.
 
-Name | Type | Description  | Notes
-------------- | ------------- | ------------- | -------------
- **subject** | **String**|  | 
+> <Array(nil, Integer, Hash)> revoke_authentication_session_with_http_info(subject)
+
+```ruby
+begin
+  # Invalidates All Login Sessions of a Certain User Invalidates a Subject's Authentication Session
+  data, status_code, headers = api_instance.revoke_authentication_session_with_http_info(subject)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => nil
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->revoke_authentication_session_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **subject** | **String** |  |  |
 
 ### Return type
 
@@ -1285,10 +1796,10 @@ Revokes Consent Sessions of a Subject for a Specific OAuth 2.0 Client
 
 This endpoint revokes a subject's granted consent sessions for a specific OAuth 2.0 Client and invalidates all associated OAuth 2.0 Access Tokens.
 
-### Example
+### Examples
 
 ```ruby
-# load the gem
+require 'time'
 require 'ory-hydra-client'
 
 api_instance = OryHydraClient::AdminApi.new
@@ -1299,21 +1810,38 @@ opts = {
 }
 
 begin
-  #Revokes Consent Sessions of a Subject for a Specific OAuth 2.0 Client
+  # Revokes Consent Sessions of a Subject for a Specific OAuth 2.0 Client
   api_instance.revoke_consent_sessions(subject, opts)
 rescue OryHydraClient::ApiError => e
-  puts "Exception when calling AdminApi->revoke_consent_sessions: #{e}"
+  puts "Error when calling AdminApi->revoke_consent_sessions: #{e}"
 end
 ```
 
-### Parameters
+#### Using the revoke_consent_sessions_with_http_info variant
 
+This returns an Array which contains the response data (`nil` in this case), status code and headers.
 
-Name | Type | Description  | Notes
-------------- | ------------- | ------------- | -------------
- **subject** | **String**| The subject (Subject) who&#39;s consent sessions should be deleted. | 
- **client** | **String**| If set, deletes only those consent sessions by the Subject that have been granted to the specified OAuth 2.0 Client ID | [optional] 
- **all** | **Boolean**| If set to &#x60;?all&#x3D;true&#x60;, deletes all consent sessions by the Subject that have been granted. | [optional] 
+> <Array(nil, Integer, Hash)> revoke_consent_sessions_with_http_info(subject, opts)
+
+```ruby
+begin
+  # Revokes Consent Sessions of a Subject for a Specific OAuth 2.0 Client
+  data, status_code, headers = api_instance.revoke_consent_sessions_with_http_info(subject, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => nil
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->revoke_consent_sessions_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **subject** | **String** | The subject (Subject) who&#39;s consent sessions should be deleted. |  |
+| **client** | **String** | If set, deletes only those consent sessions by the Subject that have been granted to the specified OAuth 2.0 Client ID | [optional] |
+| **all** | **Boolean** | If set to &#x60;?all&#x3D;true&#x60;, deletes all consent sessions by the Subject that have been granted. | [optional] |
 
 ### Return type
 
@@ -1331,42 +1859,59 @@ No authorization required
 
 ## update_json_web_key
 
-> JSONWebKey update_json_web_key(kid, set, opts)
+> <JSONWebKey> update_json_web_key(kid, set, opts)
 
 Update a JSON Web Key
 
 Use this method if you do not want to let Hydra generate the JWKs for you, but instead save your own.  A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) data structure that represents a cryptographic key. A JWK Set is a JSON data structure that represents a set of JWKs. A JSON Web Key is identified by its set and key id. ORY Hydra uses this functionality to store cryptographic keys used for TLS and JSON Web Tokens (such as OpenID Connect ID tokens), and allows storing user-defined keys as well.
 
-### Example
+### Examples
 
 ```ruby
-# load the gem
+require 'time'
 require 'ory-hydra-client'
 
 api_instance = OryHydraClient::AdminApi.new
 kid = 'kid_example' # String | The kid of the desired key
 set = 'set_example' # String | The set
 opts = {
-  body: OryHydraClient::JSONWebKey.new # JSONWebKey | 
+  body: OryHydraClient::JSONWebKey.new({alg: 'RS256', kid: '1603dfe0af8f4596', kty: 'RSA', use: 'sig'}) # JSONWebKey | 
 }
 
 begin
-  #Update a JSON Web Key
+  # Update a JSON Web Key
   result = api_instance.update_json_web_key(kid, set, opts)
   p result
 rescue OryHydraClient::ApiError => e
-  puts "Exception when calling AdminApi->update_json_web_key: #{e}"
+  puts "Error when calling AdminApi->update_json_web_key: #{e}"
 end
 ```
 
-### Parameters
+#### Using the update_json_web_key_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<JSONWebKey>, Integer, Hash)> update_json_web_key_with_http_info(kid, set, opts)
+
+```ruby
+begin
+  # Update a JSON Web Key
+  data, status_code, headers = api_instance.update_json_web_key_with_http_info(kid, set, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <JSONWebKey>
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->update_json_web_key_with_http_info: #{e}"
+end
+```
 
+### Parameters
 
-Name | Type | Description  | Notes
-------------- | ------------- | ------------- | -------------
- **kid** | **String**| The kid of the desired key | 
- **set** | **String**| The set | 
- **body** | [**JSONWebKey**](JSONWebKey.md)|  | [optional] 
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **kid** | **String** | The kid of the desired key |  |
+| **set** | **String** | The set |  |
+| **body** | [**JSONWebKey**](JSONWebKey.md) |  | [optional] |
 
 ### Return type
 
@@ -1384,16 +1929,16 @@ No authorization required
 
 ## update_json_web_key_set
 
-> JSONWebKeySet update_json_web_key_set(set, opts)
+> <JSONWebKeySet> update_json_web_key_set(set, opts)
 
 Update a JSON Web Key Set
 
 Use this method if you do not want to let Hydra generate the JWKs for you, but instead save your own.  A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) data structure that represents a cryptographic key. A JWK Set is a JSON data structure that represents a set of JWKs. A JSON Web Key is identified by its set and key id. ORY Hydra uses this functionality to store cryptographic keys used for TLS and JSON Web Tokens (such as OpenID Connect ID tokens), and allows storing user-defined keys as well.
 
-### Example
+### Examples
 
 ```ruby
-# load the gem
+require 'time'
 require 'ory-hydra-client'
 
 api_instance = OryHydraClient::AdminApi.new
@@ -1403,21 +1948,38 @@ opts = {
 }
 
 begin
-  #Update a JSON Web Key Set
+  # Update a JSON Web Key Set
   result = api_instance.update_json_web_key_set(set, opts)
   p result
 rescue OryHydraClient::ApiError => e
-  puts "Exception when calling AdminApi->update_json_web_key_set: #{e}"
+  puts "Error when calling AdminApi->update_json_web_key_set: #{e}"
 end
 ```
 
-### Parameters
+#### Using the update_json_web_key_set_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
 
+> <Array(<JSONWebKeySet>, Integer, Hash)> update_json_web_key_set_with_http_info(set, opts)
+
+```ruby
+begin
+  # Update a JSON Web Key Set
+  data, status_code, headers = api_instance.update_json_web_key_set_with_http_info(set, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <JSONWebKeySet>
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->update_json_web_key_set_with_http_info: #{e}"
+end
+```
+
+### Parameters
 
-Name | Type | Description  | Notes
-------------- | ------------- | ------------- | -------------
- **set** | **String**| The set | 
- **body** | [**JSONWebKeySet**](JSONWebKeySet.md)|  | [optional] 
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **set** | **String** | The set |  |
+| **body** | [**JSONWebKeySet**](JSONWebKeySet.md) |  | [optional] |
 
 ### Return type
 
@@ -1435,16 +1997,16 @@ No authorization required
 
 ## update_o_auth2_client
 
-> OAuth2Client update_o_auth2_client(id, body)
+> <OAuth2Client> update_o_auth2_client(id, body)
 
 Update an OAuth 2.0 Client
 
 Update an existing OAuth 2.0 Client. If you pass `client_secret` the secret will be updated and returned via the API. This is the only time you will be able to retrieve the client secret, so write it down and keep it safe.  OAuth 2.0 clients are used to perform OAuth 2.0 and OpenID Connect flows. Usually, OAuth 2.0 clients are generated for applications which want to consume your OAuth 2.0 or OpenID Connect capabilities. To manage ORY Hydra, you will need an OAuth 2.0 Client as well. Make sure that this endpoint is well protected and only callable by first-party components.
 
-### Example
+### Examples
 
 ```ruby
-# load the gem
+require 'time'
 require 'ory-hydra-client'
 
 api_instance = OryHydraClient::AdminApi.new
@@ -1452,21 +2014,38 @@ id = 'id_example' # String |
 body = OryHydraClient::OAuth2Client.new # OAuth2Client | 
 
 begin
-  #Update an OAuth 2.0 Client
+  # Update an OAuth 2.0 Client
   result = api_instance.update_o_auth2_client(id, body)
   p result
 rescue OryHydraClient::ApiError => e
-  puts "Exception when calling AdminApi->update_o_auth2_client: #{e}"
+  puts "Error when calling AdminApi->update_o_auth2_client: #{e}"
 end
 ```
 
-### Parameters
+#### Using the update_o_auth2_client_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<OAuth2Client>, Integer, Hash)> update_o_auth2_client_with_http_info(id, body)
+
+```ruby
+begin
+  # Update an OAuth 2.0 Client
+  data, status_code, headers = api_instance.update_o_auth2_client_with_http_info(id, body)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <OAuth2Client>
+rescue OryHydraClient::ApiError => e
+  puts "Error when calling AdminApi->update_o_auth2_client_with_http_info: #{e}"
+end
+```
 
+### Parameters
 
-Name | Type | Description  | Notes
-------------- | ------------- | ------------- | -------------
- **id** | **String**|  | 
- **body** | [**OAuth2Client**](OAuth2Client.md)|  | 
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **id** | **String** |  |  |
+| **body** | [**OAuth2Client**](OAuth2Client.md) |  |  |
 
 ### Return type