Open Bank Project
|
OBP v4.0.0 zh (267 APIs)
API Host: https://openlab.openbankproject.com
BankAccountsViewsCounterpartiesTransactions获取API信息(根)返回有关以下内容的信息:
Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv4.0.0 by root
获取API配置返回有关以下内容的信息:
Typical Successful Response:
Headers:
Required Roles:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by config
获取JSON Web密钥(JWK)获取服务器的公共JSON Web密钥(JWK)集和证书链。 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by getServerJWK
获取JSON Web密钥(JWK)URI获取OAuth2服务器的公共JSON Web密钥(JWK)URI。 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by getOAuth2ServerJWKsURIs
获取当前通话的通话上下文获取当前通话的通话上下文。 身份验证是强制性的 Typical Successful Response:
Headers:
Required Roles:
Possible Errors:
Connector Methods:
Implemented in OBPv4.0.0 by getCallContext
获取连接器状态(环回)该端点调用连接器以检查后端传输(例如Kafka)是否可以到达。 当前,这仅适用于基于Kafka的连接器。 对于基于Kafka的连接器,此端点将消息写入Kafka并再次读取。 将来,此端点还可能返回有关数据库连接等的信息。 身份验证是强制性的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by getObpConnectorLoopback
获取适配器信息获取有关适配器的基本信息。 身份验证是强制性的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by getAdapterInfo
获取速率限制信息获取有关此OBP实例上的速率限制设置的信息,例如: 速率限制已启用并处于活动状态吗? 身份验证是强制性的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by getRateLimitingInfo
获取银行的适配器信息获取有关代表该银行进行监听的适配器的基本信息。 身份验证是强制性的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.0.0 by getAdapterInfoForBank
创建ATM为银行创建ATM。 身份验证是强制性的 Typical Successful Response:
Headers:
Required Roles:
Possible Errors:
Connector Methods:
Implemented in OBPv3.0.0 by createAtm
获取银行ATMS返回有关BANK_ID指定的单个银行的ATM的信息,包括:
分页: 默认情况下,返回100条记录。 您可以使用url查询参数limit和offset进行分页 身份验证是可选的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.0.0 by getAtms
获取银行自动柜员机返回由BANK_ID和ATM_ID指定的单个银行的有关ATM的信息,包括:
身份验证是可选的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.0.0 by getAtm
创建帐号在BANK_ID指定的银行和ACCOUNT_ID指定的ID处创建帐户。 用户可以为自己创建一个帐户-或-在POST正文中指定了USER_ID的用户。 如果指定了PUT体USER_ID 时 ,登录的用户必须具有角色canCreateAccount。创建帐户后,该帐户将归USER_ID指定的用户所有。 如果未指定PUT主体USER_ID,则该帐户将由登录的用户拥有。 “ product_code”字段应为Product的product_code。 注意:金额必须为零。 Typical Successful Response:
Headers:
Required Roles:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by createAccount
创建帐户属性创建帐户属性 帐户属性用于描述带有键入的键值对列表的金融产品。 每个帐户属性都通过ACCOUNT_ID链接到其帐户 典型的帐户属性可能是: ISIN(用于国际债券) 发行日期(债券在市场上发行时) 有关更多示例,请参见FPML 。 类型字段必须是“ STRING”,“ INTEGER”,“ DOUBLE”或DATE_WITH_DAY”之一 身份验证是强制性的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by createAccountAttribute
创建帐户(POST)在BANK_ID指定的银行创建帐户。 用户可以为自己创建一个帐户-或-在POST正文中指定了USER_ID的用户。 如果指定了POST体USER_ID 时 ,登录的用户必须具有角色CanCreateAccount。创建帐户后,该帐户将归USER_ID指定的用户所有。 如果未指定POST正文USER_ID,则该帐户将由登录的用户拥有。 “ product_code”字段应为Product的product_code。 注意:金额必须为零。 Typical Successful Response:
Headers:
Required Roles:
Possible Errors:
Connector Methods:
Implemented in OBPv4.0.0 by addAccount
在所有银行(私人)获取帐户映射(类型->字符串) Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.0.0 by corePrivateAccountsAllBanks
在银行获取Firehose帐户获取为其分配了firehose视图的帐户。 该端点允许批量访问帐户。 需要CanUseFirehoseAtAnyBank角色 要显示在列表中,每个帐户必须链接有一个流水视图。 firehose视图的is_firehose = true 对于VIEW_ID,请尝试“所有者” 身份验证是强制性的 Typical Successful Response:
Headers:
Required Roles:
Possible Errors:
Connector Methods:
Implemented in OBPv3.0.0 by getFirehoseAccountsAtOneBank
在银行获取帐户。返回用户有权访问的BANK_ID帐户列表。 可选的请求参数:
整个网址示例: 身份验证是强制性的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv2.0.0 by getPrivateAccountsAtOneBank
在银行获取帐户(仅ID)。仅返回用户有权访问的BANK_ID上的帐户ID列表。 每个帐户必须至少有一个私有视图。 对于每个帐户,API都会返回其帐户ID。 如果要在视图上查看更多信息,请使用“帐户详细信息”调用。 可选的请求参数:
整个网址示例: 身份验证是强制性的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.0.0 by getPrivateAccountIdsbyBankId
在银行获取帐户(最低)。映射(类型->字符串) Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.0.0 by privateAccountsAtOneBank
按ID获取帐户(完整)映射(类型->字符串) Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv4.0.0 by getPrivateAccountByIdFull
按ID获取帐户(核心)映射(类型->字符串) Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv4.0.0 by getCoreAccountById
更新帐户属性更新帐户属性 帐户属性用于描述带有键入的键值对列表的金融产品。 每个帐户属性都通过ACCOUNT_ID链接到其帐户 典型的帐户属性可能是: ISIN(用于国际债券) 发行日期(债券在市场上发行时) 有关更多示例,请参见FPML 。 身份验证是强制性的 Typical Successful Response:
Headers:
Required Roles:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by updateAccountAttribute
更新帐户标签。更新帐户标签。标签是帐户所有者如何知道帐户的方式,例如“我的储蓄帐户” 身份验证是强制性的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv1.2.1 by updateAccountLabel
更新账户。更新帐户。 身份验证是强制性的 Typical Successful Response:
Headers:
Required Roles:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by updateAccount
查看可用资金查看可用资金
Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by checkFundsAvailable
获取帐户余额在一家银行获取当前用户帐户的余额。 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by getBankAccountsBalances
获取持有的帐户如果尚未为该用户分配所有者视图,则获取当前用户拥有的帐户。 可用于将帐户加入API-因为所有其他帐户和交易端点都需要分配视图。 可选的请求参数:
整个网址示例: 身份验证是强制性的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.0.0 by getAccountsHeld
获取支票簿订单注意:此端点当前仅返回示例数据。 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by getCheckbookOrders
创建账户申请创建账户申请 身份验证是强制性的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by createAccountApplication
更新帐户申请状态更新帐户申请状态 身份验证是强制性的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by updateAccountApplicationStatus
获取帐户申请获取帐户申请。 身份验证是强制性的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by getAccountApplications
通过ID获取帐户申请获取帐户申请。 身份验证是强制性的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by getAccountApplication
删除帐户标签。Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv4.0.0 by deleteTagForViewOnAccount
在帐户上添加标签。Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv4.0.0 by addTagForViewOnAccount
获取帐户标签。返回在视图 (VIEW_ID)上创建的帐户ACCOUNT_ID标签。 由于标签与用户链接,因此需要进行身份验证。 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv4.0.0 by getTagsForViewOnAccount
在所有银行获取公共帐户。在所有银行获得公共帐户(匿名访问)。 身份验证是可选的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv2.0.0 by publicAccountsAllBanks
在银行获取公共帐户返回位于BANK_ID的公共帐户(匿名访问)列表。对于每个帐户,API都会返回ID和可用的视图。 身份验证是可选的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv2.0.0 by publicAccountsAtOneBank
通过ID获取公共帐户返回有关具有公开视图的帐户的信息。 该帐户由ACCOUNT_ID指定。该信息由VIEW_ID指定的视图审核。
PSD2上下文:PSD2要求客户可以通过第三方应用程序访问其帐户信息。 身份验证是可选的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.0.0 by getPublicAccountById
取得银行获取由BANK_ID指定的银行
Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.0.0 by bankById
建立银行创建一个新的银行(授权访问)。 Typical Successful Response:
Headers:
Required Roles:
Possible Errors:
Connector Methods:
Implemented in OBPv4.0.0 by createBank
映射(类型->字符串)映射(类型->字符串) Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv2.0.0 by getTransactionTypes
映射(类型->字符串)映射(类型->字符串) Typical Successful Response:
Headers:
Required Roles:
Possible Errors:
Connector Methods:
Implemented in OBPv2.1.0 by createTransactionType
获取银行获取此API实例上的银行
Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv4.0.0 by getBanks
创建分支为银行创建分行。 身份验证是强制性的 Typical Successful Response:
Headers:
Required Roles:
Possible Errors:
Connector Methods:
Implemented in OBPv3.0.0 by createBranch
删除分支从给定的银行中删除分行。 身份验证是强制性的 Typical Successful Response:
Headers:
Required Roles:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by deleteBranch
获取分支返回有关由BANK_ID和BRANCH_ID指定的单个Branch的信息,包括:
身份验证是可选的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.0.0 by getBranch
获取银行分行返回有关BANK_ID指定的单个银行的分支机构的信息,包括:
分页: 默认情况下,返回50条记录。 您可以使用url查询参数limit和offset进行分页
注意:在仪表内部,nearLatitude和nearLongitude都为空或都具有值。 身份验证是可选的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.0.0 by getBranches
创建卡映射(类型->字符串) Typical Successful Response:
Headers:
Required Roles:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by addCardForBank
创建卡属性创建卡属性 卡属性用于描述带有键入的键值对列表的金融产品。 每个卡属性都通过CARD_ID链接到其卡 类型字段必须是“ STRING”,“ INTEGER”,“ DOUBLE”或DATE_WITH_DAY”之一 身份验证是强制性的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by createCardAttribute
删除卡在CARD_ID指定的银行删除卡。 身份验证是强制性的 Typical Successful Response:
Headers:
Required Roles:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by deleteCardForBank
更新卡映射(类型->字符串) Typical Successful Response:
Headers:
Required Roles:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by updatedCardForBank
更新卡属性更新卡属性 卡属性用于描述带有键入的键值对列表的金融产品。 每个卡属性都通过CARD_ID链接到其卡 身份验证是强制性的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by updateCardAttribute
获取信用卡订单状态注意:此端点当前仅返回示例数据。 获取所有订单 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by getStatusOfCreditCardOrder
获取当前用户的卡片映射(类型->字符串) Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv1.3.0 by getCards
获取指定银行的卡映射(类型->字符串) Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by getCardsForBank
通过ID获取卡映射(类型->字符串) Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by getCardForBank
取得同意OBP同意书允许同意书持有人呼叫一个或多个端点。 必须使用SCA(严格的客户身份验证)来创建和授权同意书。 也就是说,可以由授权用户通过OBP REST API创建同意书,但是必须通过带外(OOB)机制(例如发送到手机的代码)进行确认。 每个同意书都具有以下状态之一:初始化,接受,拒绝,撤回,已接收,有效,撤回BYPSU,已过期,终止DBP。 该端点获取当前用户创建的同意。 身份验证是强制性的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by getConsents
回答同意挑战OBP同意书允许同意书持有人呼叫一个或多个端点。 必须使用SCA(严格的客户身份验证)来创建和授权同意书。 也就是说,可以由授权用户通过OBP REST API创建同意书,但是必须通过带外(OOB)机制(例如发送到手机的代码)进行确认。 每个同意书都具有以下状态之一:初始化,接受,拒绝,撤回,已接收,有效,撤回BYPSU,已过期,终止DBP。 该端点用于确认先前创建的同意。 用户必须提供例如通过SMS带外(OOB)发送的代码。 身份验证是强制性的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by answerConsentChallenge
建立同意书(EMAIL)OBP同意书允许同意书持有人呼叫一个或多个端点。 必须使用SCA(严格的客户身份验证)来创建和授权同意书。 也就是说,可以由授权用户通过OBP REST API创建同意书,但是必须通过带外(OOB)机制(例如发送到手机的代码)进行确认。 每个同意书都具有以下状态之一:初始化,接受,拒绝,撤回,已接收,有效,撤回BYPSU,已过期,终止DBP。 该端点开始创建同意的过程。 同意是在INITIATED状态下创建的。 通过SCA_METHOD中定义的传输,将一次性密码(OTP)(又称为安全性挑战)发送给用户(OOB) 创建同意书后,OBP(或后端系统)将存储挑战,以便稍后可以根据用户通过“回答同意书挑战”端点提供的值进行检查。 身份验证是强制性的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by createConsentEmail
建立同意书(SMS)OBP同意书允许同意书持有人呼叫一个或多个端点。 必须使用SCA(严格的客户身份验证)来创建和授权同意书。 也就是说,可以由授权用户通过OBP REST API创建同意书,但是必须通过带外(OOB)机制(例如发送到手机的代码)进行确认。 每个同意书都具有以下状态之一:初始化,接受,拒绝,撤回,已接收,有效,撤回BYPSU,已过期,终止DBP。 该端点开始创建同意的过程。 同意是在INITIATED状态下创建的。 通过SCA_METHOD中定义的传输,将一次性密码(OTP)(又称为安全性挑战)发送给用户(OOB) 创建同意书后,OBP(或后端系统)将存储挑战,以便稍后可以根据用户通过“回答同意书挑战”端点提供的值进行检查。 身份验证是强制性的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by createConsentSms
撤销同意OBP同意书允许同意书持有人呼叫一个或多个端点。 必须使用SCA(严格的客户身份验证)来创建和授权同意书。 也就是说,可以由授权用户通过OBP REST API创建同意书,但是必须通过带外(OOB)机制(例如发送到手机的代码)进行确认。 每个同意书都具有以下状态之一:初始化,接受,拒绝,撤回,已接收,有效,撤回BYPSU,已过期,终止DBP。 撤销由CONSENT_ID指定的当前用户的同意书 身份验证是强制性的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by revokeConsent
启用或禁用消费者启用/禁用由CONSUMER_ID指定的使用者。 Typical Successful Response:
Headers:
Required Roles:
Possible Errors:
Connector Methods:
Implemented in OBPv2.1.0 by enableDisableConsumers
吸引消费者映射(类型->字符串) Typical Successful Response:
Headers:
Required Roles:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by getConsumer
吸引消费者映射(类型->字符串) Typical Successful Response:
Headers:
Required Roles:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by getConsumers
吸引消费者(登录用户)映射(类型->字符串) Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by getConsumersForCurrentUser
更新使用者RedirectUrl映射(类型->字符串) Typical Successful Response:
Headers:
Required Roles:
Possible Errors:
Connector Methods:
Implemented in OBPv2.1.0 by updateConsumerRedirectUrl
获取消费者的通话限制获取每个消费者的通话限制。 Typical Successful Response:
Headers:
Required Roles:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by getCallsLimit
设置消费者的通话限制设置使用者的API调用限制: 每秒 身份验证是强制性的 Typical Successful Response:
Headers:
Required Roles:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by callsLimit
创建交易对手(明确)映射(类型->字符串) Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv2.2.0 by createCounterparty
获取一个帐户的其他帐户。返回有关所有其他帐户的数据,这些帐户已经与ACCOUNT_ID共享了至少一个交易,且帐户为BANK_ID。 如果视图VIEW_ID不公开,则需要进行身份验证。 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.0.0 by getOtherAccountsForBankAccount
获取对方(明确)。映射(类型->字符串) Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv2.2.0 by getExplictCounterpartiesForAccount
通过ID获取其他帐户。返回有关“其他帐户”的数据,该“其他帐户”已通过BANK_ID与ACCOUNT_ID共享了至少一笔交易。 如果视图不是公共的,则需要认证。 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.0.0 by getOtherAccountByIdForBankAccount
通过交易对手ID(明确)获取交易对手。映射(类型->字符串) Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv2.2.0 by getExplictCounterpartyById
创建其他帐户专用别名为其他帐户OTHER_ACCOUNT_ID创建一个专用别名。 身份验证是可选的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv1.2.1 by addOtherAccountPrivateAlias
删除交易对手私人别名删除其他帐户OTHER_ACCOUNT_ID的私人别名。 身份验证是可选的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv1.2.1 by deleteCounterpartyPrivateAlias
删除其他银行帐户的更多信息。Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv1.2.1 by deleteCounterpartyMoreInfo
删除其他银行帐户的网址。Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv1.2.1 by deleteCounterpartyUrl
删除对方公共别名删除另一个帐户OTHER_ACCOUNT_ID的公共别名。 身份验证是可选的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv1.2.1 by deleteCounterpartyPublicAlias
删除对方公司位置。删除其他银行帐户的公司位置。删除交易对手注册地址的地理位置 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv1.2.1 by deleteCounterpartyCorporateLocation
删除对方图片网址删除其他银行帐户的图片网址。 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv1.2.1 by deleteCounterpartyImageUrl
删除对方开放公司网址删除其他银行帐户的打开的公司网址。 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv1.2.1 by deleteCounterpartyOpenCorporatesUrl
删除对方的物理位置。删除其他银行帐户的实际位置。 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv1.2.1 by deleteCounterpartyPhysicalLocation
将公共别名添加到其他银行帐户。为其他帐户OTHER_ACCOUNT_ID创建公用别名。 身份验证是可选的 注意:将为新的“其他帐户/交易对手”自动生成公共别名,因此仅在以下情况下使用此调用: VIEW_ID参数应该是允许调用者访问的视图,并且有权创建公共别名。 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv1.2.1 by addCounterpartyPublicAlias
将公司位置添加到交易对手添加交易对手注册地址的地理位置 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv1.2.1 by addCounterpartyCorporateLocation
将图片网址添加到其他银行帐户。添加指向交易对手徽标的网址 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv1.2.1 by addCounterpartyImageUrl
将实际位置添加到其他银行帐户。添加交易对手主要位置的地理坐标 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv1.2.1 by addCounterpartyPhysicalLocation
将开放公司网址添加到交易对手将打开的公司网址添加到其他银行帐户。 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv1.2.1 by addCounterpartyOpenCorporatesUrl
将网址添加到其他银行帐户。代表交易对手的网址(首页网址等) Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv1.2.1 by addCounterpartyUrl
更新交易对手公司位置更新交易对手注册地址的地理位置 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv1.2.1 by updateCounterpartyCorporateLocation
更新交易对手图片网址更新指向交易对手徽标的网址 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv1.2.1 by updateCounterpartyImageUrl
更新交易对手更多信息从帐户的角度(例如,我的牙医)更新对方的更多信息描述。 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv1.2.1 by updateCounterpartyMoreInfo
更新交易对手的公开公司网址更新其他银行帐户的未清公司网址。 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv1.2.1 by updateCounterpartyOpenCorporatesUrl
更新交易对手的实际位置更新交易对手主要地点的地理坐标 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv1.2.1 by updateCounterpartyPhysicalLocation
更新交易对手私人别名更新交易对手(又称其他帐户)的私有别名OTHER_ACCOUNT_ID。 身份验证是可选的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv1.2.1 by updateCounterpartyPrivateAlias
更新其他银行帐户的公共别名。更新其他帐户/交易对手OTHER_ACCOUNT_ID的公共别名。 身份验证是可选的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv1.2.1 by updateCounterpartyPublicAlias
更新其他银行帐户的网址。代表交易对手的网址(首页网址等) Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv1.2.1 by updateCounterpartyUrl
添加交易对手更多信息从帐户的角度(例如,我的牙医)添加对对方的描述。 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv1.2.1 by addCounterpartyMoreInfo
获取其他帐户专用别名返回另一个帐户OTHER_ACCOUNT_ID的私有别名。 身份验证是可选的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv1.2.1 by getOtherAccountPrivateAlias
获取其他帐户元数据。获取另一个帐户的元数据。 如果视图不是公开的,则需要通过OAuth进行身份验证。 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv1.2.1 by getOtherAccountMetadata
获取其他银行帐户的公共别名。返回其他帐户OTHER_ACCOUNT_ID的公共别名。 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv1.2.1 by getCounterpartyPublicAlias
为客户增加税收居住向CUSTOMER_ID指定的客户添加税收住所。 身份验证是强制性的 Typical Successful Response:
Headers:
Required Roles:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by createTaxResidence
创建信用额度订单请求注意:此端点当前仅返回示例数据。 创建信用额度订单请求 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by createCreditLimitRequest
创建客户。客户资源存储客户编号,法定姓名,电子邮件,电话号码,他们的出生日期,关系状态,学历,个人资料图片的网址,KYC状态等。 身份验证是强制性的 Typical Successful Response:
Headers:
Required Roles:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by createCustomer
创建用户客户链接。将用户链接到客户 身份验证是强制性的 必须具有CanCreateUserCustomerLink或CanCreateUserCustomerLinkAtAnyBank权利。 Typical Successful Response:
Headers:
Required Roles:
Possible Errors:
Connector Methods:
Implemented in OBPv2.0.0 by createUserCustomerLinks
删除客户地址删除由CUSTOMER_ADDRESS_ID指定的客户地址。 身份验证是强制性的 Typical Successful Response:
Headers:
Required Roles:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by deleteCustomerAddress
删除税收居民删除由TAX_RESIDENCE_ID指定的客户的税收居所。 身份验证是强制性的 Typical Successful Response:
Headers:
Possible Errors:
Connector Methods:
Implemented in OBPv3.1.0 by deleteTaxResidence
|