diff --git a/output/openapi/elasticsearch-openapi.json b/output/openapi/elasticsearch-openapi.json
index 2cd0a5667f..90803748df 100644
--- a/output/openapi/elasticsearch-openapi.json
+++ b/output/openapi/elasticsearch-openapi.json
@@ -27658,7 +27658,7 @@
           "security"
         ],
         "summary": "Invalidate API keys",
-        "description": "Invalidates one or more API keys.\nThe `manage_api_key` privilege allows deleting any API keys.\nThe `manage_own_api_key` only allows deleting API keys that are owned by the user.\nIn addition, with the `manage_own_api_key` privilege, an invalidation request must be issued in one of the three formats:\n- Set the parameter `owner=true`.\n- Or, set both `username` and `realm_name` to match the user’s identity.\n- Or, if the request is issued by an API key, i.e. an API key invalidates itself, specify its ID in the `ids` field.",
+        "description": "This API invalidates API keys created by the create API key or grant API key APIs.\nInvalidated API keys fail authentication, but they can still be viewed using the get API key information and query API key information APIs, for at least the configured retention period, until they are automatically deleted.\nThe `manage_api_key` privilege allows deleting any API keys.\nThe `manage_own_api_key` only allows deleting API keys that are owned by the user.\nIn addition, with the `manage_own_api_key` privilege, an invalidation request must be issued in one of the three formats:\n- Set the parameter `owner=true`.\n- Or, set both `username` and `realm_name` to match the user’s identity.\n- Or, if the request is issued by an API key, that is to say an API key invalidates itself, specify its ID in the `ids` field.",
         "operationId": "security-invalidate-api-key",
         "requestBody": {
           "content": {
@@ -28019,8 +28019,11 @@
         "tags": [
           "security"
         ],
-        "summary": "The role management APIs are generally the preferred way to manage roles, rather than using file-based role management",
-        "description": "The create or update roles API cannot update roles that are defined in roles files.",
+        "summary": "Create or update roles",
+        "description": "The role management APIs are generally the preferred way to manage roles in the native realm, rather than using file-based role management.\nThe create or update roles API cannot update roles that are defined in roles files.\nFile-based role management is not available in Elastic Serverless.",
+        "externalDocs": {
+          "url": "https://www.elastic.co/guide/en/elasticsearch/reference/current/defining-roles.html"
+        },
         "operationId": "security-put-role",
         "parameters": [
           {
@@ -28043,8 +28046,11 @@
         "tags": [
           "security"
         ],
-        "summary": "The role management APIs are generally the preferred way to manage roles, rather than using file-based role management",
-        "description": "The create or update roles API cannot update roles that are defined in roles files.",
+        "summary": "Create or update roles",
+        "description": "The role management APIs are generally the preferred way to manage roles in the native realm, rather than using file-based role management.\nThe create or update roles API cannot update roles that are defined in roles files.\nFile-based role management is not available in Elastic Serverless.",
+        "externalDocs": {
+          "url": "https://www.elastic.co/guide/en/elasticsearch/reference/current/defining-roles.html"
+        },
         "operationId": "security-put-role-1",
         "parameters": [
           {
@@ -28142,7 +28148,11 @@
         "tags": [
           "security"
         ],
-        "summary": "Creates and updates role mappings",
+        "summary": "Create or update role mappings",
+        "description": "Role mappings define which roles are assigned to each user.\nEach mapping has rules that identify users and a list of roles that are granted to those users.\nThe role mapping APIs are generally the preferred way to manage role mappings rather than using role mapping files. The create or update role mappings API cannot update role mappings that are defined in role mapping files.\n\nThis API does not create roles. Rather, it maps users to existing roles.\nRoles can be created by using the create or update roles API or roles files.",
+        "externalDocs": {
+          "url": "https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-roles.html"
+        },
         "operationId": "security-put-role-mapping",
         "parameters": [
           {
@@ -28166,7 +28176,11 @@
         "tags": [
           "security"
         ],
-        "summary": "Creates and updates role mappings",
+        "summary": "Create or update role mappings",
+        "description": "Role mappings define which roles are assigned to each user.\nEach mapping has rules that identify users and a list of roles that are granted to those users.\nThe role mapping APIs are generally the preferred way to manage role mappings rather than using role mapping files. The create or update role mappings API cannot update role mappings that are defined in role mapping files.\n\nThis API does not create roles. Rather, it maps users to existing roles.\nRoles can be created by using the create or update roles API or roles files.",
+        "externalDocs": {
+          "url": "https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-roles.html"
+        },
         "operationId": "security-put-role-mapping-1",
         "parameters": [
           {
@@ -28264,8 +28278,8 @@
         "tags": [
           "security"
         ],
-        "summary": "Adds and updates users in the native realm",
-        "description": "These users are commonly referred to as native users.",
+        "summary": "Create or update users",
+        "description": "A password is required for adding a new user but is optional when updating an existing user.\nTo change a user’s password without updating any other fields, use the change password API.",
         "operationId": "security-put-user",
         "parameters": [
           {
@@ -28288,8 +28302,8 @@
         "tags": [
           "security"
         ],
-        "summary": "Adds and updates users in the native realm",
-        "description": "These users are commonly referred to as native users.",
+        "summary": "Create or update users",
+        "description": "A password is required for adding a new user but is optional when updating an existing user.\nTo change a user’s password without updating any other fields, use the change password API.",
         "operationId": "security-put-user-1",
         "parameters": [
           {
@@ -28691,7 +28705,10 @@
         "tags": [
           "security"
         ],
-        "summary": "Adds or updates application privileges",
+        "summary": "Create or update application privileges",
+        "externalDocs": {
+          "url": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-privileges.html"
+        },
         "operationId": "security-put-privileges",
         "parameters": [
           {
@@ -28712,7 +28729,10 @@
         "tags": [
           "security"
         ],
-        "summary": "Adds or updates application privileges",
+        "summary": "Create or update application privileges",
+        "externalDocs": {
+          "url": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-privileges.html"
+        },
         "operationId": "security-put-privileges-1",
         "parameters": [
           {
@@ -28999,7 +29019,8 @@
         "tags": [
           "security"
         ],
-        "summary": "Invalidates one or more access tokens or refresh tokens",
+        "summary": "Invalidate a token",
+        "description": "The access tokens returned by the get token API have a finite period of time for which they are valid.\nAfter that time period, they can no longer be used.\nThe time period is defined by the `xpack.security.authc.token.timeout` setting.\n\nThe refresh tokens returned by the get token API are only valid for 24 hours. They can also be used exactly once.\nIf you want to invalidate one or more access or refresh tokens immediately, use this invalidate token API.",
         "operationId": "security-invalidate-token",
         "requestBody": {
           "content": {
@@ -29087,7 +29108,7 @@
         "tags": [
           "security"
         ],
-        "summary": "Retrieves security privileges for the logged in user",
+        "summary": "Get user privileges",
         "operationId": "security-get-user-privileges",
         "parameters": [
           {
@@ -29187,7 +29208,8 @@
         "tags": [
           "security"
         ],
-        "summary": "Retrieves a user's profile using the unique profile ID",
+        "summary": "Get a user profile",
+        "description": "Get a user's profile using the unique profile ID.",
         "operationId": "security-get-user-profile",
         "parameters": [
           {
@@ -29266,8 +29288,8 @@
         "tags": [
           "security"
         ],
-        "summary": "Creates an API key on behalf of another user",
-        "description": "This API is similar to Create API keys, however it creates the API key for a user that is different than the user that runs the API.\nThe caller must have authentication credentials (either an access token, or a username and password) for the user on whose behalf the API key will be created.\nIt is not possible to use this API to create an API key without that user’s credentials.\nThe user, for whom the authentication credentials is provided, can optionally \"run as\" (impersonate) another user.\nIn this case, the API key will be created on behalf of the impersonated user.\n\nThis API is intended be used by applications that need to create and manage API keys for end users, but cannot guarantee that those users have permission to create API keys on their own behalf.\n\nA successful grant API key API call returns a JSON structure that contains the API key, its unique id, and its name.\nIf applicable, it also returns expiration information for the API key in milliseconds.\n\nBy default, API keys never expire. You can specify expiration information when you create the API keys.",
+        "summary": "Grant an API key",
+        "description": "Create an API key on behalf of another user.\nThis API is similar to the create API keys API, however it creates the API key for a user that is different than the user that runs the API.\nThe caller must have authentication credentials (either an access token, or a username and password) for the user on whose behalf the API key will be created.\nIt is not possible to use this API to create an API key without that user’s credentials.\nThe user, for whom the authentication credentials is provided, can optionally \"run as\" (impersonate) another user.\nIn this case, the API key will be created on behalf of the impersonated user.\n\nThis API is intended be used by applications that need to create and manage API keys for end users, but cannot guarantee that those users have permission to create API keys on their own behalf.\n\nA successful grant API key API call returns a JSON structure that contains the API key, its unique id, and its name.\nIf applicable, it also returns expiration information for the API key in milliseconds.\n\nBy default, API keys never expire. You can specify expiration information when you create the API keys.",
         "operationId": "security-grant-api-key",
         "requestBody": {
           "content": {
@@ -29348,7 +29370,10 @@
           "security"
         ],
         "summary": "Check user privileges",
-        "description": "Determines whether the specified user has a specified list of privileges.",
+        "description": "Determine whether the specified user has a specified list of privileges.",
+        "externalDocs": {
+          "url": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-privileges.html"
+        },
         "operationId": "security-has-privileges",
         "requestBody": {
           "$ref": "#/components/requestBodies/security.has_privileges"
@@ -29365,7 +29390,10 @@
           "security"
         ],
         "summary": "Check user privileges",
-        "description": "Determines whether the specified user has a specified list of privileges.",
+        "description": "Determine whether the specified user has a specified list of privileges.",
+        "externalDocs": {
+          "url": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-privileges.html"
+        },
         "operationId": "security-has-privileges-1",
         "requestBody": {
           "$ref": "#/components/requestBodies/security.has_privileges"
@@ -29384,7 +29412,10 @@
           "security"
         ],
         "summary": "Check user privileges",
-        "description": "Determines whether the specified user has a specified list of privileges.",
+        "description": "Determine whether the specified user has a specified list of privileges.",
+        "externalDocs": {
+          "url": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-privileges.html"
+        },
         "operationId": "security-has-privileges-2",
         "parameters": [
           {
@@ -29406,7 +29437,10 @@
           "security"
         ],
         "summary": "Check user privileges",
-        "description": "Determines whether the specified user has a specified list of privileges.",
+        "description": "Determine whether the specified user has a specified list of privileges.",
+        "externalDocs": {
+          "url": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-privileges.html"
+        },
         "operationId": "security-has-privileges-3",
         "parameters": [
           {
@@ -29429,7 +29463,11 @@
         "tags": [
           "security"
         ],
-        "summary": "Determines whether the users associated with the specified profile IDs have all the requested privileges",
+        "summary": "Check user profile privileges",
+        "description": "Determine whether the users associated with the specified user profile IDs have all the requested privileges.",
+        "externalDocs": {
+          "url": "https://www.elastic.co/guide/en/elasticsearch/reference/current/user-profile.html"
+        },
         "operationId": "security-has-privileges-user-profile",
         "requestBody": {
           "$ref": "#/components/requestBodies/security.has_privileges_user_profile"
@@ -29445,7 +29483,11 @@
         "tags": [
           "security"
         ],
-        "summary": "Determines whether the users associated with the specified profile IDs have all the requested privileges",
+        "summary": "Check user profile privileges",
+        "description": "Determine whether the users associated with the specified user profile IDs have all the requested privileges.",
+        "externalDocs": {
+          "url": "https://www.elastic.co/guide/en/elasticsearch/reference/current/user-profile.html"
+        },
         "operationId": "security-has-privileges-user-profile-1",
         "requestBody": {
           "$ref": "#/components/requestBodies/security.has_privileges_user_profile"
@@ -29463,8 +29505,8 @@
         "tags": [
           "security"
         ],
-        "summary": "Query API keys",
-        "description": "Retrieves a paginated list of API keys and their information. You can optionally filter the results with a query.",
+        "summary": "Find API keys with a query",
+        "description": "Get a paginated list of API keys and their information. You can optionally filter the results with a query.",
         "operationId": "security-query-api-keys",
         "parameters": [
           {
@@ -29491,8 +29533,8 @@
         "tags": [
           "security"
         ],
-        "summary": "Query API keys",
-        "description": "Retrieves a paginated list of API keys and their information. You can optionally filter the results with a query.",
+        "summary": "Find API keys with a query",
+        "description": "Get a paginated list of API keys and their information. You can optionally filter the results with a query.",
         "operationId": "security-query-api-keys-1",
         "parameters": [
           {
@@ -29521,8 +29563,8 @@
         "tags": [
           "security"
         ],
-        "summary": "Retrieves roles in a paginated manner",
-        "description": "You can optionally filter the results with a query.",
+        "summary": "Find roles with a query",
+        "description": "Get roles in a paginated manner. You can optionally filter the results with a query.",
         "operationId": "security-query-role",
         "requestBody": {
           "$ref": "#/components/requestBodies/security.query_role"
@@ -29538,8 +29580,8 @@
         "tags": [
           "security"
         ],
-        "summary": "Retrieves roles in a paginated manner",
-        "description": "You can optionally filter the results with a query.",
+        "summary": "Find roles with a query",
+        "description": "Get roles in a paginated manner. You can optionally filter the results with a query.",
         "operationId": "security-query-role-1",
         "requestBody": {
           "$ref": "#/components/requestBodies/security.query_role"
@@ -29557,8 +29599,8 @@
         "tags": [
           "security"
         ],
-        "summary": "Retrieves information for Users in a paginated manner",
-        "description": "You can optionally filter the results with a query.",
+        "summary": "Find users with a query",
+        "description": "Get information for users in a paginated manner.\nYou can optionally filter the results with a query.",
         "operationId": "security-query-user",
         "parameters": [
           {
@@ -29579,8 +29621,8 @@
         "tags": [
           "security"
         ],
-        "summary": "Retrieves information for Users in a paginated manner",
-        "description": "You can optionally filter the results with a query.",
+        "summary": "Find users with a query",
+        "description": "Get information for users in a paginated manner.\nYou can optionally filter the results with a query.",
         "operationId": "security-query-user-1",
         "parameters": [
           {
@@ -29603,7 +29645,8 @@
         "tags": [
           "security"
         ],
-        "summary": "Submits a SAML Response message to Elasticsearch for consumption",
+        "summary": "Authenticate SAML",
+        "description": "Submits a SAML response message to Elasticsearch for consumption.",
         "operationId": "security-saml-authenticate",
         "requestBody": {
           "content": {
@@ -29676,7 +29719,8 @@
         "tags": [
           "security"
         ],
-        "summary": "Verifies the logout response sent from the SAML IdP",
+        "summary": "Logout of SAML completely",
+        "description": "Verifies the logout response sent from the SAML IdP.",
         "operationId": "security-saml-complete-logout",
         "requestBody": {
           "content": {
@@ -29725,7 +29769,8 @@
         "tags": [
           "security"
         ],
-        "summary": "Submits a SAML LogoutRequest message to Elasticsearch for consumption",
+        "summary": "Invalidate SAML",
+        "description": "Submits a SAML LogoutRequest message to Elasticsearch for consumption.",
         "operationId": "security-saml-invalidate",
         "requestBody": {
           "content": {
@@ -29790,7 +29835,8 @@
         "tags": [
           "security"
         ],
-        "summary": "Submits a request to invalidate an access token and refresh token",
+        "summary": "Logout of SAML",
+        "description": "Submits a request to invalidate an access token and refresh token.",
         "operationId": "security-saml-logout",
         "requestBody": {
           "content": {
@@ -29843,7 +29889,8 @@
         "tags": [
           "security"
         ],
-        "summary": "Creates a SAML authentication request (<AuthnRequest>) as a URL string, based on the configuration of the respective SAML realm in Elasticsearch",
+        "summary": "Prepare SAML authentication",
+        "description": "Creates a SAML authentication request (`<AuthnRequest>`) as a URL string, based on the configuration of the respective SAML realm in Elasticsearch.",
         "operationId": "security-saml-prepare-authentication",
         "requestBody": {
           "content": {
@@ -29905,7 +29952,8 @@
         "tags": [
           "security"
         ],
-        "summary": "Generate SAML metadata for a SAML 2.0 Service Provider",
+        "summary": "Create SAML service provider metadata",
+        "description": "Generate SAML metadata for a SAML 2.0 Service Provider.",
         "operationId": "security-saml-service-provider-metadata",
         "parameters": [
           {
@@ -29948,7 +29996,8 @@
         "tags": [
           "security"
         ],
-        "summary": "Get suggestions for user profiles that match specified search criteria",
+        "summary": "Suggest a user profile",
+        "description": "Get suggestions for user profiles that match specified search criteria.",
         "operationId": "security-suggest-user-profiles",
         "parameters": [
           {
@@ -29969,7 +30018,8 @@
         "tags": [
           "security"
         ],
-        "summary": "Get suggestions for user profiles that match specified search criteria",
+        "summary": "Suggest a user profile",
+        "description": "Get suggestions for user profiles that match specified search criteria.",
         "operationId": "security-suggest-user-profiles-1",
         "parameters": [
           {
@@ -30061,7 +30111,8 @@
         "tags": [
           "security"
         ],
-        "summary": "Updates specific data for the user profile that's associated with the specified unique ID",
+        "summary": "Update user profile data",
+        "description": "Update specific data for the user profile that is associated with a unique ID.",
         "operationId": "security-update-user-profile-data",
         "parameters": [
           {
@@ -30091,7 +30142,8 @@
         "tags": [
           "security"
         ],
-        "summary": "Updates specific data for the user profile that's associated with the specified unique ID",
+        "summary": "Update user profile data",
+        "description": "Update specific data for the user profile that is associated with a unique ID.",
         "operationId": "security-update-user-profile-data-1",
         "parameters": [
           {
diff --git a/output/openapi/elasticsearch-serverless-openapi.json b/output/openapi/elasticsearch-serverless-openapi.json
index 2f0c482af5..e8b54be087 100644
--- a/output/openapi/elasticsearch-serverless-openapi.json
+++ b/output/openapi/elasticsearch-serverless-openapi.json
@@ -17004,7 +17004,7 @@
           "security"
         ],
         "summary": "Invalidate API keys",
-        "description": "Invalidates one or more API keys.\nThe `manage_api_key` privilege allows deleting any API keys.\nThe `manage_own_api_key` only allows deleting API keys that are owned by the user.\nIn addition, with the `manage_own_api_key` privilege, an invalidation request must be issued in one of the three formats:\n- Set the parameter `owner=true`.\n- Or, set both `username` and `realm_name` to match the user’s identity.\n- Or, if the request is issued by an API key, i.e. an API key invalidates itself, specify its ID in the `ids` field.",
+        "description": "This API invalidates API keys created by the create API key or grant API key APIs.\nInvalidated API keys fail authentication, but they can still be viewed using the get API key information and query API key information APIs, for at least the configured retention period, until they are automatically deleted.\nThe `manage_api_key` privilege allows deleting any API keys.\nThe `manage_own_api_key` only allows deleting API keys that are owned by the user.\nIn addition, with the `manage_own_api_key` privilege, an invalidation request must be issued in one of the three formats:\n- Set the parameter `owner=true`.\n- Or, set both `username` and `realm_name` to match the user’s identity.\n- Or, if the request is issued by an API key, that is to say an API key invalidates itself, specify its ID in the `ids` field.",
         "operationId": "security-invalidate-api-key",
         "requestBody": {
           "content": {
@@ -17091,7 +17091,10 @@
           "security"
         ],
         "summary": "Check user privileges",
-        "description": "Determines whether the specified user has a specified list of privileges.",
+        "description": "Determine whether the specified user has a specified list of privileges.",
+        "externalDocs": {
+          "url": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-privileges.html"
+        },
         "operationId": "security-has-privileges",
         "requestBody": {
           "$ref": "#/components/requestBodies/security.has_privileges"
@@ -17108,7 +17111,10 @@
           "security"
         ],
         "summary": "Check user privileges",
-        "description": "Determines whether the specified user has a specified list of privileges.",
+        "description": "Determine whether the specified user has a specified list of privileges.",
+        "externalDocs": {
+          "url": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-privileges.html"
+        },
         "operationId": "security-has-privileges-1",
         "requestBody": {
           "$ref": "#/components/requestBodies/security.has_privileges"
@@ -17127,7 +17133,10 @@
           "security"
         ],
         "summary": "Check user privileges",
-        "description": "Determines whether the specified user has a specified list of privileges.",
+        "description": "Determine whether the specified user has a specified list of privileges.",
+        "externalDocs": {
+          "url": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-privileges.html"
+        },
         "operationId": "security-has-privileges-2",
         "parameters": [
           {
@@ -17149,7 +17158,10 @@
           "security"
         ],
         "summary": "Check user privileges",
-        "description": "Determines whether the specified user has a specified list of privileges.",
+        "description": "Determine whether the specified user has a specified list of privileges.",
+        "externalDocs": {
+          "url": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-privileges.html"
+        },
         "operationId": "security-has-privileges-3",
         "parameters": [
           {
@@ -17172,8 +17184,8 @@
         "tags": [
           "security"
         ],
-        "summary": "Query API keys",
-        "description": "Retrieves a paginated list of API keys and their information. You can optionally filter the results with a query.",
+        "summary": "Find API keys with a query",
+        "description": "Get a paginated list of API keys and their information. You can optionally filter the results with a query.",
         "operationId": "security-query-api-keys",
         "parameters": [
           {
@@ -17200,8 +17212,8 @@
         "tags": [
           "security"
         ],
-        "summary": "Query API keys",
-        "description": "Retrieves a paginated list of API keys and their information. You can optionally filter the results with a query.",
+        "summary": "Find API keys with a query",
+        "description": "Get a paginated list of API keys and their information. You can optionally filter the results with a query.",
         "operationId": "security-query-api-keys-1",
         "parameters": [
           {
diff --git a/output/schema/schema.json b/output/schema/schema.json
index 2ce927308c..7d9a6a7da7 100644
--- a/output/schema/schema.json
+++ b/output/schema/schema.json
@@ -16296,7 +16296,7 @@
           "stability": "stable"
         }
       },
-      "description": "Retrieves security privileges for the logged in user.",
+      "description": "Get user privileges.",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-get-user-privileges.html",
       "name": "security.get_user_privileges",
       "request": {
@@ -16331,7 +16331,7 @@
           "stability": "stable"
         }
       },
-      "description": "Retrieves a user's profile using the unique profile ID.",
+      "description": "Get a user profile.\n\nGet a user's profile using the unique profile ID.",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-get-user-profile.html",
       "name": "security.get_user_profile",
       "privileges": {
@@ -16371,7 +16371,7 @@
           "stability": "stable"
         }
       },
-      "description": "Creates an API key on behalf of another user.\nThis API is similar to Create API keys, however it creates the API key for a user that is different than the user that runs the API.\nThe caller must have authentication credentials (either an access token, or a username and password) for the user on whose behalf the API key will be created.\nIt is not possible to use this API to create an API key without that user’s credentials.\nThe user, for whom the authentication credentials is provided, can optionally \"run as\" (impersonate) another user.\nIn this case, the API key will be created on behalf of the impersonated user.\n\nThis API is intended be used by applications that need to create and manage API keys for end users, but cannot guarantee that those users have permission to create API keys on their own behalf.\n\nA successful grant API key API call returns a JSON structure that contains the API key, its unique id, and its name.\nIf applicable, it also returns expiration information for the API key in milliseconds.\n\nBy default, API keys never expire. You can specify expiration information when you create the API keys.",
+      "description": "Grant an API key.\n\nCreate an API key on behalf of another user.\nThis API is similar to the create API keys API, however it creates the API key for a user that is different than the user that runs the API.\nThe caller must have authentication credentials (either an access token, or a username and password) for the user on whose behalf the API key will be created.\nIt is not possible to use this API to create an API key without that user’s credentials.\nThe user, for whom the authentication credentials is provided, can optionally \"run as\" (impersonate) another user.\nIn this case, the API key will be created on behalf of the impersonated user.\n\nThis API is intended be used by applications that need to create and manage API keys for end users, but cannot guarantee that those users have permission to create API keys on their own behalf.\n\nA successful grant API key API call returns a JSON structure that contains the API key, its unique id, and its name.\nIf applicable, it also returns expiration information for the API key in milliseconds.\n\nBy default, API keys never expire. You can specify expiration information when you create the API keys.",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-grant-api-key.html",
       "name": "security.grant_api_key",
       "privileges": {
@@ -16414,8 +16414,10 @@
           "stability": "stable"
         }
       },
-      "description": "Check user privileges.\nDetermines whether the specified user has a specified list of privileges.",
+      "description": "Check user privileges.\n\nDetermine whether the specified user has a specified list of privileges.",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-has-privileges.html",
+      "extDocId": "security-privileges",
+      "extDocUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/{branch}/security-privileges.html",
       "name": "security.has_privileges",
       "request": {
         "name": "Request",
@@ -16460,8 +16462,10 @@
           "stability": "stable"
         }
       },
-      "description": "Determines whether the users associated with the specified profile IDs have all the requested privileges.",
+      "description": "Check user profile privileges.\n\nDetermine whether the users associated with the specified user profile IDs have all the requested privileges.",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-has-privileges-user-profile.html",
+      "extDocId": "user-profile",
+      "extDocUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/{branch}/user-profile.html",
       "name": "security.has_privileges_user_profile",
       "privileges": {
         "cluster": [
@@ -16504,7 +16508,7 @@
           "stability": "stable"
         }
       },
-      "description": "Invalidate API keys.\nInvalidates one or more API keys.\nThe `manage_api_key` privilege allows deleting any API keys.\nThe `manage_own_api_key` only allows deleting API keys that are owned by the user.\nIn addition, with the `manage_own_api_key` privilege, an invalidation request must be issued in one of the three formats:\n- Set the parameter `owner=true`.\n- Or, set both `username` and `realm_name` to match the user’s identity.\n- Or, if the request is issued by an API key, i.e. an API key invalidates itself, specify its ID in the `ids` field.",
+      "description": "Invalidate API keys.\n\nThis API invalidates API keys created by the create API key or grant API key APIs.\nInvalidated API keys fail authentication, but they can still be viewed using the get API key information and query API key information APIs, for at least the configured retention period, until they are automatically deleted.\nThe `manage_api_key` privilege allows deleting any API keys.\nThe `manage_own_api_key` only allows deleting API keys that are owned by the user.\nIn addition, with the `manage_own_api_key` privilege, an invalidation request must be issued in one of the three formats:\n- Set the parameter `owner=true`.\n- Or, set both `username` and `realm_name` to match the user’s identity.\n- Or, if the request is issued by an API key, that is to say an API key invalidates itself, specify its ID in the `ids` field.",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-invalidate-api-key.html",
       "name": "security.invalidate_api_key",
       "privileges": {
@@ -16548,7 +16552,7 @@
           "stability": "stable"
         }
       },
-      "description": "Invalidates one or more access tokens or refresh tokens.",
+      "description": "Invalidate a token.\n\nThe access tokens returned by the get token API have a finite period of time for which they are valid.\nAfter that time period, they can no longer be used.\nThe time period is defined by the `xpack.security.authc.token.timeout` setting.\n\nThe refresh tokens returned by the get token API are only valid for 24 hours. They can also be used exactly once.\nIf you want to invalidate one or more access or refresh tokens immediately, use this invalidate token API.",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-invalidate-token.html",
       "name": "security.invalidate_token",
       "request": {
@@ -16670,8 +16674,10 @@
           "stability": "stable"
         }
       },
-      "description": "Adds or updates application privileges.",
+      "description": "Create or update application privileges.",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-put-privileges.html",
+      "extDocId": "security-privileges",
+      "extDocUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/{branch}/security-privileges.html",
       "name": "security.put_privileges",
       "request": {
         "name": "Request",
@@ -16708,8 +16714,10 @@
           "stability": "stable"
         }
       },
-      "description": "The role management APIs are generally the preferred way to manage roles, rather than using file-based role management.\nThe create or update roles API cannot update roles that are defined in roles files.",
+      "description": "Create or update roles.\n\nThe role management APIs are generally the preferred way to manage roles in the native realm, rather than using file-based role management.\nThe create or update roles API cannot update roles that are defined in roles files.\nFile-based role management is not available in Elastic Serverless.",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-put-role.html",
+      "extDocId": "defining-roles",
+      "extDocUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/{branch}/defining-roles.html",
       "name": "security.put_role",
       "privileges": {
         "cluster": [
@@ -16752,8 +16760,10 @@
           "stability": "stable"
         }
       },
-      "description": "Creates and updates role mappings.",
+      "description": "Create or update role mappings.\n\nRole mappings define which roles are assigned to each user.\nEach mapping has rules that identify users and a list of roles that are granted to those users.\nThe role mapping APIs are generally the preferred way to manage role mappings rather than using role mapping files. The create or update role mappings API cannot update role mappings that are defined in role mapping files.\n\nThis API does not create roles. Rather, it maps users to existing roles.\nRoles can be created by using the create or update roles API or roles files.",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-put-role-mapping.html",
+      "extDocId": "mapping-roles",
+      "extDocUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/{branch}/mapping-roles.html",
       "name": "security.put_role_mapping",
       "request": {
         "name": "Request",
@@ -16786,7 +16796,7 @@
           "stability": "stable"
         }
       },
-      "description": "Adds and updates users in the native realm. These users are commonly referred to as native users.",
+      "description": "Create or update users.\n\nA password is required for adding a new user but is optional when updating an existing user.\nTo change a user’s password without updating any other fields, use the change password API.",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-put-user.html",
       "name": "security.put_user",
       "request": {
@@ -16825,7 +16835,7 @@
           "stability": "stable"
         }
       },
-      "description": "Query API keys.\nRetrieves a paginated list of API keys and their information. You can optionally filter the results with a query.",
+      "description": "Find API keys with a query.\n\nGet a paginated list of API keys and their information. You can optionally filter the results with a query.",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-query-api-key.html",
       "name": "security.query_api_keys",
       "privileges": {
@@ -16870,7 +16880,7 @@
           "stability": "stable"
         }
       },
-      "description": "Retrieves roles in a paginated manner. You can optionally filter the results with a query.",
+      "description": "Find roles with a query.\n\nGet roles in a paginated manner. You can optionally filter the results with a query.",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-query-role.html",
       "name": "security.query_role",
       "privileges": {
@@ -16914,7 +16924,7 @@
           "stability": "stable"
         }
       },
-      "description": "Retrieves information for Users in a paginated manner. You can optionally filter the results with a query.",
+      "description": "Find users with a query.\n\nGet information for users in a paginated manner.\nYou can optionally filter the results with a query.",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-query-user.html",
       "name": "security.query_user",
       "privileges": {
@@ -16958,7 +16968,7 @@
           "stability": "stable"
         }
       },
-      "description": "Submits a SAML Response message to Elasticsearch for consumption.",
+      "description": "Authenticate SAML.\n\nSubmits a SAML response message to Elasticsearch for consumption.",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-saml-authenticate.html",
       "name": "security.saml_authenticate",
       "request": {
@@ -16996,7 +17006,7 @@
           "stability": "stable"
         }
       },
-      "description": "Verifies the logout response sent from the SAML IdP.",
+      "description": "Logout of SAML completely.\n\nVerifies the logout response sent from the SAML IdP.",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-saml-complete-logout.html",
       "name": "security.saml_complete_logout",
       "request": {
@@ -17034,7 +17044,7 @@
           "stability": "stable"
         }
       },
-      "description": "Submits a SAML LogoutRequest message to Elasticsearch for consumption.",
+      "description": "Invalidate SAML.\n\nSubmits a SAML LogoutRequest message to Elasticsearch for consumption.",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-saml-invalidate.html",
       "name": "security.saml_invalidate",
       "request": {
@@ -17072,7 +17082,7 @@
           "stability": "stable"
         }
       },
-      "description": "Submits a request to invalidate an access token and refresh token.",
+      "description": "Logout of SAML.\n\nSubmits a request to invalidate an access token and refresh token.",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-saml-logout.html",
       "name": "security.saml_logout",
       "request": {
@@ -17110,7 +17120,7 @@
           "stability": "stable"
         }
       },
-      "description": "Creates a SAML authentication request (<AuthnRequest>) as a URL string, based on the configuration of the respective SAML realm in Elasticsearch.",
+      "description": "Prepare SAML authentication.\n\nCreates a SAML authentication request (`<AuthnRequest>`) as a URL string, based on the configuration of the respective SAML realm in Elasticsearch.",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-saml-prepare-authentication.html",
       "name": "security.saml_prepare_authentication",
       "request": {
@@ -17148,7 +17158,7 @@
           "stability": "stable"
         }
       },
-      "description": "Generate SAML metadata for a SAML 2.0 Service Provider.",
+      "description": "Create SAML service provider metadata.\n\nGenerate SAML metadata for a SAML 2.0 Service Provider.",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-saml-sp-metadata.html",
       "name": "security.saml_service_provider_metadata",
       "request": {
@@ -17186,7 +17196,7 @@
           "stability": "stable"
         }
       },
-      "description": "Get suggestions for user profiles that match specified search criteria.",
+      "description": "Suggest a user profile.\n\nGet suggestions for user profiles that match specified search criteria.",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/master/security-api-suggest-user-profile.html",
       "name": "security.suggest_user_profiles",
       "request": {
@@ -17225,7 +17235,7 @@
           "stability": "stable"
         }
       },
-      "description": "Update an API key.\nUpdates attributes of an existing API key.\nUsers can only update API keys that they created or that were granted to them.\nUse this API to update API keys created by the create API Key or grant API Key APIs.\nIf you need to apply the same update to many API keys, you can use bulk update API Keys to reduce overhead.\nIt’s not possible to update expired API keys, or API keys that have been invalidated by invalidate API Key.\nThis API supports updates to an API key’s access scope and metadata.\nThe access scope of an API key is derived from the `role_descriptors` you specify in the request, and a snapshot of the owner user’s permissions at the time of the request.\nThe snapshot of the owner’s permissions is updated automatically on every call.\nIf you don’t specify `role_descriptors` in the request, a call to this API might still change the API key’s access scope.\nThis change can occur if the owner user’s permissions have changed since the API key was created or last modified.\nTo update another user’s API key, use the `run_as` feature to submit a request on behalf of another user.\nIMPORTANT: It’s not possible to use an API key as the authentication credential for this API.\nTo update an API key, the owner user’s credentials are required.",
+      "description": "Update an API key.\n\nUpdates attributes of an existing API key.\nUsers can only update API keys that they created or that were granted to them.\nUse this API to update API keys created by the create API Key or grant API Key APIs.\nIf you need to apply the same update to many API keys, you can use bulk update API Keys to reduce overhead.\nIt’s not possible to update expired API keys, or API keys that have been invalidated by invalidate API Key.\nThis API supports updates to an API key’s access scope and metadata.\nThe access scope of an API key is derived from the `role_descriptors` you specify in the request, and a snapshot of the owner user’s permissions at the time of the request.\nThe snapshot of the owner’s permissions is updated automatically on every call.\nIf you don’t specify `role_descriptors` in the request, a call to this API might still change the API key’s access scope.\nThis change can occur if the owner user’s permissions have changed since the API key was created or last modified.\nTo update another user’s API key, use the `run_as` feature to submit a request on behalf of another user.\nIMPORTANT: It’s not possible to use an API key as the authentication credential for this API.\nTo update an API key, the owner user’s credentials are required.",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-update-api-key.html",
       "name": "security.update_api_key",
       "privileges": {
@@ -17324,7 +17334,7 @@
           "stability": "stable"
         }
       },
-      "description": "Updates specific data for the user profile that's associated with the specified unique ID.",
+      "description": "Update user profile data.\n\nUpdate specific data for the user profile that is associated with a unique ID.",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-update-user-profile-data.html",
       "name": "security.update_user_profile_data",
       "privileges": {
@@ -191714,7 +191724,7 @@
       "body": {
         "kind": "no_body"
       },
-      "description": "Retrieves security privileges for the logged in user.",
+      "description": "Get user privileges.",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -191775,7 +191785,7 @@
           }
         }
       ],
-      "specLocation": "security/get_user_privileges/SecurityGetUserPrivilegesRequest.ts#L23-L36"
+      "specLocation": "security/get_user_privileges/SecurityGetUserPrivilegesRequest.ts#L23-L37"
     },
     {
       "kind": "response",
@@ -191911,7 +191921,7 @@
       "body": {
         "kind": "no_body"
       },
-      "description": "Retrieves a user's profile using the unique profile ID.",
+      "description": "Get a user profile.\n\nGet a user's profile using the unique profile ID.",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -191980,7 +191990,7 @@
           }
         }
       ],
-      "specLocation": "security/get_user_profile/Request.ts#L23-L46"
+      "specLocation": "security/get_user_profile/Request.ts#L23-L48"
     },
     {
       "kind": "response",
@@ -192212,7 +192222,7 @@
           }
         ]
       },
-      "description": "Creates an API key on behalf of another user.\nThis API is similar to Create API keys, however it creates the API key for a user that is different than the user that runs the API.\nThe caller must have authentication credentials (either an access token, or a username and password) for the user on whose behalf the API key will be created.\nIt is not possible to use this API to create an API key without that user’s credentials.\nThe user, for whom the authentication credentials is provided, can optionally \"run as\" (impersonate) another user.\nIn this case, the API key will be created on behalf of the impersonated user.\n\nThis API is intended be used by applications that need to create and manage API keys for end users, but cannot guarantee that those users have permission to create API keys on their own behalf.\n\nA successful grant API key API call returns a JSON structure that contains the API key, its unique id, and its name.\nIf applicable, it also returns expiration information for the API key in milliseconds.\n\nBy default, API keys never expire. You can specify expiration information when you create the API keys.",
+      "description": "Grant an API key.\n\nCreate an API key on behalf of another user.\nThis API is similar to the create API keys API, however it creates the API key for a user that is different than the user that runs the API.\nThe caller must have authentication credentials (either an access token, or a username and password) for the user on whose behalf the API key will be created.\nIt is not possible to use this API to create an API key without that user’s credentials.\nThe user, for whom the authentication credentials is provided, can optionally \"run as\" (impersonate) another user.\nIn this case, the API key will be created on behalf of the impersonated user.\n\nThis API is intended be used by applications that need to create and manage API keys for end users, but cannot guarantee that those users have permission to create API keys on their own behalf.\n\nA successful grant API key API call returns a JSON structure that contains the API key, its unique id, and its name.\nIf applicable, it also returns expiration information for the API key in milliseconds.\n\nBy default, API keys never expire. You can specify expiration information when you create the API keys.",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -192225,7 +192235,7 @@
       },
       "path": [],
       "query": [],
-      "specLocation": "security/grant_api_key/SecurityGrantApiKeyRequest.ts#L24-L75"
+      "specLocation": "security/grant_api_key/SecurityGrantApiKeyRequest.ts#L24-L77"
     },
     {
       "kind": "response",
@@ -192510,7 +192520,7 @@
           }
         ]
       },
-      "description": "Check user privileges.\nDetermines whether the specified user has a specified list of privileges.",
+      "description": "Check user privileges.\n\nDetermine whether the specified user has a specified list of privileges.",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -192536,7 +192546,7 @@
         }
       ],
       "query": [],
-      "specLocation": "security/has_privileges/SecurityHasPrivilegesRequest.ts#L25-L44"
+      "specLocation": "security/has_privileges/SecurityHasPrivilegesRequest.ts#L25-L46"
     },
     {
       "kind": "type_alias",
@@ -192786,7 +192796,7 @@
           }
         ]
       },
-      "description": "Determines whether the users associated with the specified profile IDs have all the requested privileges.",
+      "description": "Check user profile privileges.\n\nDetermine whether the users associated with the specified user profile IDs have all the requested privileges.",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -192799,7 +192809,7 @@
       },
       "path": [],
       "query": [],
-      "specLocation": "security/has_privileges_user_profile/Request.ts#L24-L38"
+      "specLocation": "security/has_privileges_user_profile/Request.ts#L24-L42"
     },
     {
       "kind": "response",
@@ -192926,7 +192936,7 @@
           }
         ]
       },
-      "description": "Invalidate API keys.\nInvalidates one or more API keys.\nThe `manage_api_key` privilege allows deleting any API keys.\nThe `manage_own_api_key` only allows deleting API keys that are owned by the user.\nIn addition, with the `manage_own_api_key` privilege, an invalidation request must be issued in one of the three formats:\n- Set the parameter `owner=true`.\n- Or, set both `username` and `realm_name` to match the user’s identity.\n- Or, if the request is issued by an API key, i.e. an API key invalidates itself, specify its ID in the `ids` field.",
+      "description": "Invalidate API keys.\n\nThis API invalidates API keys created by the create API key or grant API key APIs.\nInvalidated API keys fail authentication, but they can still be viewed using the get API key information and query API key information APIs, for at least the configured retention period, until they are automatically deleted.\nThe `manage_api_key` privilege allows deleting any API keys.\nThe `manage_own_api_key` only allows deleting API keys that are owned by the user.\nIn addition, with the `manage_own_api_key` privilege, an invalidation request must be issued in one of the three formats:\n- Set the parameter `owner=true`.\n- Or, set both `username` and `realm_name` to match the user’s identity.\n- Or, if the request is issued by an API key, that is to say an API key invalidates itself, specify its ID in the `ids` field.",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -192939,7 +192949,7 @@
       },
       "path": [],
       "query": [],
-      "specLocation": "security/invalidate_api_key/SecurityInvalidateApiKeyRequest.ts#L23-L67"
+      "specLocation": "security/invalidate_api_key/SecurityInvalidateApiKeyRequest.ts#L23-L69"
     },
     {
       "kind": "response",
@@ -193061,7 +193071,7 @@
           }
         ]
       },
-      "description": "Invalidates one or more access tokens or refresh tokens.",
+      "description": "Invalidate a token.\n\nThe access tokens returned by the get token API have a finite period of time for which they are valid.\nAfter that time period, they can no longer be used.\nThe time period is defined by the `xpack.security.authc.token.timeout` setting.\n\nThe refresh tokens returned by the get token API are only valid for 24 hours. They can also be used exactly once.\nIf you want to invalidate one or more access or refresh tokens immediately, use this invalidate token API.",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -193074,7 +193084,7 @@
       },
       "path": [],
       "query": [],
-      "specLocation": "security/invalidate_token/SecurityInvalidateTokenRequest.ts#L23-L35"
+      "specLocation": "security/invalidate_token/SecurityInvalidateTokenRequest.ts#L23-L43"
     },
     {
       "kind": "response",
@@ -193231,7 +193241,7 @@
           }
         }
       },
-      "description": "Adds or updates application privileges.",
+      "description": "Create or update application privileges.",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -193257,7 +193267,7 @@
           }
         }
       ],
-      "specLocation": "security/put_privileges/SecurityPutPrivilegesRequest.ts#L25-L37"
+      "specLocation": "security/put_privileges/SecurityPutPrivilegesRequest.ts#L25-L38"
     },
     {
       "kind": "response",
@@ -193456,7 +193466,7 @@
           }
         ]
       },
-      "description": "The role management APIs are generally the preferred way to manage roles, rather than using file-based role management.\nThe create or update roles API cannot update roles that are defined in roles files.",
+      "description": "Create or update roles.\n\nThe role management APIs are generally the preferred way to manage roles in the native realm, rather than using file-based role management.\nThe create or update roles API cannot update roles that are defined in roles files.\nFile-based role management is not available in Elastic Serverless.",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -193495,7 +193505,7 @@
           }
         }
       ],
-      "specLocation": "security/put_role/SecurityPutRoleRequest.ts#L31-L91"
+      "specLocation": "security/put_role/SecurityPutRoleRequest.ts#L31-L95"
     },
     {
       "kind": "response",
@@ -193606,7 +193616,7 @@
           }
         ]
       },
-      "description": "Creates and updates role mappings.",
+      "description": "Create or update role mappings.\n\nRole mappings define which roles are assigned to each user.\nEach mapping has rules that identify users and a list of roles that are granted to those users.\nThe role mapping APIs are generally the preferred way to manage role mappings rather than using role mapping files. The create or update role mappings API cannot update role mappings that are defined in role mapping files.\n\nThis API does not create roles. Rather, it maps users to existing roles.\nRoles can be created by using the create or update roles API or roles files.",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -193645,7 +193655,7 @@
           }
         }
       ],
-      "specLocation": "security/put_role_mapping/SecurityPutRoleMappingRequest.ts#L25-L47"
+      "specLocation": "security/put_role_mapping/SecurityPutRoleMappingRequest.ts#L25-L56"
     },
     {
       "kind": "response",
@@ -193807,7 +193817,7 @@
           }
         ]
       },
-      "description": "Adds and updates users in the native realm. These users are commonly referred to as native users.",
+      "description": "Create or update users.\n\nA password is required for adding a new user but is optional when updating an existing user.\nTo change a user’s password without updating any other fields, use the change password API.",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -193846,7 +193856,7 @@
           }
         }
       ],
-      "specLocation": "security/put_user/SecurityPutUserRequest.ts#L23-L44"
+      "specLocation": "security/put_user/SecurityPutUserRequest.ts#L23-L48"
     },
     {
       "kind": "response",
@@ -194552,7 +194562,7 @@
           }
         ]
       },
-      "description": "Query API keys.\nRetrieves a paginated list of API keys and their information. You can optionally filter the results with a query.",
+      "description": "Find API keys with a query.\n\nGet a paginated list of API keys and their information. You can optionally filter the results with a query.",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -194622,7 +194632,7 @@
           }
         }
       ],
-      "specLocation": "security/query_api_keys/QueryApiKeysRequest.ts#L26-L100"
+      "specLocation": "security/query_api_keys/QueryApiKeysRequest.ts#L26-L101"
     },
     {
       "kind": "response",
@@ -194812,7 +194822,7 @@
           }
         ]
       },
-      "description": "Retrieves roles in a paginated manner. You can optionally filter the results with a query.",
+      "description": "Find roles with a query.\n\nGet roles in a paginated manner. You can optionally filter the results with a query.",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -194825,7 +194835,7 @@
       },
       "path": [],
       "query": [],
-      "specLocation": "security/query_role/QueryRolesRequest.ts#L25-L67"
+      "specLocation": "security/query_role/QueryRolesRequest.ts#L25-L69"
     },
     {
       "kind": "response",
@@ -195203,7 +195213,7 @@
           }
         ]
       },
-      "description": "Retrieves information for Users in a paginated manner. You can optionally filter the results with a query.",
+      "description": "Find users with a query.\n\nGet information for users in a paginated manner.\nYou can optionally filter the results with a query.",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -195229,7 +195239,7 @@
           }
         }
       ],
-      "specLocation": "security/query_user/SecurityQueryUserRequest.ts#L25-L72"
+      "specLocation": "security/query_user/SecurityQueryUserRequest.ts#L25-L75"
     },
     {
       "kind": "response",
@@ -195552,7 +195562,7 @@
           }
         ]
       },
-      "description": "Submits a SAML Response message to Elasticsearch for consumption.",
+      "description": "Authenticate SAML.\n\nSubmits a SAML response message to Elasticsearch for consumption.",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -195565,7 +195575,7 @@
       },
       "path": [],
       "query": [],
-      "specLocation": "security/saml_authenticate/Request.ts#L23-L38"
+      "specLocation": "security/saml_authenticate/Request.ts#L23-L40"
     },
     {
       "kind": "response",
@@ -195693,7 +195703,7 @@
           }
         ]
       },
-      "description": "Verifies the logout response sent from the SAML IdP.",
+      "description": "Logout of SAML completely.\n\nVerifies the logout response sent from the SAML IdP.",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -195706,7 +195716,7 @@
       },
       "path": [],
       "query": [],
-      "specLocation": "security/saml_complete_logout/Request.ts#L23-L40"
+      "specLocation": "security/saml_complete_logout/Request.ts#L23-L42"
     },
     {
       "kind": "response",
@@ -195765,7 +195775,7 @@
           }
         ]
       },
-      "description": "Submits a SAML LogoutRequest message to Elasticsearch for consumption.",
+      "description": "Invalidate SAML.\n\nSubmits a SAML LogoutRequest message to Elasticsearch for consumption.",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -195778,7 +195788,7 @@
       },
       "path": [],
       "query": [],
-      "specLocation": "security/saml_invalidate/Request.ts#L22-L43"
+      "specLocation": "security/saml_invalidate/Request.ts#L22-L45"
     },
     {
       "kind": "response",
@@ -195860,7 +195870,7 @@
           }
         ]
       },
-      "description": "Submits a request to invalidate an access token and refresh token.",
+      "description": "Logout of SAML.\n\nSubmits a request to invalidate an access token and refresh token.",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -195873,7 +195883,7 @@
       },
       "path": [],
       "query": [],
-      "specLocation": "security/saml_logout/Request.ts#L22-L41"
+      "specLocation": "security/saml_logout/Request.ts#L22-L43"
     },
     {
       "kind": "response",
@@ -195945,7 +195955,7 @@
           }
         ]
       },
-      "description": "Creates a SAML authentication request (<AuthnRequest>) as a URL string, based on the configuration of the respective SAML realm in Elasticsearch.",
+      "description": "Prepare SAML authentication.\n\nCreates a SAML authentication request (`<AuthnRequest>`) as a URL string, based on the configuration of the respective SAML realm in Elasticsearch.",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -195958,7 +195968,7 @@
       },
       "path": [],
       "query": [],
-      "specLocation": "security/saml_prepare_authentication/Request.ts#L22-L46"
+      "specLocation": "security/saml_prepare_authentication/Request.ts#L22-L48"
     },
     {
       "kind": "response",
@@ -196014,7 +196024,7 @@
       "body": {
         "kind": "no_body"
       },
-      "description": "Generate SAML metadata for a SAML 2.0 Service Provider.",
+      "description": "Create SAML service provider metadata.\n\nGenerate SAML metadata for a SAML 2.0 Service Provider.",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -196040,7 +196050,7 @@
         }
       ],
       "query": [],
-      "specLocation": "security/saml_service_provider_metadata/Request.ts#L23-L34"
+      "specLocation": "security/saml_service_provider_metadata/Request.ts#L23-L36"
     },
     {
       "kind": "response",
@@ -196203,7 +196213,7 @@
           }
         ]
       },
-      "description": "Get suggestions for user profiles that match specified search criteria.",
+      "description": "Suggest a user profile.\n\nGet suggestions for user profiles that match specified search criteria.",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -196244,7 +196254,7 @@
           }
         }
       ],
-      "specLocation": "security/suggest_user_profiles/Request.ts#L24-L66"
+      "specLocation": "security/suggest_user_profiles/Request.ts#L24-L68"
     },
     {
       "kind": "response",
@@ -196386,7 +196396,7 @@
           }
         ]
       },
-      "description": "Update an API key.\nUpdates attributes of an existing API key.\nUsers can only update API keys that they created or that were granted to them.\nUse this API to update API keys created by the create API Key or grant API Key APIs.\nIf you need to apply the same update to many API keys, you can use bulk update API Keys to reduce overhead.\nIt’s not possible to update expired API keys, or API keys that have been invalidated by invalidate API Key.\nThis API supports updates to an API key’s access scope and metadata.\nThe access scope of an API key is derived from the `role_descriptors` you specify in the request, and a snapshot of the owner user’s permissions at the time of the request.\nThe snapshot of the owner’s permissions is updated automatically on every call.\nIf you don’t specify `role_descriptors` in the request, a call to this API might still change the API key’s access scope.\nThis change can occur if the owner user’s permissions have changed since the API key was created or last modified.\nTo update another user’s API key, use the `run_as` feature to submit a request on behalf of another user.\nIMPORTANT: It’s not possible to use an API key as the authentication credential for this API.\nTo update an API key, the owner user’s credentials are required.",
+      "description": "Update an API key.\n\nUpdates attributes of an existing API key.\nUsers can only update API keys that they created or that were granted to them.\nUse this API to update API keys created by the create API Key or grant API Key APIs.\nIf you need to apply the same update to many API keys, you can use bulk update API Keys to reduce overhead.\nIt’s not possible to update expired API keys, or API keys that have been invalidated by invalidate API Key.\nThis API supports updates to an API key’s access scope and metadata.\nThe access scope of an API key is derived from the `role_descriptors` you specify in the request, and a snapshot of the owner user’s permissions at the time of the request.\nThe snapshot of the owner’s permissions is updated automatically on every call.\nIf you don’t specify `role_descriptors` in the request, a call to this API might still change the API key’s access scope.\nThis change can occur if the owner user’s permissions have changed since the API key was created or last modified.\nTo update another user’s API key, use the `run_as` feature to submit a request on behalf of another user.\nIMPORTANT: It’s not possible to use an API key as the authentication credential for this API.\nTo update an API key, the owner user’s credentials are required.",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -196412,7 +196422,7 @@
         }
       ],
       "query": [],
-      "specLocation": "security/update_api_key/Request.ts#L26-L66"
+      "specLocation": "security/update_api_key/Request.ts#L26-L67"
     },
     {
       "kind": "response",
@@ -196487,7 +196497,7 @@
           }
         ]
       },
-      "description": "Updates specific data for the user profile that's associated with the specified unique ID.",
+      "description": "Update user profile data.\n\nUpdate specific data for the user profile that is associated with a unique ID.",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -196551,7 +196561,7 @@
           }
         }
       ],
-      "specLocation": "security/update_user_profile_data/Request.ts#L27-L70"
+      "specLocation": "security/update_user_profile_data/Request.ts#L27-L72"
     },
     {
       "kind": "response",