There is no explicit, built-in field in Ory Hydra that directly marks a client as "dynamically registered" during the consent flow, according to the available documentation and API references. The consent request object (as returned by getOAuth2ConsentRequest) does not include a property that indicates whether the client was registered via the dynamic registration endpoint or through the admin API. Recommended Approach: A common and recommended workaround is to use the OAuth2 Client's metadata field to tag dynamically registered clients. When registering a client dynamically (using the OpenID Dynamic Client Registration endpoint), you can include a custom property in the metadata, such as

"metadata": {"dynamically_registered": true}

. During the consent flow, you can then check for this property in the client object attached to the consent request. This approach is also mentioned as a "quick and dirty fix" in community discussions, with the suggestion that a proper field might be added in the future. The consent UI or backend can then check this metadata field to identify dynamically registered clients and apply any special logic as needed [Skip consent flow in default Ory Network UI](https://github.com/ory/network/issues/205). Example: When registering a client:

json {   "redirect_uris": ["<https://example.com/callback>"],   "grant_types": ["authorization_code"],   "metadata": {     "dynamically_registered": true   } }

Then, in your consent logic:

js if (consentRequest.client.metadata?.dynamically_registered) {   // Handle dynamically registered client }

Summary: There is no built-in flag, but using the metadata field is the recommended and supported way to tag and later identify dynamically registered clients during the consent flow [Skip consent flow in default Ory Network UI](https://github.com/ory/network/issues/205).

New message text here