agilicus 1.304.0__py3-none-any.whl → 1.304.2__py3-none-any.whl

agilicus/.openapi-generator/FILES

@@ -366,6 +366,7 @@ agilicus_api/docs/FileTemplateSpec.md
 agilicus_api/docs/FileVisibility.md
 agilicus_api/docs/FilesApi.md
 agilicus_api/docs/FormInjection.md
+agilicus_api/docs/FormInjectionConfig.md
 agilicus_api/docs/FrameOptionsSettings.md
 agilicus_api/docs/GenericFloatMetric.md
 agilicus_api/docs/GenericIntMetric.md
@@ -1293,6 +1294,7 @@ agilicus_api/model/file_template_resource_info.py
 agilicus_api/model/file_template_spec.py
 agilicus_api/model/file_visibility.py
 agilicus_api/model/form_injection.py
+agilicus_api/model/form_injection_config.py
 agilicus_api/model/frame_options_settings.py
 agilicus_api/model/generic_float_metric.py
 agilicus_api/model/generic_int_metric.py
@@ -2213,6 +2215,7 @@ agilicus_api/test/test_file_template_spec.py
 agilicus_api/test/test_file_visibility.py
 agilicus_api/test/test_files_api.py
 agilicus_api/test/test_form_injection.py
+agilicus_api/test/test_form_injection_config.py
 agilicus_api/test/test_frame_options_settings.py
 agilicus_api/test/test_generic_float_metric.py
 agilicus_api/test/test_generic_int_metric.py

agilicus/agilicus_api/__init__.py

@@ -5,7 +5,7 @@
 
     Agilicus is API-first. Modern software is controlled by other software, is open, is available for you to use the way you want, securely, simply.  The OpenAPI Specification in YAML format is available on [www](https://www.agilicus.com/www/api/agilicus-openapi.yaml) for importing to other tools.  A rendered, online viewable and usable version of this specification is available at [api](https://www.agilicus.com/api). You may try the API inline directly in the web page. To do so, first obtain an Authentication Token (the simplest way is to install the Python SDK, and then run `agilicus-cli --issuer https://MYISSUER get-token`). You will need an org-id for most calls (and can obtain from `agilicus-cli --issuer https://MYISSUER list-orgs`). The `MYISSUER` will typically be `auth.MYDOMAIN`, and you will see it as you sign-in to the administrative UI.  This API releases on Bearer-Token authentication. To obtain a valid bearer token you will need to Authenticate to an Issuer with OpenID Connect (a superset of OAUTH2).  Your \"issuer\" will look like https://auth.MYDOMAIN. For example, when you signed-up, if you said \"use my own domain name\" and assigned a CNAME of cloud.example.com, then your issuer would be https://auth.cloud.example.com.  If you selected \"use an Agilicus supplied domain name\", your issuer would look like https://auth.myorg.agilicus.cloud.  For test purposes you can use our [Python SDK](https://pypi.org/project/agilicus/) and run `agilicus-cli --issuer https://auth.MYDOMAIN get-token`.  This API may be used in any language runtime that supports OpenAPI 3.0, or, you may use our [Python SDK](https://pypi.org/project/agilicus/), our [Typescript SDK](https://www.npmjs.com/package/@agilicus/angular), or our [Golang SDK](https://git.agilicus.com/pub/sdk-go).  100% of the activities in our system our API-driven, from our web-admin, through our progressive web applications, to all internals: there is nothing that is not accessible.  For more information, see [developer resources](https://www.agilicus.com/developer).   # noqa: E501
 
-    The version of the OpenAPI document: 2025.10.23
+    The version of the OpenAPI document: 2025.10.28
     Contact: dev@agilicus.com
     Generated by: https://openapi-generator.tech
 """
@@ -346,6 +346,7 @@ from agilicus_api.model.file_template_resource_info import FileTemplateResourceI
 from agilicus_api.model.file_template_spec import FileTemplateSpec
 from agilicus_api.model.file_visibility import FileVisibility
 from agilicus_api.model.form_injection import FormInjection
+from agilicus_api.model.form_injection_config import FormInjectionConfig
 from agilicus_api.model.frame_options_settings import FrameOptionsSettings
 from agilicus_api.model.generic_float_metric import GenericFloatMetric
 from agilicus_api.model.generic_int_metric import GenericIntMetric

agilicus/agilicus_api/api/application_services_api.py

@@ -3,7 +3,7 @@
 
     Agilicus is API-first. Modern software is controlled by other software, is open, is available for you to use the way you want, securely, simply.  The OpenAPI Specification in YAML format is available on [www](https://www.agilicus.com/www/api/agilicus-openapi.yaml) for importing to other tools.  A rendered, online viewable and usable version of this specification is available at [api](https://www.agilicus.com/api). You may try the API inline directly in the web page. To do so, first obtain an Authentication Token (the simplest way is to install the Python SDK, and then run `agilicus-cli --issuer https://MYISSUER get-token`). You will need an org-id for most calls (and can obtain from `agilicus-cli --issuer https://MYISSUER list-orgs`). The `MYISSUER` will typically be `auth.MYDOMAIN`, and you will see it as you sign-in to the administrative UI.  This API releases on Bearer-Token authentication. To obtain a valid bearer token you will need to Authenticate to an Issuer with OpenID Connect (a superset of OAUTH2).  Your \"issuer\" will look like https://auth.MYDOMAIN. For example, when you signed-up, if you said \"use my own domain name\" and assigned a CNAME of cloud.example.com, then your issuer would be https://auth.cloud.example.com.  If you selected \"use an Agilicus supplied domain name\", your issuer would look like https://auth.myorg.agilicus.cloud.  For test purposes you can use our [Python SDK](https://pypi.org/project/agilicus/) and run `agilicus-cli --issuer https://auth.MYDOMAIN get-token`.  This API may be used in any language runtime that supports OpenAPI 3.0, or, you may use our [Python SDK](https://pypi.org/project/agilicus/), our [Typescript SDK](https://www.npmjs.com/package/@agilicus/angular), or our [Golang SDK](https://git.agilicus.com/pub/sdk-go).  100% of the activities in our system our API-driven, from our web-admin, through our progressive web applications, to all internals: there is nothing that is not accessible.  For more information, see [developer resources](https://www.agilicus.com/developer).   # noqa: E501
 
-    The version of the OpenAPI document: 2025.10.23
+    The version of the OpenAPI document: 2025.10.28
     Contact: dev@agilicus.com
     Generated by: https://openapi-generator.tech
 """
@@ -3394,6 +3394,10 @@ class ApplicationServicesApi(object):
                 resource_id (str): The id of the resource to query for. [optional]
                 page_at_id (str): Pagination based query with the id as the key. To get the initial entries supply an empty string. On subsequent requests, supply the `page_at_id` field from the list response. . [optional]
                 name_slug (str): The slug of the resource to query for. [optional]
+                page_on ([str]): A list of fields to page on and sort by, in order. Results will be sorted in order of the first item in the list, followed by second and so on.  The page to retrieve is defined in page_at_key, whose entries correspond to the previous page's values for the respective keys.  The results are sorted according to the optional page_sort whose entries define, respectively, whether to sort ascending or descending by the given field. . [optional]
+                page_at_key ([str, none_type]): The values defining the item in a collection immediately preceeding the page to fetch.  The meaning of the entries is defined in page_on. For example, if page_on is `[\"name\", \"created\"]`, and page_at_key is `[\"hello\", \"2025-05-01T10:20:30\"]` then the page to fetch will return all items whose name is greater than \"hello\", or whose name is \"hello\", but whose date is greater than \"2025-05-01T10:20:30\", up to a limit of `limit`. A value of `null` represents the first page.  The results are sorted according to the optional page_sort whose entries define, respectively, whether to sort ascending or descending by the given field. . [optional]
+                page_sort ([str]): A list of fields to page on and sort by, in order. Results will be sorted in order of the first item in the list, followed by second and so on.  The page to retrieve is defined in page_at_key, whose entries correspond to the previous page's values for the respective keys.  The results are sorted according to the optional page_sort whose entries define, respectively, whether to sort ascending or descending by the given field. . [optional]
+                search_direction (str): Direction which the search should go starting from the email_nullable_query parameter. . [optional] if omitted the server will use the default value of "forwards"
                 _return_http_data_only (bool): response data without head status
                     code and headers. Default is True.
                 _preload_content (bool): if False, the urllib3.HTTPResponse object
@@ -3463,11 +3467,16 @@ class ApplicationServicesApi(object):
                         'resource_id',
                         'page_at_id',
                         'name_slug',
+                        'page_on',
+                        'page_at_key',
+                        'page_sort',
+                        'search_direction',
                     ],
                     'required': [],
                     'nullable': [
                     ],
                     'enum': [
+                        'search_direction',
                     ],
                     'validation': [
                         'name',
@@ -3489,6 +3498,11 @@ class ApplicationServicesApi(object):
                         },
                     },
                     'allowed_values': {
+                        ('search_direction',): {
+
+                            "BACKWARDS": "backwards",
+                            "FORWARDS": "forwards"
+                        },
                     },
                     'openapi_types': {
                         'org_id':
@@ -3509,6 +3523,14 @@ class ApplicationServicesApi(object):
                             (str,),
                         'name_slug':
                             (str,),
+                        'page_on':
+                            ([str],),
+                        'page_at_key':
+                            ([str, none_type],),
+                        'page_sort':
+                            ([str],),
+                        'search_direction':
+                            (str,),
                     },
                     'attribute_map': {
                         'org_id': 'org_id',
@@ -3520,6 +3542,10 @@ class ApplicationServicesApi(object):
                         'resource_id': 'resource_id',
                         'page_at_id': 'page_at_id',
                         'name_slug': 'name_slug',
+                        'page_on': 'page_on',
+                        'page_at_key': 'page_at_key',
+                        'page_sort': 'page_sort',
+                        'search_direction': 'search_direction',
                     },
                     'location_map': {
                         'org_id': 'query',
@@ -3531,9 +3557,16 @@ class ApplicationServicesApi(object):
                         'resource_id': 'query',
                         'page_at_id': 'query',
                         'name_slug': 'query',
+                        'page_on': 'query',
+                        'page_at_key': 'query',
+                        'page_sort': 'query',
+                        'search_direction': 'query',
                     },
                     'collection_format_map': {
                         'org_ids': 'multi',
+                        'page_on': 'multi',
+                        'page_at_key': 'multi',
+                        'page_sort': 'multi',
                     }
                 },
                 headers_map={
@@ -3572,6 +3605,10 @@ class ApplicationServicesApi(object):
                 name_slug (str): The slug of the resource to query for. [optional]
                 desktop_type (str): The type of desktop search for.. [optional]
                 has_remote_app (bool): Only return desktops with configured remote apps. [optional]
+                page_on ([str]): A list of fields to page on and sort by, in order. Results will be sorted in order of the first item in the list, followed by second and so on.  The page to retrieve is defined in page_at_key, whose entries correspond to the previous page's values for the respective keys.  The results are sorted according to the optional page_sort whose entries define, respectively, whether to sort ascending or descending by the given field. . [optional]
+                page_at_key ([str, none_type]): The values defining the item in a collection immediately preceeding the page to fetch.  The meaning of the entries is defined in page_on. For example, if page_on is `[\"name\", \"created\"]`, and page_at_key is `[\"hello\", \"2025-05-01T10:20:30\"]` then the page to fetch will return all items whose name is greater than \"hello\", or whose name is \"hello\", but whose date is greater than \"2025-05-01T10:20:30\", up to a limit of `limit`. A value of `null` represents the first page.  The results are sorted according to the optional page_sort whose entries define, respectively, whether to sort ascending or descending by the given field. . [optional]
+                page_sort ([str]): A list of fields to page on and sort by, in order. Results will be sorted in order of the first item in the list, followed by second and so on.  The page to retrieve is defined in page_at_key, whose entries correspond to the previous page's values for the respective keys.  The results are sorted according to the optional page_sort whose entries define, respectively, whether to sort ascending or descending by the given field. . [optional]
+                search_direction (str): Direction which the search should go starting from the email_nullable_query parameter. . [optional] if omitted the server will use the default value of "forwards"
                 _return_http_data_only (bool): response data without head status
                     code and headers. Default is True.
                 _preload_content (bool): if False, the urllib3.HTTPResponse object
@@ -3643,12 +3680,17 @@ class ApplicationServicesApi(object):
                         'name_slug',
                         'desktop_type',
                         'has_remote_app',
+                        'page_on',
+                        'page_at_key',
+                        'page_sort',
+                        'search_direction',
                     ],
                     'required': [],
                     'nullable': [
                     ],
                     'enum': [
                         'desktop_type',
+                        'search_direction',
                     ],
                     'validation': [
                         'name',
@@ -3675,6 +3717,11 @@ class ApplicationServicesApi(object):
                             "RDP": "rdp",
                             "VNC": "vnc"
                         },
+                        ('search_direction',): {
+
+                            "BACKWARDS": "backwards",
+                            "FORWARDS": "forwards"
+                        },
                     },
                     'openapi_types': {
                         'org_id':
@@ -3699,6 +3746,14 @@ class ApplicationServicesApi(object):
                             (str,),
                         'has_remote_app':
                             (bool,),
+                        'page_on':
+                            ([str],),
+                        'page_at_key':
+                            ([str, none_type],),
+                        'page_sort':
+                            ([str],),
+                        'search_direction':
+                            (str,),
                     },
                     'attribute_map': {
                         'org_id': 'org_id',
@@ -3712,6 +3767,10 @@ class ApplicationServicesApi(object):
                         'name_slug': 'name_slug',
                         'desktop_type': 'desktop_type',
                         'has_remote_app': 'has_remote_app',
+                        'page_on': 'page_on',
+                        'page_at_key': 'page_at_key',
+                        'page_sort': 'page_sort',
+                        'search_direction': 'search_direction',
                     },
                     'location_map': {
                         'org_id': 'query',
@@ -3725,9 +3784,16 @@ class ApplicationServicesApi(object):
                         'name_slug': 'query',
                         'desktop_type': 'query',
                         'has_remote_app': 'query',
+                        'page_on': 'query',
+                        'page_at_key': 'query',
+                        'page_sort': 'query',
+                        'search_direction': 'query',
                     },
                     'collection_format_map': {
                         'org_ids': 'multi',
+                        'page_on': 'multi',
+                        'page_at_key': 'multi',
+                        'page_sort': 'multi',
                     }
                 },
                 headers_map={
@@ -3763,6 +3829,10 @@ class ApplicationServicesApi(object):
                 org_ids ([str]): The list of org ids to search for. Each org will be searched for independently.. [optional]
                 resource_id (str): The id of the resource to query for. [optional]
                 page_at_id (str): Pagination based query with the id as the key. To get the initial entries supply an empty string. On subsequent requests, supply the `page_at_id` field from the list response. . [optional]
+                page_on ([str]): A list of fields to page on and sort by, in order. Results will be sorted in order of the first item in the list, followed by second and so on.  The page to retrieve is defined in page_at_key, whose entries correspond to the previous page's values for the respective keys.  The results are sorted according to the optional page_sort whose entries define, respectively, whether to sort ascending or descending by the given field. . [optional]
+                page_at_key ([str, none_type]): The values defining the item in a collection immediately preceeding the page to fetch.  The meaning of the entries is defined in page_on. For example, if page_on is `[\"name\", \"created\"]`, and page_at_key is `[\"hello\", \"2025-05-01T10:20:30\"]` then the page to fetch will return all items whose name is greater than \"hello\", or whose name is \"hello\", but whose date is greater than \"2025-05-01T10:20:30\", up to a limit of `limit`. A value of `null` represents the first page.  The results are sorted according to the optional page_sort whose entries define, respectively, whether to sort ascending or descending by the given field. . [optional]
+                page_sort ([str]): A list of fields to page on and sort by, in order. Results will be sorted in order of the first item in the list, followed by second and so on.  The page to retrieve is defined in page_at_key, whose entries correspond to the previous page's values for the respective keys.  The results are sorted according to the optional page_sort whose entries define, respectively, whether to sort ascending or descending by the given field. . [optional]
+                search_direction (str): Direction which the search should go starting from the email_nullable_query parameter. . [optional] if omitted the server will use the default value of "forwards"
                 _return_http_data_only (bool): response data without head status
                     code and headers. Default is True.
                 _preload_content (bool): if False, the urllib3.HTTPResponse object
@@ -3831,11 +3901,16 @@ class ApplicationServicesApi(object):
                         'org_ids',
                         'resource_id',
                         'page_at_id',
+                        'page_on',
+                        'page_at_key',
+                        'page_sort',
+                        'search_direction',
                     ],
                     'required': [],
                     'nullable': [
                     ],
                     'enum': [
+                        'search_direction',
                     ],
                     'validation': [
                         'limit',
@@ -3850,6 +3925,11 @@ class ApplicationServicesApi(object):
                         },
                     },
                     'allowed_values': {
+                        ('search_direction',): {
+
+                            "BACKWARDS": "backwards",
+                            "FORWARDS": "forwards"
+                        },
                     },
                     'openapi_types': {
                         'org_id':
@@ -3868,6 +3948,14 @@ class ApplicationServicesApi(object):
                             (str,),
                         'page_at_id':
                             (str,),
+                        'page_on':
+                            ([str],),
+                        'page_at_key':
+                            ([str, none_type],),
+                        'page_sort':
+                            ([str],),
+                        'search_direction':
+                            (str,),
                     },
                     'attribute_map': {
                         'org_id': 'org_id',
@@ -3878,6 +3966,10 @@ class ApplicationServicesApi(object):
                         'org_ids': 'org_ids',
                         'resource_id': 'resource_id',
                         'page_at_id': 'page_at_id',
+                        'page_on': 'page_on',
+                        'page_at_key': 'page_at_key',
+                        'page_sort': 'page_sort',
+                        'search_direction': 'search_direction',
                     },
                     'location_map': {
                         'org_id': 'query',
@@ -3888,9 +3980,16 @@ class ApplicationServicesApi(object):
                         'org_ids': 'query',
                         'resource_id': 'query',
                         'page_at_id': 'query',
+                        'page_on': 'query',
+                        'page_at_key': 'query',
+                        'page_sort': 'query',
+                        'search_direction': 'query',
                     },
                     'collection_format_map': {
                         'org_ids': 'multi',
+                        'page_on': 'multi',
+                        'page_at_key': 'multi',
+                        'page_sort': 'multi',
                     }
                 },
                 headers_map={
@@ -3926,6 +4025,10 @@ class ApplicationServicesApi(object):
                 updated_since (datetime): query since updated. [optional]
                 limit (int): limit the number of rows in the response. [optional] if omitted the server will use the default value of 500
                 org_ids ([str]): The list of org ids to search for. Each org will be searched for independently.. [optional]
+                page_on ([str]): A list of fields to page on and sort by, in order. Results will be sorted in order of the first item in the list, followed by second and so on.  The page to retrieve is defined in page_at_key, whose entries correspond to the previous page's values for the respective keys.  The results are sorted according to the optional page_sort whose entries define, respectively, whether to sort ascending or descending by the given field. . [optional]
+                page_at_key ([str, none_type]): The values defining the item in a collection immediately preceeding the page to fetch.  The meaning of the entries is defined in page_on. For example, if page_on is `[\"name\", \"created\"]`, and page_at_key is `[\"hello\", \"2025-05-01T10:20:30\"]` then the page to fetch will return all items whose name is greater than \"hello\", or whose name is \"hello\", but whose date is greater than \"2025-05-01T10:20:30\", up to a limit of `limit`. A value of `null` represents the first page.  The results are sorted according to the optional page_sort whose entries define, respectively, whether to sort ascending or descending by the given field. . [optional]
+                page_sort ([str]): A list of fields to page on and sort by, in order. Results will be sorted in order of the first item in the list, followed by second and so on.  The page to retrieve is defined in page_at_key, whose entries correspond to the previous page's values for the respective keys.  The results are sorted according to the optional page_sort whose entries define, respectively, whether to sort ascending or descending by the given field. . [optional]
+                search_direction (str): Direction which the search should go starting from the email_nullable_query parameter. . [optional] if omitted the server will use the default value of "forwards"
                 _return_http_data_only (bool): response data without head status
                     code and headers. Default is True.
                 _preload_content (bool): if False, the urllib3.HTTPResponse object
@@ -3994,11 +4097,16 @@ class ApplicationServicesApi(object):
                         'updated_since',
                         'limit',
                         'org_ids',
+                        'page_on',
+                        'page_at_key',
+                        'page_sort',
+                        'search_direction',
                     ],
                     'required': [],
                     'nullable': [
                     ],
                     'enum': [
+                        'search_direction',
                     ],
                     'validation': [
                         'app_service_id',
@@ -4020,6 +4128,11 @@ class ApplicationServicesApi(object):
                         },
                     },
                     'allowed_values': {
+                        ('search_direction',): {
+
+                            "BACKWARDS": "backwards",
+                            "FORWARDS": "forwards"
+                        },
                     },
                     'openapi_types': {
                         'org_id':
@@ -4038,6 +4151,14 @@ class ApplicationServicesApi(object):
                             (int,),
                         'org_ids':
                             ([str],),
+                        'page_on':
+                            ([str],),
+                        'page_at_key':
+                            ([str, none_type],),
+                        'page_sort':
+                            ([str],),
+                        'search_direction':
+                            (str,),
                     },
                     'attribute_map': {
                         'org_id': 'org_id',
@@ -4048,6 +4169,10 @@ class ApplicationServicesApi(object):
                         'updated_since': 'updated_since',
                         'limit': 'limit',
                         'org_ids': 'org_ids',
+                        'page_on': 'page_on',
+                        'page_at_key': 'page_at_key',
+                        'page_sort': 'page_sort',
+                        'search_direction': 'search_direction',
                     },
                     'location_map': {
                         'org_id': 'query',
@@ -4058,9 +4183,16 @@ class ApplicationServicesApi(object):
                         'updated_since': 'query',
                         'limit': 'query',
                         'org_ids': 'query',
+                        'page_on': 'query',
+                        'page_at_key': 'query',
+                        'page_sort': 'query',
+                        'search_direction': 'query',
                     },
                     'collection_format_map': {
                         'org_ids': 'multi',
+                        'page_on': 'multi',
+                        'page_at_key': 'multi',
+                        'page_sort': 'multi',
                     }
                 },
                 headers_map={
@@ -4097,6 +4229,10 @@ class ApplicationServicesApi(object):
                 resource_id (str): The id of the resource to query for. [optional]
                 page_at_id (str): Pagination based query with the id as the key. To get the initial entries supply an empty string. On subsequent requests, supply the `page_at_id` field from the list response. . [optional]
                 name_slug (str): The slug of the resource to query for. [optional]
+                page_on ([str]): A list of fields to page on and sort by, in order. Results will be sorted in order of the first item in the list, followed by second and so on.  The page to retrieve is defined in page_at_key, whose entries correspond to the previous page's values for the respective keys.  The results are sorted according to the optional page_sort whose entries define, respectively, whether to sort ascending or descending by the given field. . [optional]
+                page_at_key ([str, none_type]): The values defining the item in a collection immediately preceeding the page to fetch.  The meaning of the entries is defined in page_on. For example, if page_on is `[\"name\", \"created\"]`, and page_at_key is `[\"hello\", \"2025-05-01T10:20:30\"]` then the page to fetch will return all items whose name is greater than \"hello\", or whose name is \"hello\", but whose date is greater than \"2025-05-01T10:20:30\", up to a limit of `limit`. A value of `null` represents the first page.  The results are sorted according to the optional page_sort whose entries define, respectively, whether to sort ascending or descending by the given field. . [optional]
+                page_sort ([str]): A list of fields to page on and sort by, in order. Results will be sorted in order of the first item in the list, followed by second and so on.  The page to retrieve is defined in page_at_key, whose entries correspond to the previous page's values for the respective keys.  The results are sorted according to the optional page_sort whose entries define, respectively, whether to sort ascending or descending by the given field. . [optional]
+                search_direction (str): Direction which the search should go starting from the email_nullable_query parameter. . [optional] if omitted the server will use the default value of "forwards"
                 _return_http_data_only (bool): response data without head status
                     code and headers. Default is True.
                 _preload_content (bool): if False, the urllib3.HTTPResponse object
@@ -4166,11 +4302,16 @@ class ApplicationServicesApi(object):
                         'resource_id',
                         'page_at_id',
                         'name_slug',
+                        'page_on',
+                        'page_at_key',
+                        'page_sort',
+                        'search_direction',
                     ],
                     'required': [],
                     'nullable': [
                     ],
                     'enum': [
+                        'search_direction',
                     ],
                     'validation': [
                         'name',
@@ -4192,6 +4333,11 @@ class ApplicationServicesApi(object):
                         },
                     },
                     'allowed_values': {
+                        ('search_direction',): {
+
+                            "BACKWARDS": "backwards",
+                            "FORWARDS": "forwards"
+                        },
                     },
                     'openapi_types': {
                         'org_id':
@@ -4212,6 +4358,14 @@ class ApplicationServicesApi(object):
                             (str,),
                         'name_slug':
                             (str,),
+                        'page_on':
+                            ([str],),
+                        'page_at_key':
+                            ([str, none_type],),
+                        'page_sort':
+                            ([str],),
+                        'search_direction':
+                            (str,),
                     },
                     'attribute_map': {
                         'org_id': 'org_id',
@@ -4223,6 +4377,10 @@ class ApplicationServicesApi(object):
                         'resource_id': 'resource_id',
                         'page_at_id': 'page_at_id',
                         'name_slug': 'name_slug',
+                        'page_on': 'page_on',
+                        'page_at_key': 'page_at_key',
+                        'page_sort': 'page_sort',
+                        'search_direction': 'search_direction',
                     },
                     'location_map': {
                         'org_id': 'query',
@@ -4234,9 +4392,16 @@ class ApplicationServicesApi(object):
                         'resource_id': 'query',
                         'page_at_id': 'query',
                         'name_slug': 'query',
+                        'page_on': 'query',
+                        'page_at_key': 'query',
+                        'page_sort': 'query',
+                        'search_direction': 'query',
                     },
                     'collection_format_map': {
                         'org_ids': 'multi',
+                        'page_on': 'multi',
+                        'page_at_key': 'multi',
+                        'page_sort': 'multi',
                     }
                 },
                 headers_map={

agilicus/agilicus_api/api/applications_api.py

@@ -3,7 +3,7 @@
 
     Agilicus is API-first. Modern software is controlled by other software, is open, is available for you to use the way you want, securely, simply.  The OpenAPI Specification in YAML format is available on [www](https://www.agilicus.com/www/api/agilicus-openapi.yaml) for importing to other tools.  A rendered, online viewable and usable version of this specification is available at [api](https://www.agilicus.com/api). You may try the API inline directly in the web page. To do so, first obtain an Authentication Token (the simplest way is to install the Python SDK, and then run `agilicus-cli --issuer https://MYISSUER get-token`). You will need an org-id for most calls (and can obtain from `agilicus-cli --issuer https://MYISSUER list-orgs`). The `MYISSUER` will typically be `auth.MYDOMAIN`, and you will see it as you sign-in to the administrative UI.  This API releases on Bearer-Token authentication. To obtain a valid bearer token you will need to Authenticate to an Issuer with OpenID Connect (a superset of OAUTH2).  Your \"issuer\" will look like https://auth.MYDOMAIN. For example, when you signed-up, if you said \"use my own domain name\" and assigned a CNAME of cloud.example.com, then your issuer would be https://auth.cloud.example.com.  If you selected \"use an Agilicus supplied domain name\", your issuer would look like https://auth.myorg.agilicus.cloud.  For test purposes you can use our [Python SDK](https://pypi.org/project/agilicus/) and run `agilicus-cli --issuer https://auth.MYDOMAIN get-token`.  This API may be used in any language runtime that supports OpenAPI 3.0, or, you may use our [Python SDK](https://pypi.org/project/agilicus/), our [Typescript SDK](https://www.npmjs.com/package/@agilicus/angular), or our [Golang SDK](https://git.agilicus.com/pub/sdk-go).  100% of the activities in our system our API-driven, from our web-admin, through our progressive web applications, to all internals: there is nothing that is not accessible.  For more information, see [developer resources](https://www.agilicus.com/developer).   # noqa: E501
 
-    The version of the OpenAPI document: 2025.10.23
+    The version of the OpenAPI document: 2025.10.28
     Contact: dev@agilicus.com
     Generated by: https://openapi-generator.tech
 """

agilicus/agilicus_api/api/audits_api.py

@@ -3,7 +3,7 @@
 
     Agilicus is API-first. Modern software is controlled by other software, is open, is available for you to use the way you want, securely, simply.  The OpenAPI Specification in YAML format is available on [www](https://www.agilicus.com/www/api/agilicus-openapi.yaml) for importing to other tools.  A rendered, online viewable and usable version of this specification is available at [api](https://www.agilicus.com/api). You may try the API inline directly in the web page. To do so, first obtain an Authentication Token (the simplest way is to install the Python SDK, and then run `agilicus-cli --issuer https://MYISSUER get-token`). You will need an org-id for most calls (and can obtain from `agilicus-cli --issuer https://MYISSUER list-orgs`). The `MYISSUER` will typically be `auth.MYDOMAIN`, and you will see it as you sign-in to the administrative UI.  This API releases on Bearer-Token authentication. To obtain a valid bearer token you will need to Authenticate to an Issuer with OpenID Connect (a superset of OAUTH2).  Your \"issuer\" will look like https://auth.MYDOMAIN. For example, when you signed-up, if you said \"use my own domain name\" and assigned a CNAME of cloud.example.com, then your issuer would be https://auth.cloud.example.com.  If you selected \"use an Agilicus supplied domain name\", your issuer would look like https://auth.myorg.agilicus.cloud.  For test purposes you can use our [Python SDK](https://pypi.org/project/agilicus/) and run `agilicus-cli --issuer https://auth.MYDOMAIN get-token`.  This API may be used in any language runtime that supports OpenAPI 3.0, or, you may use our [Python SDK](https://pypi.org/project/agilicus/), our [Typescript SDK](https://www.npmjs.com/package/@agilicus/angular), or our [Golang SDK](https://git.agilicus.com/pub/sdk-go).  100% of the activities in our system our API-driven, from our web-admin, through our progressive web applications, to all internals: there is nothing that is not accessible.  For more information, see [developer resources](https://www.agilicus.com/developer).   # noqa: E501
 
-    The version of the OpenAPI document: 2025.10.23
+    The version of the OpenAPI document: 2025.10.28
     Contact: dev@agilicus.com
     Generated by: https://openapi-generator.tech
 """

agilicus/agilicus_api/api/billing_api.py

@@ -3,7 +3,7 @@
 
     Agilicus is API-first. Modern software is controlled by other software, is open, is available for you to use the way you want, securely, simply.  The OpenAPI Specification in YAML format is available on [www](https://www.agilicus.com/www/api/agilicus-openapi.yaml) for importing to other tools.  A rendered, online viewable and usable version of this specification is available at [api](https://www.agilicus.com/api). You may try the API inline directly in the web page. To do so, first obtain an Authentication Token (the simplest way is to install the Python SDK, and then run `agilicus-cli --issuer https://MYISSUER get-token`). You will need an org-id for most calls (and can obtain from `agilicus-cli --issuer https://MYISSUER list-orgs`). The `MYISSUER` will typically be `auth.MYDOMAIN`, and you will see it as you sign-in to the administrative UI.  This API releases on Bearer-Token authentication. To obtain a valid bearer token you will need to Authenticate to an Issuer with OpenID Connect (a superset of OAUTH2).  Your \"issuer\" will look like https://auth.MYDOMAIN. For example, when you signed-up, if you said \"use my own domain name\" and assigned a CNAME of cloud.example.com, then your issuer would be https://auth.cloud.example.com.  If you selected \"use an Agilicus supplied domain name\", your issuer would look like https://auth.myorg.agilicus.cloud.  For test purposes you can use our [Python SDK](https://pypi.org/project/agilicus/) and run `agilicus-cli --issuer https://auth.MYDOMAIN get-token`.  This API may be used in any language runtime that supports OpenAPI 3.0, or, you may use our [Python SDK](https://pypi.org/project/agilicus/), our [Typescript SDK](https://www.npmjs.com/package/@agilicus/angular), or our [Golang SDK](https://git.agilicus.com/pub/sdk-go).  100% of the activities in our system our API-driven, from our web-admin, through our progressive web applications, to all internals: there is nothing that is not accessible.  For more information, see [developer resources](https://www.agilicus.com/developer).   # noqa: E501
 
-    The version of the OpenAPI document: 2025.10.23
+    The version of the OpenAPI document: 2025.10.28
     Contact: dev@agilicus.com
     Generated by: https://openapi-generator.tech
 """

agilicus/agilicus_api/api/catalogues_api.py

@@ -3,7 +3,7 @@
 
     Agilicus is API-first. Modern software is controlled by other software, is open, is available for you to use the way you want, securely, simply.  The OpenAPI Specification in YAML format is available on [www](https://www.agilicus.com/www/api/agilicus-openapi.yaml) for importing to other tools.  A rendered, online viewable and usable version of this specification is available at [api](https://www.agilicus.com/api). You may try the API inline directly in the web page. To do so, first obtain an Authentication Token (the simplest way is to install the Python SDK, and then run `agilicus-cli --issuer https://MYISSUER get-token`). You will need an org-id for most calls (and can obtain from `agilicus-cli --issuer https://MYISSUER list-orgs`). The `MYISSUER` will typically be `auth.MYDOMAIN`, and you will see it as you sign-in to the administrative UI.  This API releases on Bearer-Token authentication. To obtain a valid bearer token you will need to Authenticate to an Issuer with OpenID Connect (a superset of OAUTH2).  Your \"issuer\" will look like https://auth.MYDOMAIN. For example, when you signed-up, if you said \"use my own domain name\" and assigned a CNAME of cloud.example.com, then your issuer would be https://auth.cloud.example.com.  If you selected \"use an Agilicus supplied domain name\", your issuer would look like https://auth.myorg.agilicus.cloud.  For test purposes you can use our [Python SDK](https://pypi.org/project/agilicus/) and run `agilicus-cli --issuer https://auth.MYDOMAIN get-token`.  This API may be used in any language runtime that supports OpenAPI 3.0, or, you may use our [Python SDK](https://pypi.org/project/agilicus/), our [Typescript SDK](https://www.npmjs.com/package/@agilicus/angular), or our [Golang SDK](https://git.agilicus.com/pub/sdk-go).  100% of the activities in our system our API-driven, from our web-admin, through our progressive web applications, to all internals: there is nothing that is not accessible.  For more information, see [developer resources](https://www.agilicus.com/developer).   # noqa: E501
 
-    The version of the OpenAPI document: 2025.10.23
+    The version of the OpenAPI document: 2025.10.28
     Contact: dev@agilicus.com
     Generated by: https://openapi-generator.tech
 """

agilicus/agilicus_api/api/certificates_api.py

@@ -3,7 +3,7 @@
 
     Agilicus is API-first. Modern software is controlled by other software, is open, is available for you to use the way you want, securely, simply.  The OpenAPI Specification in YAML format is available on [www](https://www.agilicus.com/www/api/agilicus-openapi.yaml) for importing to other tools.  A rendered, online viewable and usable version of this specification is available at [api](https://www.agilicus.com/api). You may try the API inline directly in the web page. To do so, first obtain an Authentication Token (the simplest way is to install the Python SDK, and then run `agilicus-cli --issuer https://MYISSUER get-token`). You will need an org-id for most calls (and can obtain from `agilicus-cli --issuer https://MYISSUER list-orgs`). The `MYISSUER` will typically be `auth.MYDOMAIN`, and you will see it as you sign-in to the administrative UI.  This API releases on Bearer-Token authentication. To obtain a valid bearer token you will need to Authenticate to an Issuer with OpenID Connect (a superset of OAUTH2).  Your \"issuer\" will look like https://auth.MYDOMAIN. For example, when you signed-up, if you said \"use my own domain name\" and assigned a CNAME of cloud.example.com, then your issuer would be https://auth.cloud.example.com.  If you selected \"use an Agilicus supplied domain name\", your issuer would look like https://auth.myorg.agilicus.cloud.  For test purposes you can use our [Python SDK](https://pypi.org/project/agilicus/) and run `agilicus-cli --issuer https://auth.MYDOMAIN get-token`.  This API may be used in any language runtime that supports OpenAPI 3.0, or, you may use our [Python SDK](https://pypi.org/project/agilicus/), our [Typescript SDK](https://www.npmjs.com/package/@agilicus/angular), or our [Golang SDK](https://git.agilicus.com/pub/sdk-go).  100% of the activities in our system our API-driven, from our web-admin, through our progressive web applications, to all internals: there is nothing that is not accessible.  For more information, see [developer resources](https://www.agilicus.com/developer).   # noqa: E501
 
-    The version of the OpenAPI document: 2025.10.23
+    The version of the OpenAPI document: 2025.10.28
     Contact: dev@agilicus.com
     Generated by: https://openapi-generator.tech
 """

agilicus/agilicus_api/api/challenges_api.py

@@ -3,7 +3,7 @@
 
     Agilicus is API-first. Modern software is controlled by other software, is open, is available for you to use the way you want, securely, simply.  The OpenAPI Specification in YAML format is available on [www](https://www.agilicus.com/www/api/agilicus-openapi.yaml) for importing to other tools.  A rendered, online viewable and usable version of this specification is available at [api](https://www.agilicus.com/api). You may try the API inline directly in the web page. To do so, first obtain an Authentication Token (the simplest way is to install the Python SDK, and then run `agilicus-cli --issuer https://MYISSUER get-token`). You will need an org-id for most calls (and can obtain from `agilicus-cli --issuer https://MYISSUER list-orgs`). The `MYISSUER` will typically be `auth.MYDOMAIN`, and you will see it as you sign-in to the administrative UI.  This API releases on Bearer-Token authentication. To obtain a valid bearer token you will need to Authenticate to an Issuer with OpenID Connect (a superset of OAUTH2).  Your \"issuer\" will look like https://auth.MYDOMAIN. For example, when you signed-up, if you said \"use my own domain name\" and assigned a CNAME of cloud.example.com, then your issuer would be https://auth.cloud.example.com.  If you selected \"use an Agilicus supplied domain name\", your issuer would look like https://auth.myorg.agilicus.cloud.  For test purposes you can use our [Python SDK](https://pypi.org/project/agilicus/) and run `agilicus-cli --issuer https://auth.MYDOMAIN get-token`.  This API may be used in any language runtime that supports OpenAPI 3.0, or, you may use our [Python SDK](https://pypi.org/project/agilicus/), our [Typescript SDK](https://www.npmjs.com/package/@agilicus/angular), or our [Golang SDK](https://git.agilicus.com/pub/sdk-go).  100% of the activities in our system our API-driven, from our web-admin, through our progressive web applications, to all internals: there is nothing that is not accessible.  For more information, see [developer resources](https://www.agilicus.com/developer).   # noqa: E501
 
-    The version of the OpenAPI document: 2025.10.23
+    The version of the OpenAPI document: 2025.10.28
     Contact: dev@agilicus.com
     Generated by: https://openapi-generator.tech
 """

agilicus/agilicus_api/api/connectors_api.py

@@ -3,7 +3,7 @@
 
     Agilicus is API-first. Modern software is controlled by other software, is open, is available for you to use the way you want, securely, simply.  The OpenAPI Specification in YAML format is available on [www](https://www.agilicus.com/www/api/agilicus-openapi.yaml) for importing to other tools.  A rendered, online viewable and usable version of this specification is available at [api](https://www.agilicus.com/api). You may try the API inline directly in the web page. To do so, first obtain an Authentication Token (the simplest way is to install the Python SDK, and then run `agilicus-cli --issuer https://MYISSUER get-token`). You will need an org-id for most calls (and can obtain from `agilicus-cli --issuer https://MYISSUER list-orgs`). The `MYISSUER` will typically be `auth.MYDOMAIN`, and you will see it as you sign-in to the administrative UI.  This API releases on Bearer-Token authentication. To obtain a valid bearer token you will need to Authenticate to an Issuer with OpenID Connect (a superset of OAUTH2).  Your \"issuer\" will look like https://auth.MYDOMAIN. For example, when you signed-up, if you said \"use my own domain name\" and assigned a CNAME of cloud.example.com, then your issuer would be https://auth.cloud.example.com.  If you selected \"use an Agilicus supplied domain name\", your issuer would look like https://auth.myorg.agilicus.cloud.  For test purposes you can use our [Python SDK](https://pypi.org/project/agilicus/) and run `agilicus-cli --issuer https://auth.MYDOMAIN get-token`.  This API may be used in any language runtime that supports OpenAPI 3.0, or, you may use our [Python SDK](https://pypi.org/project/agilicus/), our [Typescript SDK](https://www.npmjs.com/package/@agilicus/angular), or our [Golang SDK](https://git.agilicus.com/pub/sdk-go).  100% of the activities in our system our API-driven, from our web-admin, through our progressive web applications, to all internals: there is nothing that is not accessible.  For more information, see [developer resources](https://www.agilicus.com/developer).   # noqa: E501
 
-    The version of the OpenAPI document: 2025.10.23
+    The version of the OpenAPI document: 2025.10.28
     Contact: dev@agilicus.com
     Generated by: https://openapi-generator.tech
 """

agilicus/agilicus_api/api/credentials_api.py

@@ -3,7 +3,7 @@
 
     Agilicus is API-first. Modern software is controlled by other software, is open, is available for you to use the way you want, securely, simply.  The OpenAPI Specification in YAML format is available on [www](https://www.agilicus.com/www/api/agilicus-openapi.yaml) for importing to other tools.  A rendered, online viewable and usable version of this specification is available at [api](https://www.agilicus.com/api). You may try the API inline directly in the web page. To do so, first obtain an Authentication Token (the simplest way is to install the Python SDK, and then run `agilicus-cli --issuer https://MYISSUER get-token`). You will need an org-id for most calls (and can obtain from `agilicus-cli --issuer https://MYISSUER list-orgs`). The `MYISSUER` will typically be `auth.MYDOMAIN`, and you will see it as you sign-in to the administrative UI.  This API releases on Bearer-Token authentication. To obtain a valid bearer token you will need to Authenticate to an Issuer with OpenID Connect (a superset of OAUTH2).  Your \"issuer\" will look like https://auth.MYDOMAIN. For example, when you signed-up, if you said \"use my own domain name\" and assigned a CNAME of cloud.example.com, then your issuer would be https://auth.cloud.example.com.  If you selected \"use an Agilicus supplied domain name\", your issuer would look like https://auth.myorg.agilicus.cloud.  For test purposes you can use our [Python SDK](https://pypi.org/project/agilicus/) and run `agilicus-cli --issuer https://auth.MYDOMAIN get-token`.  This API may be used in any language runtime that supports OpenAPI 3.0, or, you may use our [Python SDK](https://pypi.org/project/agilicus/), our [Typescript SDK](https://www.npmjs.com/package/@agilicus/angular), or our [Golang SDK](https://git.agilicus.com/pub/sdk-go).  100% of the activities in our system our API-driven, from our web-admin, through our progressive web applications, to all internals: there is nothing that is not accessible.  For more information, see [developer resources](https://www.agilicus.com/developer).   # noqa: E501
 
-    The version of the OpenAPI document: 2025.10.23
+    The version of the OpenAPI document: 2025.10.28
     Contact: dev@agilicus.com
     Generated by: https://openapi-generator.tech
 """

agilicus/agilicus_api/api/diagnostics_api.py

@@ -3,7 +3,7 @@
 
     Agilicus is API-first. Modern software is controlled by other software, is open, is available for you to use the way you want, securely, simply.  The OpenAPI Specification in YAML format is available on [www](https://www.agilicus.com/www/api/agilicus-openapi.yaml) for importing to other tools.  A rendered, online viewable and usable version of this specification is available at [api](https://www.agilicus.com/api). You may try the API inline directly in the web page. To do so, first obtain an Authentication Token (the simplest way is to install the Python SDK, and then run `agilicus-cli --issuer https://MYISSUER get-token`). You will need an org-id for most calls (and can obtain from `agilicus-cli --issuer https://MYISSUER list-orgs`). The `MYISSUER` will typically be `auth.MYDOMAIN`, and you will see it as you sign-in to the administrative UI.  This API releases on Bearer-Token authentication. To obtain a valid bearer token you will need to Authenticate to an Issuer with OpenID Connect (a superset of OAUTH2).  Your \"issuer\" will look like https://auth.MYDOMAIN. For example, when you signed-up, if you said \"use my own domain name\" and assigned a CNAME of cloud.example.com, then your issuer would be https://auth.cloud.example.com.  If you selected \"use an Agilicus supplied domain name\", your issuer would look like https://auth.myorg.agilicus.cloud.  For test purposes you can use our [Python SDK](https://pypi.org/project/agilicus/) and run `agilicus-cli --issuer https://auth.MYDOMAIN get-token`.  This API may be used in any language runtime that supports OpenAPI 3.0, or, you may use our [Python SDK](https://pypi.org/project/agilicus/), our [Typescript SDK](https://www.npmjs.com/package/@agilicus/angular), or our [Golang SDK](https://git.agilicus.com/pub/sdk-go).  100% of the activities in our system our API-driven, from our web-admin, through our progressive web applications, to all internals: there is nothing that is not accessible.  For more information, see [developer resources](https://www.agilicus.com/developer).   # noqa: E501
 
-    The version of the OpenAPI document: 2025.10.23
+    The version of the OpenAPI document: 2025.10.28
     Contact: dev@agilicus.com
     Generated by: https://openapi-generator.tech
 """

agilicus/agilicus_api/api/features_api.py

@@ -3,7 +3,7 @@
 
     Agilicus is API-first. Modern software is controlled by other software, is open, is available for you to use the way you want, securely, simply.  The OpenAPI Specification in YAML format is available on [www](https://www.agilicus.com/www/api/agilicus-openapi.yaml) for importing to other tools.  A rendered, online viewable and usable version of this specification is available at [api](https://www.agilicus.com/api). You may try the API inline directly in the web page. To do so, first obtain an Authentication Token (the simplest way is to install the Python SDK, and then run `agilicus-cli --issuer https://MYISSUER get-token`). You will need an org-id for most calls (and can obtain from `agilicus-cli --issuer https://MYISSUER list-orgs`). The `MYISSUER` will typically be `auth.MYDOMAIN`, and you will see it as you sign-in to the administrative UI.  This API releases on Bearer-Token authentication. To obtain a valid bearer token you will need to Authenticate to an Issuer with OpenID Connect (a superset of OAUTH2).  Your \"issuer\" will look like https://auth.MYDOMAIN. For example, when you signed-up, if you said \"use my own domain name\" and assigned a CNAME of cloud.example.com, then your issuer would be https://auth.cloud.example.com.  If you selected \"use an Agilicus supplied domain name\", your issuer would look like https://auth.myorg.agilicus.cloud.  For test purposes you can use our [Python SDK](https://pypi.org/project/agilicus/) and run `agilicus-cli --issuer https://auth.MYDOMAIN get-token`.  This API may be used in any language runtime that supports OpenAPI 3.0, or, you may use our [Python SDK](https://pypi.org/project/agilicus/), our [Typescript SDK](https://www.npmjs.com/package/@agilicus/angular), or our [Golang SDK](https://git.agilicus.com/pub/sdk-go).  100% of the activities in our system our API-driven, from our web-admin, through our progressive web applications, to all internals: there is nothing that is not accessible.  For more information, see [developer resources](https://www.agilicus.com/developer).   # noqa: E501
 
-    The version of the OpenAPI document: 2025.10.23
+    The version of the OpenAPI document: 2025.10.28
     Contact: dev@agilicus.com
     Generated by: https://openapi-generator.tech
 """

agilicus/agilicus_api/api/files_api.py

@@ -3,7 +3,7 @@
 
     Agilicus is API-first. Modern software is controlled by other software, is open, is available for you to use the way you want, securely, simply.  The OpenAPI Specification in YAML format is available on [www](https://www.agilicus.com/www/api/agilicus-openapi.yaml) for importing to other tools.  A rendered, online viewable and usable version of this specification is available at [api](https://www.agilicus.com/api). You may try the API inline directly in the web page. To do so, first obtain an Authentication Token (the simplest way is to install the Python SDK, and then run `agilicus-cli --issuer https://MYISSUER get-token`). You will need an org-id for most calls (and can obtain from `agilicus-cli --issuer https://MYISSUER list-orgs`). The `MYISSUER` will typically be `auth.MYDOMAIN`, and you will see it as you sign-in to the administrative UI.  This API releases on Bearer-Token authentication. To obtain a valid bearer token you will need to Authenticate to an Issuer with OpenID Connect (a superset of OAUTH2).  Your \"issuer\" will look like https://auth.MYDOMAIN. For example, when you signed-up, if you said \"use my own domain name\" and assigned a CNAME of cloud.example.com, then your issuer would be https://auth.cloud.example.com.  If you selected \"use an Agilicus supplied domain name\", your issuer would look like https://auth.myorg.agilicus.cloud.  For test purposes you can use our [Python SDK](https://pypi.org/project/agilicus/) and run `agilicus-cli --issuer https://auth.MYDOMAIN get-token`.  This API may be used in any language runtime that supports OpenAPI 3.0, or, you may use our [Python SDK](https://pypi.org/project/agilicus/), our [Typescript SDK](https://www.npmjs.com/package/@agilicus/angular), or our [Golang SDK](https://git.agilicus.com/pub/sdk-go).  100% of the activities in our system our API-driven, from our web-admin, through our progressive web applications, to all internals: there is nothing that is not accessible.  For more information, see [developer resources](https://www.agilicus.com/developer).   # noqa: E501
 
-    The version of the OpenAPI document: 2025.10.23
+    The version of the OpenAPI document: 2025.10.28
     Contact: dev@agilicus.com
     Generated by: https://openapi-generator.tech
 """