tccli 3.0.1215.1__py2.py3-none-any.whl → 3.0.1216.1__py2.py3-none-any.whl
Sign up to get free protection for your applications and to get access to all the features.
- tccli/__init__.py +1 -1
- tccli/configure.py +46 -1
- tccli/services/__init__.py +0 -3
- tccli/services/apm/v20210622/api.json +20 -0
- tccli/services/asr/v20190614/api.json +3 -3
- tccli/services/bi/v20220105/api.json +32 -4
- tccli/services/bi/v20220105/examples.json +1 -1
- tccli/services/billing/billing_client.py +53 -0
- tccli/services/billing/v20180709/api.json +304 -0
- tccli/services/billing/v20180709/examples.json +8 -0
- tccli/services/bsca/v20210811/api.json +222 -17
- tccli/services/bsca/v20210811/examples.json +4 -4
- tccli/services/ccc/ccc_client.py +53 -0
- tccli/services/ccc/v20200210/api.json +167 -18
- tccli/services/ccc/v20200210/examples.json +11 -3
- tccli/services/cdb/v20170320/api.json +13 -4
- tccli/services/cdb/v20170320/examples.json +1 -1
- tccli/services/cdn/v20180606/api.json +5 -3
- tccli/services/cdwdoris/v20211228/api.json +12 -2
- tccli/services/cfw/v20190904/api.json +81 -47
- tccli/services/cfw/v20190904/examples.json +46 -40
- tccli/services/ciam/v20220331/api.json +316 -315
- tccli/services/ciam/v20220331/examples.json +49 -49
- tccli/services/cloudaudit/cloudaudit_client.py +30 -30
- tccli/services/cloudaudit/v20190319/api.json +215 -186
- tccli/services/cloudaudit/v20190319/examples.json +13 -13
- tccli/services/cls/v20201016/api.json +365 -66
- tccli/services/cls/v20201016/examples.json +9 -3
- tccli/services/csip/v20221121/api.json +4 -4
- tccli/services/cvm/v20170312/api.json +42 -0
- tccli/services/cwp/v20180228/api.json +217 -163
- tccli/services/cwp/v20180228/examples.json +53 -65
- tccli/services/cynosdb/v20190107/api.json +77 -29
- tccli/services/cynosdb/v20190107/examples.json +22 -22
- tccli/services/dasb/v20191018/api.json +77 -0
- tccli/services/dasb/v20191018/examples.json +5 -5
- tccli/services/domain/v20180808/api.json +3 -3
- tccli/services/domain/v20180808/examples.json +3 -3
- tccli/services/eb/v20210416/api.json +15 -15
- tccli/services/eb/v20210416/examples.json +1 -1
- tccli/services/es/es_client.py +249 -37
- tccli/services/es/v20180416/api.json +521 -0
- tccli/services/es/v20180416/examples.json +32 -0
- tccli/services/ess/ess_client.py +53 -0
- tccli/services/ess/v20201111/api.json +145 -9
- tccli/services/ess/v20201111/examples.json +15 -1
- tccli/services/essbasic/essbasic_client.py +106 -0
- tccli/services/essbasic/v20210526/api.json +234 -12
- tccli/services/essbasic/v20210526/examples.json +22 -0
- tccli/services/gaap/v20180529/api.json +44 -26
- tccli/services/gaap/v20180529/examples.json +24 -30
- tccli/services/iotexplorer/v20190423/api.json +40 -0
- tccli/services/live/v20180801/api.json +35 -9
- tccli/services/mongodb/v20190725/api.json +6 -8
- tccli/services/ocr/v20181119/api.json +2 -2
- tccli/services/organization/organization_client.py +352 -34
- tccli/services/organization/v20210331/api.json +451 -0
- tccli/services/organization/v20210331/examples.json +48 -0
- tccli/services/region/v20220627/api.json +1 -1
- tccli/services/scf/scf_client.py +269 -4
- tccli/services/scf/v20180416/api.json +554 -0
- tccli/services/scf/v20180416/examples.json +46 -0
- tccli/services/ssl/v20191205/api.json +1 -1
- tccli/services/tat/v20201028/api.json +27 -25
- tccli/services/tat/v20201028/examples.json +4 -4
- tccli/services/tcss/v20201101/api.json +13 -13
- tccli/services/tcss/v20201101/examples.json +5 -5
- tccli/services/tdmq/v20200217/api.json +64 -63
- tccli/services/tdmq/v20200217/examples.json +2 -2
- tccli/services/tem/v20210701/api.json +144 -103
- tccli/services/tem/v20210701/examples.json +27 -27
- tccli/services/teo/teo_client.py +277 -12
- tccli/services/teo/v20220901/api.json +1020 -143
- tccli/services/teo/v20220901/examples.json +71 -1
- tccli/services/tke/tke_client.py +53 -0
- tccli/services/tke/v20180525/api.json +43 -0
- tccli/services/tke/v20180525/examples.json +8 -0
- tccli/services/tms/tms_client.py +4 -57
- tccli/services/tms/v20201229/api.json +0 -354
- tccli/services/tms/v20201229/examples.json +0 -8
- tccli/services/trtc/v20190722/api.json +221 -22
- tccli/services/vpc/v20170312/api.json +105 -30
- tccli/services/vpc/v20170312/examples.json +10 -2
- tccli/services/vpc/vpc_client.py +107 -54
- tccli/services/waf/v20180125/api.json +61 -0
- tccli/services/waf/v20180125/examples.json +8 -0
- tccli/services/waf/waf_client.py +53 -0
- tccli/services/wedata/v20210820/api.json +686 -0
- tccli/services/wedata/v20210820/examples.json +16 -0
- tccli/services/wedata/wedata_client.py +106 -0
- {tccli-3.0.1215.1.dist-info → tccli-3.0.1216.1.dist-info}/METADATA +6 -2
- {tccli-3.0.1215.1.dist-info → tccli-3.0.1216.1.dist-info}/RECORD +95 -99
- tccli/services/cr/__init__.py +0 -4
- tccli/services/cr/cr_client.py +0 -1626
- tccli/services/cr/v20180321/api.json +0 -2829
- tccli/services/cr/v20180321/examples.json +0 -235
- {tccli-3.0.1215.1.dist-info → tccli-3.0.1216.1.dist-info}/WHEEL +0 -0
- {tccli-3.0.1215.1.dist-info → tccli-3.0.1216.1.dist-info}/entry_points.txt +0 -0
- {tccli-3.0.1215.1.dist-info → tccli-3.0.1216.1.dist-info}/license_files/LICENSE +0 -0
@@ -71,7 +71,7 @@
|
|
71
71
|
"status": "online"
|
72
72
|
},
|
73
73
|
"ChannelCreateFlowApprovers": {
|
74
|
-
"document": "
|
74
|
+
"document": "**适用场景**:\n当通过模板或文件发起合同时,若未指定企业签署人信息,则可调用此接口动态补充签署人。同一签署人只允许补充一人,最终实际签署人取决于谁先领取合同完成签署。\n\n**接口使用说明**:\n\n1.本接口现已支持批量补充签署人\n\n2.当<a href=\"https://qian.tencent.com/developers/partnerApis/dataTypes/#fillapproverinfo/\" target=\"_blank\">补充签署人结构体</a>中指定需要补充的FlowId时,可以对指定合同补充签署人;可以指定多个相同发起方的不同合同在完成批量补充\n\n3.当<a href=\"https://qian.tencent.com/developers/partnerApis/flows/ChannelCreateFlowApprovers/\" target=\"_blank\">补充签署人接口入参</a>中指定需要补充的FlowId时,是对指定的合同补充多个指定的签署人\n\n4.如果同时指定了<a href=\"https://qian.tencent.com/developers/partnerApis/dataTypes/#fillapproverinfo/\" target=\"_blank\">补充签署人结构体</a>中的FlowId和<a href=\"https://qian.tencent.com/developers/partnerApis/flows/ChannelCreateFlowApprovers/\" target=\"_blank\">补充签署人接口入参</a>中的FlowId,仅使用<a href=\"https://qian.tencent.com/developers/partnerApis/dataTypes/#fillapproverinfo/\" target=\"_blank\">补充签署人结构体</a>中的FlowId作为补充的合同\n\n5.如果部分指定了<a href=\"https://qian.tencent.com/developers/partnerApis/dataTypes/#fillapproverinfo/\" target=\"_blank\">补充签署人结构体</a>中的FlowId,又指定了<a href=\"https://qian.tencent.com/developers/partnerApis/flows/ChannelCreateFlowApprovers/\" target=\"_blank\">补充签署人接口入参</a>中的FlowId;那么<a href=\"https://qian.tencent.com/developers/partnerApis/dataTypes/#fillapproverinfo/\" target=\"_blank\">补充签署人结构体</a>存在指定的FlowId,则使用<a href=\"https://qian.tencent.com/developers/partnerApis/dataTypes/#fillapproverinfo/\" target=\"_blank\">补充签署人结构体</a>中的FlowId,不存在则使用<a href=\"https://qian.tencent.com/developers/partnerApis/flows/ChannelCreateFlowApprovers/\" target=\"_blank\">补充签署人接口入参</a>中的FlowId作为补充的合同\n\n\n6.如果同时未指定了<a href=\"https://qian.tencent.com/developers/partnerApis/dataTypes/#fillapproverinfo/\" target=\"_blank\">补充签署人结构体</a>中的FlowId和<a href=\"https://qian.tencent.com/developers/partnerApis/flows/ChannelCreateFlowApprovers/\" target=\"_blank\">补充签署人接口入参</a>中的FlowId,则传参错误\n\n**限制条件**:\n1. 本企业(发起方企业)企业签署人仅支持通过企业名称+姓名+手机号进行补充。\n2. 个人签署人支持通过姓名+手机号进行补充,补充动态签署人时:若个人用户已完成实名,则可通过姓名+证件号码进行补充。",
|
75
75
|
"input": "ChannelCreateFlowApproversRequest",
|
76
76
|
"name": "补充签署流程签署人信息",
|
77
77
|
"output": "ChannelCreateFlowApproversResponse",
|
@@ -155,7 +155,7 @@
|
|
155
155
|
"status": "online"
|
156
156
|
},
|
157
157
|
"ChannelCreateReleaseFlow": {
|
158
|
-
"document": "发起解除协议的主要应用场景为:基于一份已经签署的合同(签署流程),进行解除操作。\n
|
158
|
+
"document": "发起解除协议的主要应用场景为:基于一份已经签署的合同(签署流程),进行解除操作。\n解除协议的模板是官方提供,经过提供法务审核,暂不支持自定义。具体用法可以参考文档[合同解除](https://qian.tencent.com/developers/partner/flow_release)。\n\n注意:\n<ul><li><code>原合同必须签署完</code>成后才能发起解除协议。</li>\n<li>只有原合同企业类型的参与人才能发起解除协议,<code>个人参与方不能发起解除协议</code>。</li>\n<li>原合同个人类型参与人必须是解除协议的参与人,<code>不能更换其他第三方个人</code>参与解除协议。</li>\n<li>如果原合同企业参与人无法参与解除协议,可以指定同企业具有同等权限的<code>企业员工代为处理</code>。</li>\n<li>发起解除协议同发起其他企业合同一样,也会参与合同<code>扣费</code>,扣费标准同其他类型合同。</li>\n<li>在解除协议签署完毕后,原合同及解除协议均变为已解除状态。</li>\n<li>非原合同企业参与人发起解除协议时,需要有<code>解除合同的权限</code>。</li>\n</ul>",
|
159
159
|
"input": "ChannelCreateReleaseFlowRequest",
|
160
160
|
"name": "发起解除协议",
|
161
161
|
"output": "ChannelCreateReleaseFlowResponse",
|
@@ -288,7 +288,7 @@
|
|
288
288
|
"status": "online"
|
289
289
|
},
|
290
290
|
"ChannelGetTaskResultApi": {
|
291
|
-
"document": "此接口(ChannelGetTaskResultApi)用来查询转换任务的状态。如需发起转换任务,请使用<a href=\"https://qian.tencent.com/developers/partnerApis/files/ChannelCreateConvertTaskApi\" target=\"_blank\">创建文件转换任务接口</a>进行资源文件的转换操作<br />\n前提条件:已调用 <a href=\"https://qian.tencent.com/developers/partnerApis/files/ChannelCreateConvertTaskApi\" target=\"_blank\">创建文件转换任务接口</a>进行文件转换,并得到了返回的转换任务Id。<br />\n\n适用场景:已创建一个文件转换任务,想查询该文件转换任务的状态,或获取转换后的文件资源
|
291
|
+
"document": "此接口(ChannelGetTaskResultApi)用来查询转换任务的状态。如需发起转换任务,请使用<a href=\"https://qian.tencent.com/developers/partnerApis/files/ChannelCreateConvertTaskApi\" target=\"_blank\">创建文件转换任务接口</a>进行资源文件的转换操作<br />\n前提条件:已调用 <a href=\"https://qian.tencent.com/developers/partnerApis/files/ChannelCreateConvertTaskApi\" target=\"_blank\">创建文件转换任务接口</a>进行文件转换,并得到了返回的转换任务Id。<br />\n\n适用场景:已创建一个文件转换任务,想查询该文件转换任务的状态,或获取转换后的文件资源ID。<br />\n注:\n1. `大文件转换所需的时间可能会比较长。`\n2. `本接口返回的文件资源ID就是PDF资源ID,可以直接用于【用PDF文件创建签署流程】接口发起合同。`",
|
292
292
|
"input": "ChannelGetTaskResultApiRequest",
|
293
293
|
"name": "查询转换任务状态",
|
294
294
|
"output": "ChannelGetTaskResultApiResponse",
|
@@ -357,6 +357,13 @@
|
|
357
357
|
"output": "CreateChannelSubOrganizationActiveResponse",
|
358
358
|
"status": "online"
|
359
359
|
},
|
360
|
+
"CreateCloseOrganizationUrl": {
|
361
|
+
"document": "创建企业注销链接\n\n系统将返回操作链接。贵方需要主动联系并通知企业的超级管理员(超管)或法人。由他们点击该链接,完成企业的注销操作。\n\n注意: `在调用此接口以管理企业扩展服务时,操作者( Agent.ProxyOperator.OpenId)必须是企业的超级管理员(超管)或法人。`",
|
362
|
+
"input": "CreateCloseOrganizationUrlRequest",
|
363
|
+
"name": "创建企业注销链接",
|
364
|
+
"output": "CreateCloseOrganizationUrlResponse",
|
365
|
+
"status": "online"
|
366
|
+
},
|
360
367
|
"CreateConsoleLoginUrl": {
|
361
368
|
"document": "此接口(CreateConsoleLoginUrl)用于创建第三方平台子客企业控制台Web/移动登录链接。支持web控制台、电子签小程序和H5链接。登录链接是进入子客web企业控制台的唯一入口。\n\nWeb链接访问后,会根据子客企业(**Agent中ProxyOrganizationOpenId表示**)和员工(**Agent中OpenId表示**)的状态,进入不同的流程,主要情况分类如下:\n<table>\n<thead>\n<tr>\n<th>子客企业状态</th>\n<th>子客企业员工状态</th>\n<th>点击链接进入的流程</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>企业未激活</td>\n<td>员工未认证</td>\n<td>进入企业激活流程,首次完成企业激活流程的员工会成为超管</td>\n</tr>\n<tr>\n<td>企业已激活</td>\n<td>员工未认证</td>\n<td>进入员工认证并加入企业流程</td>\n</tr>\n<tr>\n<td>企业已激活</td>\n<td>员工已认证</td>\n<td>进入子客企业Web控制台</td>\n</tr>\n</tbody>\n</table>\n如果是企业激活流程,需要注意如下情况:\n\n1. 若在激活过程中,**更换用户OpenID重新生成链接,之前的认证会被清理**。因此不要在企业认证过程生成多个链接给多人同时操作,会导致认证过程互相影响。\n2. 若您认证中发现信息有误需要重新认证,**可通过更换用户OpenID重新生成链接的方式,来清理掉已有的流程**。\n\n系统的渠道企业, 应用, 子客企业, 子客员工的组织形式\n![image](https://qcloudimg.tencent-cloud.cn/raw/77677faeea26c9d7f37474597c81fe01.png)\n\n\n<font color=\"red\">相关视频指引</font> <br>\n1. <a href=\"https://dyn.ess.tencent.cn/guide/apivideo/essbasic-createconsoleloginin.mp4\" target=\"_blank\">【生成子客登录链接】代码编写 & 子企业认证示例</a><br>",
|
362
369
|
"input": "CreateConsoleLoginUrlRequest",
|
@@ -427,6 +434,13 @@
|
|
427
434
|
"output": "CreateSignUrlsResponse",
|
428
435
|
"status": "online"
|
429
436
|
},
|
437
|
+
"DeleteOrganizationAuthorizations": {
|
438
|
+
"document": "批量清理未认证的企业认证流程。\n\n此接口用来清除企业方认证信息填写错误,批量清理认证中的认证流信息。\n为接口[提交子企业批量认证链接创建任务](https://qian.tencent.com/developers/partnerApis/accounts/CreateBatchOrganizationRegistrationTasks) 和[查询子企业批量认证链接](https://qian.tencent.com/developers/partnerApis/accounts/DescribeBatchOrganizationRegistrationUrls) 接口的扩展接口。即在批量认证过程中,当发起认证企业发现超管信息错误的时候,可以将当前超管下的所有认证流企业清除。\n\n注意:\n**这个接口的操作人必须跟生成批量认证链接接口的应用号一致,才可以调用,否则会返回当前操作人没有认证中的企业认证流**",
|
439
|
+
"input": "DeleteOrganizationAuthorizationsRequest",
|
440
|
+
"name": "批量清除未认证的企业认证流",
|
441
|
+
"output": "DeleteOrganizationAuthorizationsResponse",
|
442
|
+
"status": "online"
|
443
|
+
},
|
430
444
|
"DescribeBatchOrganizationRegistrationUrls": {
|
431
445
|
"document": "此接口用于获取企业批量认证异步任务的状态及结果。需要先调用接口<a href=\"https://qian.tencent.com/developers/partnerApis/accounts/CreateBatchOrganizationRegistrationTasks\" target=\"_blank\">提交子企业批量认证链接创建任务</a>获取到任务ID,然后再调用此接口获取到各个子企业的注册认证链接。整体流程如下图。\n![image](https://qcloudimg.tencent-cloud.cn/raw/654aa2a72ab7d42f06464ea33c50c3bb.png)\n\n\n注:\n`异步任务的处理完成时间视当前已提交的任务量、任务的复杂程度等因素决定,正常情况下 3~5 秒即可完成,但也可能需要更长的时间`",
|
432
446
|
"input": "DescribeBatchOrganizationRegistrationUrlsRequest",
|
@@ -484,7 +498,7 @@
|
|
484
498
|
"status": "online"
|
485
499
|
},
|
486
500
|
"DescribeResourceUrlsByFlows": {
|
487
|
-
"document": "获取合同流程PDF
|
501
|
+
"document": "获取合同流程PDF的下载链接,可以下载签署中、签署完的此子企业创建的合同。\n\n\n\n\n### 1. 确保合同的PDF已经合成后,再调用本接口。\n 用户创建合同或者提交签署动作后,后台需要1~3秒的时间就进行合同PDF合成或者签名,为了确保您下载的是签署完成的完整合同文件,我们建议采取下面两种方式的一种来<font color=\"red\"><b>确保PDF已经合成完成,然后在调用本接口</b></font>。\n\n**第一种**:请确保您的系统配置了[接收合同完成通知的回调](https://qian.tencent.com/developers/partner/callback_types_contracts_sign)功能。一旦所有参与方签署完毕,我们的系统将自动向您提供的回调地址发送完成通知。\n**第二种**:通过调用我们的[获取合同信息](https://qian.tencent.com/developers/partnerApis/flows/DescribeFlowDetailInfo)接口来主动检查合同的签署状态。请仅在确认合同状态为“全部签署完成”后,进行文件的下载操作。\n\n### 2. 有两种开通下载权限的途径。\n\n**第一种**: 需第三方应用的子企业登录控制台进行授权, 授权在**企业中心**的**授权管理**区域, 界面如下图。\n授权过程需要**子企业超管**扫描跳转到电子签小程序签署<<渠道端下载渠道子客合同功能授权委托书>>\n\n![image](https://qcloudimg.tencent-cloud.cn/raw/8b483dfebdeafac85051279406944048.png)\n\n**第二种**: 渠道方企业在**企业应用管理**的配置界面打开需要配置的应用,点击**应用扩展服务**开通此功能,需要**渠道方企业的超管**扫描二维码跳转到电子签小程序签署 <<渠道端下载渠道子客合同功能开通知情同意书>>\n注: \n1. `请注意如果第三方应用的子客主动关闭了渠道端下载渠道子客合同功能开关,那么渠道方开通了此功能也无法下载子客的合同文件`\n![image](https://qcloudimg.tencent-cloud.cn/raw/238979ef51dd381ccbdbc755a593debc/channel_DescribeResourceUrlsByFlows_appilications2.png)",
|
488
502
|
"input": "DescribeResourceUrlsByFlowsRequest",
|
489
503
|
"name": "获取合同PDF下载链接",
|
490
504
|
"output": "DescribeResourceUrlsByFlowsResponse",
|
@@ -711,7 +725,7 @@
|
|
711
725
|
},
|
712
726
|
{
|
713
727
|
"disabled": false,
|
714
|
-
"document": "签署人信息补充类型,默认无需补充。\n\n<ul><li> **1** :
|
728
|
+
"document": "签署人信息补充类型,默认无需补充。\n\n<ul><li> **1** : 动态签署人(可发起合同后再补充签署人信息)注:`企业自动签不支持动态补充`</li></ul>\n\n注:\n`使用动态签署人能力前,需登陆腾讯电子签控制台打开服务开关`",
|
715
729
|
"example": "无",
|
716
730
|
"member": "int64",
|
717
731
|
"name": "FillType",
|
@@ -2142,7 +2156,7 @@
|
|
2142
2156
|
},
|
2143
2157
|
{
|
2144
2158
|
"disabled": false,
|
2145
|
-
"document": "合同流程ID,为32位字符串。 建议开发者妥善保存此流程ID
|
2159
|
+
"document": "合同流程ID,为32位字符串。 \n- 建议开发者妥善保存此流程ID,以便于顺利进行后续操作。\n- 可登录腾讯电子签控制台,在 \"合同\"->\"合同中心\" 中查看某个合同的FlowId(在页面中展示为合同ID)。\n- <font color=\"red\">不建议继续使用</font>,请使用<a href=\"https://qian.tencent.com/developers/partnerApis/dataTypes/#fillapproverinfo/\" target=\"_blank\">补充签署人结构体</a>中的FlowId指定合同",
|
2146
2160
|
"example": "无",
|
2147
2161
|
"member": "string",
|
2148
2162
|
"name": "FlowId",
|
@@ -6376,6 +6390,93 @@
|
|
6376
6390
|
],
|
6377
6391
|
"type": "object"
|
6378
6392
|
},
|
6393
|
+
"CreateCloseOrganizationUrlRequest": {
|
6394
|
+
"document": "CreateCloseOrganizationUrl请求参数结构体",
|
6395
|
+
"members": [
|
6396
|
+
{
|
6397
|
+
"disabled": false,
|
6398
|
+
"document": "应用相关信息。 此接口Agent.ProxyOrganizationOpenId、Agent. ProxyOperator.OpenId、Agent.AppId 必填。",
|
6399
|
+
"example": "无",
|
6400
|
+
"member": "Agent",
|
6401
|
+
"name": "Agent",
|
6402
|
+
"required": true,
|
6403
|
+
"type": "object"
|
6404
|
+
}
|
6405
|
+
],
|
6406
|
+
"type": "object"
|
6407
|
+
},
|
6408
|
+
"CreateCloseOrganizationUrlResponse": {
|
6409
|
+
"document": "CreateCloseOrganizationUrl返回参数结构体",
|
6410
|
+
"members": [
|
6411
|
+
{
|
6412
|
+
"disabled": false,
|
6413
|
+
"document": "链接有效期,unix时间戳,精确到秒",
|
6414
|
+
"example": "1730257357",
|
6415
|
+
"member": "int64",
|
6416
|
+
"name": "ExpiredOn",
|
6417
|
+
"output_required": true,
|
6418
|
+
"type": "int",
|
6419
|
+
"value_allowed_null": false
|
6420
|
+
},
|
6421
|
+
{
|
6422
|
+
"disabled": false,
|
6423
|
+
"document": "H5跳转到电子签小程序链接, 一般用于发送短信中带的链接, 打开后进入腾讯电子签小程序",
|
6424
|
+
"example": "https://res.ess.tencent.cn/cdn/h5-activity/jump-mp.html?to=ENTERPRISE_LOGOUT_LANDING&shortKey=yDCkuUW35EQA3r0aqr88",
|
6425
|
+
"member": "string",
|
6426
|
+
"name": "LongUrl",
|
6427
|
+
"output_required": true,
|
6428
|
+
"type": "string",
|
6429
|
+
"value_allowed_null": false
|
6430
|
+
},
|
6431
|
+
{
|
6432
|
+
"disabled": false,
|
6433
|
+
"document": "H5跳转到电子签小程序链接的短链形式, 一般用于发送短信中带的链接, 打开后进入腾讯电子签小程序",
|
6434
|
+
"example": "https:/essurl.cn/ppiKUBJLt0",
|
6435
|
+
"member": "string",
|
6436
|
+
"name": "ShortUrl",
|
6437
|
+
"output_required": true,
|
6438
|
+
"type": "string",
|
6439
|
+
"value_allowed_null": false
|
6440
|
+
},
|
6441
|
+
{
|
6442
|
+
"disabled": false,
|
6443
|
+
"document": "APP或小程序跳转电子签小程序链接, 一般用于客户小程序或者APP跳转过来, 打开后进入腾讯电子签小程序",
|
6444
|
+
"example": "pages/guide/index?to=ENTERPRISE_LOGOUT_LANDING&shortKey=yDCkuUW35EQA3r0aqr88",
|
6445
|
+
"member": "string",
|
6446
|
+
"name": "MiniAppPath",
|
6447
|
+
"output_required": true,
|
6448
|
+
"type": "string",
|
6449
|
+
"value_allowed_null": false
|
6450
|
+
},
|
6451
|
+
{
|
6452
|
+
"disabled": false,
|
6453
|
+
"document": "二维码链接",
|
6454
|
+
"example": "https://dyn.ess.tencent.cn/imgs/qrcode_urls/enterprise_logout_landing/yDCkxUUckp495fo9Ua9wie1hisAGTzhI.png",
|
6455
|
+
"member": "string",
|
6456
|
+
"name": "QrcodeUrl",
|
6457
|
+
"output_required": true,
|
6458
|
+
"type": "string",
|
6459
|
+
"value_allowed_null": false
|
6460
|
+
},
|
6461
|
+
{
|
6462
|
+
"disabled": false,
|
6463
|
+
"document": "直接跳转至电子签小程序的二维码链接,无需通过中转页。您需要自行将其转换为二维码,使用微信扫码后可直接进入。请注意,直接点击链接是无效的。",
|
6464
|
+
"example": "https://res.ess.tencent.cn/mp-gate/release/ENTERPRISE_LOGOUT_LANDING?shortKey=yDCkuUW35EQA3r0aqr82",
|
6465
|
+
"member": "string",
|
6466
|
+
"name": "WeixinQrcodeUrl",
|
6467
|
+
"output_required": true,
|
6468
|
+
"type": "string",
|
6469
|
+
"value_allowed_null": false
|
6470
|
+
},
|
6471
|
+
{
|
6472
|
+
"document": "唯一请求 ID,由服务端生成,每次请求都会返回(若请求因其他原因未能抵达服务端,则该次请求不会获得 RequestId)。定位问题时需要提供该次请求的 RequestId。",
|
6473
|
+
"member": "string",
|
6474
|
+
"name": "RequestId",
|
6475
|
+
"type": "string"
|
6476
|
+
}
|
6477
|
+
],
|
6478
|
+
"type": "object"
|
6479
|
+
},
|
6379
6480
|
"CreateConsoleLoginUrlRequest": {
|
6380
6481
|
"document": "CreateConsoleLoginUrl请求参数结构体",
|
6381
6482
|
"members": [
|
@@ -6516,7 +6617,7 @@
|
|
6516
6617
|
},
|
6517
6618
|
{
|
6518
6619
|
"disabled": false,
|
6519
|
-
"document": "
|
6620
|
+
"document": "是否自动激活子客企业,有下面两种选项:\n\n**false(默认设置)**:不自动激活子客户。您需要通过控制台或调用[激活或者续期子企业](https://qian.tencent.com/developers/partnerApis/accounts/CreateChannelSubOrganizationActive)接口手动完成激活过程。\n\n**true**:若持有的许可证充足,子客户企业注册完成后将自动激活,无需手动操作或访问控制台。\n\n<b>注</b>:如果<b>应用扩展服务</b>中的<b>自动激活子客企业</b>为打开态, 则忽略本接口的AutoActive这个参数(若持有的许可证充足,子客户企业注册完成后将自动激活),具体位置参考下图:\n![image](https://qcloudimg.tencent-cloud.cn/raw/c3639b05503d3735bac483d17aa6b0a3.png)",
|
6520
6621
|
"example": "无",
|
6521
6622
|
"member": "bool",
|
6522
6623
|
"name": "AutoActive",
|
@@ -7365,7 +7466,7 @@
|
|
7365
7466
|
},
|
7366
7467
|
{
|
7367
7468
|
"disabled": false,
|
7368
|
-
"document": "合同流程ID数组,最多支持100个。\n注:
|
7469
|
+
"document": "合同流程ID数组,最多支持100个。\n\n注: \n1. 必须选择提供此参数或合同组编号中的一个。\n2. 当生成类型(GenerateType)设为“ALL”时,不可提供多个流程ID。",
|
7369
7470
|
"example": "[\"yDwFmUUckpstqfvzUE1h3jo1f3cqjkGm\"]",
|
7370
7471
|
"member": "string",
|
7371
7472
|
"name": "FlowIds",
|
@@ -7392,7 +7493,7 @@
|
|
7392
7493
|
},
|
7393
7494
|
{
|
7394
7495
|
"disabled": false,
|
7395
|
-
"document": "签署链接生成类型,可以选择的类型如下\n\n<ul><li
|
7496
|
+
"document": "签署链接生成类型,可以选择的类型如下\n\n<ul><li><strong>ALL</strong>:(默认)为所有签署方生成签署链接,但不包括自动签署(静默签署)的签署方。注意:<strong>此中类型不支持多个合同ID(FlowIds)</strong>。</li>\n<li><strong>CHANNEL</strong>:适用于第三方子企业的员工签署方。</li>\n<li><strong>NOT_CHANNEL</strong>:适用于SaaS平台企业的员工签署方。</li>\n<li><strong>PERSON</strong>:适用于个人或自然人签署方。</li>\n<li><strong>FOLLOWER</strong>:适用于关注方,目前指合同的抄送方。</li>\n<li><strong>RECIPIENT</strong>:根据RecipientId生成对应的签署链接,适用于动态添加签署人的情况。</li></ul>",
|
7396
7497
|
"example": "CHANNEL",
|
7397
7498
|
"member": "string",
|
7398
7499
|
"name": "GenerateType",
|
@@ -7401,7 +7502,7 @@
|
|
7401
7502
|
},
|
7402
7503
|
{
|
7403
7504
|
"disabled": false,
|
7404
|
-
"document": "SaaS
|
7505
|
+
"document": "SaaS平台企业员工签署方的企业名称如果名称中包含英文括号(),请使用中文括号()代替。 注: `1.GenerateType为\"NOT_CHANNEL\"时必填` `2.获取B端动态签署人领取链接时,可指定此字段来预先设定签署人的企业,预设后只能以该企业身份去领取合同并完成签署`",
|
7405
7506
|
"example": "典子谦示例企业",
|
7406
7507
|
"member": "string",
|
7407
7508
|
"name": "OrganizationName",
|
@@ -7551,6 +7652,117 @@
|
|
7551
7652
|
],
|
7552
7653
|
"type": "object"
|
7553
7654
|
},
|
7655
|
+
"DeleteOrganizationAuthorizationInfo": {
|
7656
|
+
"document": "清理的企业认证流信息",
|
7657
|
+
"members": [
|
7658
|
+
{
|
7659
|
+
"disabled": false,
|
7660
|
+
"document": "认证流 Id 是指在企业认证过程中,当前操作人的认证流程的唯一标识。每个企业在认证过程中只能有一条认证流认证成功。这意味着在同一认证过程内,一个企业只能有一个认证流程处于成功状态,以确保认证的唯一性和有效性。\t",
|
7661
|
+
"example": "yDCHHUUckpbdaiqbUxJVsHWy99WG6kTY",
|
7662
|
+
"member": "string",
|
7663
|
+
"name": "AuthorizationId",
|
7664
|
+
"output_required": false,
|
7665
|
+
"type": "string",
|
7666
|
+
"value_allowed_null": false
|
7667
|
+
},
|
7668
|
+
{
|
7669
|
+
"disabled": false,
|
7670
|
+
"document": "认证的企业名称\t",
|
7671
|
+
"example": "典子谦示例企业\t",
|
7672
|
+
"member": "string",
|
7673
|
+
"name": "OrganizationName",
|
7674
|
+
"output_required": false,
|
7675
|
+
"type": "string",
|
7676
|
+
"value_allowed_null": false
|
7677
|
+
},
|
7678
|
+
{
|
7679
|
+
"disabled": false,
|
7680
|
+
"document": "第三方平台子客企业的唯一标识,定义Agent中的ProxyOrganizationOpenId一样, 可以参考<a href=\"https://qian.tencent.com/developers/partnerApis/dataTypes/#agent\" target=\"_blank\">Agent结构体</a>",
|
7681
|
+
"example": "org_dianziqian",
|
7682
|
+
"member": "string",
|
7683
|
+
"name": "OrganizationOpenId",
|
7684
|
+
"output_required": false,
|
7685
|
+
"type": "string",
|
7686
|
+
"value_allowed_null": false
|
7687
|
+
},
|
7688
|
+
{
|
7689
|
+
"disabled": false,
|
7690
|
+
"document": "清除认证流产生的错误信息",
|
7691
|
+
"example": "无",
|
7692
|
+
"member": "string",
|
7693
|
+
"name": "Errormessage",
|
7694
|
+
"output_required": false,
|
7695
|
+
"type": "string",
|
7696
|
+
"value_allowed_null": false
|
7697
|
+
}
|
7698
|
+
],
|
7699
|
+
"usage": "out"
|
7700
|
+
},
|
7701
|
+
"DeleteOrganizationAuthorizationsRequest": {
|
7702
|
+
"document": "DeleteOrganizationAuthorizations请求参数结构体",
|
7703
|
+
"members": [
|
7704
|
+
{
|
7705
|
+
"disabled": false,
|
7706
|
+
"document": "关于渠道应用的相关信息,包括渠道应用标识、第三方平台子客企业标识及第三方平台子客企业中的员工标识等内容,您可以参阅开发者中心所提供的 Agent 结构体以获取详细定义。\n\n此接口下面信息必填。\n<ul>\n<li>渠道应用标识: Agent.AppId</li>\n</ul>\n",
|
7707
|
+
"example": "无",
|
7708
|
+
"member": "Agent",
|
7709
|
+
"name": "Agent",
|
7710
|
+
"required": true,
|
7711
|
+
"type": "object"
|
7712
|
+
},
|
7713
|
+
{
|
7714
|
+
"disabled": false,
|
7715
|
+
"document": "认证人姓名,组织机构超管姓名。 在注册流程中,必须是超管本人进行操作。 ",
|
7716
|
+
"example": "张三",
|
7717
|
+
"member": "string",
|
7718
|
+
"name": "AdminName",
|
7719
|
+
"required": false,
|
7720
|
+
"type": "string"
|
7721
|
+
},
|
7722
|
+
{
|
7723
|
+
"disabled": false,
|
7724
|
+
"document": "认证人手机号,组织机构超管手机号。 在注册流程中,必须是超管本人进行操作。 ",
|
7725
|
+
"example": "18888888888",
|
7726
|
+
"member": "string",
|
7727
|
+
"name": "AdminMobile",
|
7728
|
+
"required": false,
|
7729
|
+
"type": "string"
|
7730
|
+
}
|
7731
|
+
],
|
7732
|
+
"type": "object"
|
7733
|
+
},
|
7734
|
+
"DeleteOrganizationAuthorizationsResponse": {
|
7735
|
+
"document": "DeleteOrganizationAuthorizations返回参数结构体",
|
7736
|
+
"members": [
|
7737
|
+
{
|
7738
|
+
"disabled": false,
|
7739
|
+
"document": "清理认证流的详细信息,包括企业名称、认证流唯一 ID 以及清理认证流过程中产生的错误信息。",
|
7740
|
+
"example": "无",
|
7741
|
+
"member": "DeleteOrganizationAuthorizationInfo",
|
7742
|
+
"name": "DeleteOrganizationAuthorizationInfos",
|
7743
|
+
"output_required": false,
|
7744
|
+
"type": "list",
|
7745
|
+
"value_allowed_null": false
|
7746
|
+
},
|
7747
|
+
{
|
7748
|
+
"disabled": false,
|
7749
|
+
"document": "批量清理认证流返回的状态值其中包括- 1 全部成功- 2 部分成功- 3 全部失败",
|
7750
|
+
"example": "1",
|
7751
|
+
"member": "uint64",
|
7752
|
+
"name": "Status",
|
7753
|
+
"output_required": false,
|
7754
|
+
"type": "int",
|
7755
|
+
"value_allowed_null": false
|
7756
|
+
},
|
7757
|
+
{
|
7758
|
+
"document": "唯一请求 ID,由服务端生成,每次请求都会返回(若请求因其他原因未能抵达服务端,则该次请求不会获得 RequestId)。定位问题时需要提供该次请求的 RequestId。",
|
7759
|
+
"member": "string",
|
7760
|
+
"name": "RequestId",
|
7761
|
+
"type": "string"
|
7762
|
+
}
|
7763
|
+
],
|
7764
|
+
"type": "object"
|
7765
|
+
},
|
7554
7766
|
"Department": {
|
7555
7767
|
"document": "第三方应用集成员工部门信息",
|
7556
7768
|
"members": [
|
@@ -8711,7 +8923,7 @@
|
|
8711
8923
|
},
|
8712
8924
|
{
|
8713
8925
|
"disabled": false,
|
8714
|
-
"document": "合同流程ID
|
8926
|
+
"document": "合同流程ID\n- 补充合同组子合同动态签署人时必传。\n- 补充正常合同,请阅读:<a href=\"https://qian.tencent.com/developers/partnerApis/flows/ChannelCreateFlowApprovers/\" target=\"_blank\">补充签署人接口</a>接口使用说明",
|
8715
8927
|
"example": "yDwFmUUckpstqfvzUE1h3jo1f3cqjkGm",
|
8716
8928
|
"member": "string",
|
8717
8929
|
"name": "FlowId",
|
@@ -8743,6 +8955,16 @@
|
|
8743
8955
|
"output_required": false,
|
8744
8956
|
"type": "string",
|
8745
8957
|
"value_allowed_null": true
|
8958
|
+
},
|
8959
|
+
{
|
8960
|
+
"disabled": false,
|
8961
|
+
"document": "合同流程ID,为32位字符串。\t\n注意:此字段可能返回 null,表示取不到有效值。",
|
8962
|
+
"example": "无",
|
8963
|
+
"member": "string",
|
8964
|
+
"name": "FlowId",
|
8965
|
+
"output_required": false,
|
8966
|
+
"type": "string",
|
8967
|
+
"value_allowed_null": true
|
8746
8968
|
}
|
8747
8969
|
],
|
8748
8970
|
"usage": "out"
|
@@ -11527,7 +11749,7 @@
|
|
11527
11749
|
},
|
11528
11750
|
{
|
11529
11751
|
"disabled": false,
|
11530
|
-
"document": "参与方在合同中的角色是按照创建合同的时候来排序的,解除协议默认会将第一个参与人叫`甲方`,第二个叫`乙方`, 第三个叫`丙方`,以此类推。\n如果需改动此参与人的角色名字,可用此字段指定,由汉字,英文字符,数字组成,最大20
|
11752
|
+
"document": "参与方在合同中的角色是按照创建合同的时候来排序的,解除协议默认会将第一个参与人叫`甲方`,第二个叫`乙方`, 第三个叫`丙方`,以此类推。\n如果需改动此参与人的角色名字,可用此字段指定,由汉字,英文字符,数字组成,最大20个字。\n\n![image](https://qcloudimg.tencent-cloud.cn/raw/973a820ab66d1ce57082c160c2b2d44a.png)",
|
11531
11753
|
"example": "供应商",
|
11532
11754
|
"member": "string",
|
11533
11755
|
"name": "ApproverSignRole",
|
@@ -810,6 +810,14 @@
|
|
810
810
|
"title": "子客激活"
|
811
811
|
}
|
812
812
|
],
|
813
|
+
"CreateCloseOrganizationUrl": [
|
814
|
+
{
|
815
|
+
"document": "",
|
816
|
+
"input": "POST / HTTP/1.1\nHost: essbasic.tencentcloudapi.com\nContent-Type: application/json\nX-TC-Action: CreateCloseOrganizationUrl\n<公共请求参数>\n\n{\n \"Agent\": {\n \"ProxyOperator\": {\n \"OpenId\": \"n9527\"\n },\n \"ProxyOrganizationOpenId\": \"org_dianziqian\",\n \"AppId\": \"yDRSRUUgygj6qnwfUuO4zjEwc193c2hH\"\n }\n}",
|
817
|
+
"output": "{\n \"Response\": {\n \"ExpiredOn\": 1730257357,\n \"LongUrl\": \"https://res.ess.tencent.cn/cdn/h5-activity-dev/jump-mp.html?to=ENTERPRISE_LOGOUT_LANDING&shortKey=yDCkuUW35EQA3r0aqr88\",\n \"MiniAppPath\": \"pages/guide/index?to=ENTERPRISE_LOGOUT_LANDING&shortKey=yDCkuUW35EQA3r0aqr88\",\n \"QrcodeUrl\": \"https://dyn.ess.tencent.cn/imgs/qrcode_urls/enterprise_logout_landing/yDCkxUUckp495fo9Ua9wie1hisAGTzhI.png\",\n \"RequestId\": \"s1729652557401395967\",\n \"ShortUrl\": \"https://essurl.cn/ppiKUBJLt0\",\n \"WeixinQrcodeUrl\": \"https://res.ess.tencent.cn/mp-gate/develop/ENTERPRISE_LOGOUT_LANDING?shortKey=yDCkuUW35EQA3r0aqr88\"\n }\n}",
|
818
|
+
"title": "创建企业注销链接"
|
819
|
+
}
|
820
|
+
],
|
813
821
|
"CreateConsoleLoginUrl": [
|
814
822
|
{
|
815
823
|
"document": "如果<b>典子谦示例企业的员工张三已经完成了认证和加入企业</b>, 此时给典子谦示例企业的员工张三生成登录的PC控制台的链接\n\n典子谦示例企业的定义标识为:org_dianziqian\n员工张三定义员工标识为:n9527\n",
|
@@ -984,6 +992,20 @@
|
|
984
992
|
"input": "POST / HTTP/1.1\nHost: essbasic.tencentcloudapi.com\nContent-Type: application/json\nX-TC-Action: CreateSignUrls\n<公共请求参数>\n\n{\n \"Agent\": {\n \"AppId\": \"yDwhxUUckp3gl8j5UuFX33LSNozpRsbi\",\n \"ProxyOrganizationOpenId\": \"org_dianziqian\",\n \"ProxyOperator\": {\n \"OpenId\": \"n9527\"\n },\n \"ProxyAppId\": \"\"\n },\n \"FlowIds\": [\n \"yDwiBUUckpo27hh3UuLiduR83BEL3kSb\"\n ],\n \"Endpoint\": \"WEIXINAPP\",\n \"GenerateType\": \"PERSON\",\n \"Name\": \"张三\",\n \"Mobile\": \"18888888888\",\n \"IdCardType\": \"ID_CARD\",\n \"IdCardNumber\": \"620000198802020000\"\n}",
|
985
993
|
"output": "{\n \"Response\": {\n \"SignUrlInfos\": [\n {\n \"SignUrl\": \"https://essurl.cn/9oJ**P\",\n \"Deadline\": 0,\n \"SignOrder\": 0,\n \"SignId\": \"\",\n \"CustomUserId\": \"\",\n \"Name\": \"\",\n \"Mobile\": \"\",\n \"OrganizationName\": \"\",\n \"ApproverType\": \"\",\n \"IdCardNumber\": \"\",\n \"FlowId\": \"yDwiBUUckpo27hh3UuLiduR83BEL3kSb\",\n \"OpenId\": \"\",\n \"FlowGroupId\": \"\",\n \"SignQrcodeUrl\": \"\"\n }\n ],\n \"ErrorMessages\": [],\n \"RequestId\": \"0ec76ecb**bde91\"\n }\n}",
|
986
994
|
"title": "指定证件信息,为个人/自然人生成签署链接"
|
995
|
+
},
|
996
|
+
{
|
997
|
+
"document": "获取动态签署人补充链接,创建合同时未指定具体签署人,可获取链接后推送给指定的人进行补充,预设了企业名称后进入领取链接只能以该企业身份去领取并签署合同\n注: \n`1.参数GenerateType需传值为RECIPIENT` \n`2.需指定对应的签署方角色编号(即RecipientId)` ",
|
998
|
+
"input": "POST / HTTP/1.1\nHost: essbasic.tencentcloudapi.com\nContent-Type: application/json\nX-TC-Action: CreateSignUrls\n<公共请求参数>\n\n{\n \"FlowIds\": [\n \"yDwhGUUfe5g******CX8ZwTiSg8gISocy\"\n ],\n \"RecipientIds\": [\n \"yDwJDUUckpkv98zbUEF1GNmv6ln4ga9W\"\n ],\n \"OrganizationName\": \"典子谦有限公司\",\n \"GenerateType\": \"RECIPIENT\",\n \"Agent\": {\n \"ProxyOrganizationOpenId\": \"1000***8062\",\n \"ProxyOperator\": {\n \"OpenId\": \"yDR3L****eTdCt5TVx\"\n },\n \"AppId\": \"125***319\"\n },\n \"Endpoint\": \"\"\n}",
|
999
|
+
"output": "{\n \"Response\": {\n \"ErrorMessages\": [],\n \"RequestId\": \"s1696937862717144539\",\n \"SignUrlInfos\": [\n {\n \"ApproverType\": \"\",\n \"CustomUserId\": \"\",\n \"Deadline\": 0,\n \"FlowGroupId\": \"\",\n \"FlowId\": \"yDwhGUUfe5g******CX8ZwTiSg8gISocy\",\n \"IdCardNumber\": \"\",\n \"Mobile\": \"\",\n \"Name\": \"\",\n \"OpenId\": \"\",\n \"OrganizationName\": \"\",\n \"SignId\": \"\",\n \"SignOrder\": 0,\n \"SignQrcodeUrl\": \"https://file.test.ess.tencent.cn/bresource/resource/resource/0/0.JPG?hkey=5d92f0db15e6bbba6aea641f64c5c06dcbe2797f**************69ee4e24cd976dd8376dbd41c6ff227c803c4c561c\",\n \"SignUrl\": \"https://test.essurl.cn/gGI***nZC\"\n }\n ]\n }\n}",
|
1000
|
+
"title": "获取动态签署人补充链接, 并且预设企业名称"
|
1001
|
+
}
|
1002
|
+
],
|
1003
|
+
"DeleteOrganizationAuthorizations": [
|
1004
|
+
{
|
1005
|
+
"document": "1. 企业典子谦示例企业 通过生成批量认证接口生成了 两个认证企业 (张三示例企业一, 张三示例企业二)\n2. 此时操作人典子谦示例企业 的业务员典子谦 发现超管应该是李四,信息填写错误,希望批量清除之前写错的信息,进行重新认证。\n3. 此时传递超管的姓名和手机号, 来进行清理。\n4. 全部清理成功,status 返回为 1",
|
1006
|
+
"input": "POST / HTTP/1.1\nHost: essbasic.tencentcloudapi.com\nContent-Type: application/json\nX-TC-Action: DeleteOrganizationAuthorizations\n<公共请求参数>\n\n{\n \"Agent\": {\n \"AppId\": \"yDwhxUUckp3gl8j5UuFX33LSNozpRsbi\",\n \"ProxyOrganizationOpenId\": \"org_dianziqian\",\n \"ProxyOperator\": {\n \"OpenId\": \"n9527\"\n }\n },\n \"AdminName\": \"张三\",\n \"AdminMobile\": \"18888888888\"\n}",
|
1007
|
+
"output": "{\n \"Response\": {\n \"DeleteOrganizationAuthorizationInfos\": [\n {\n \"AuthorizationId\": \"yDCkRUUckp4mdtwzUuvjSCCEzIZPsM4A\",\n \"OrganizationName\": \"张三示例企业一\",\n \"OrganizationOpenId\": \"org_zhangsan_1\"\n },\n {\n \"AuthorizationId\": \"yDCkRUUckp4mdw8eUuYnzJiiRO2w2jQI\",\n \"OrganizationName\": \"张三示例企业一\",\n \"OrganizationOpenId\": \"org_zhangsan_2\"\n }\n ],\n \"RequestId\": \"37e81c99bc4e\",\n \"Status\": 1\n }\n}",
|
1008
|
+
"title": "批量清理张三的所有认证中的认证流"
|
987
1009
|
}
|
988
1010
|
],
|
989
1011
|
"DescribeBatchOrganizationRegistrationUrls": [
|