在Docusign API上线时出错 [英] Error when going live on Docusign API

问题描述

在沙盒中进行开发之后，我们使我们的api密钥获得批准并提升为真实帐户。

After developing in the sandbox, we got our api key approved and promoted to a live account.

从那时起，我们一直得到以下答复-

Since then we've been getting the following response -

响应：{
errorCode： ACCOUNT_LACKS_PERMISSIONS，
message：此帐户缺少足够的权限。
}
http代码：401
执行于：2017-05-17 15:03:59

response: { "errorCode": "ACCOUNT_LACKS_PERMISSIONS", "message": "This Account lacks sufficient permissions." } http code: 401 exeucted at: 2017-05-17 15:03:59

根据我的研究和根据创建信封时的ACCOUNT_LACKS_PERMISSIONS错误

需要在Docusign的后端切换设置。用户提到-

A setting needs to be switched on the backend at Docusign. The user mentions -

他们在限制器附近的API部分将名为In Session的设置更改为Enabled，只有帐户管理器或第2层支持可以更改。一切都很好。

"They changed a setting called In Session to Enabled in API section near limiter that only the account manager or tier 2 support can change. All is well."

帐户ID为30953035
API用户名bcbffa28-a316-473e-b2b7-48d964d909a7
以下是API请求。在模拟账户下，这个工作很好。我什至升级到了Intermediate API，希望它能解决我的问题，但不会带来麻烦。

The account ID is 30953035 API username bcbffa28-a316-473e-b2b7-48d964d909a7 The API request is below. This was working just fine under a Demo account. I've even upgraded to the Intermediate API in the hopes that it will resolve my issues but no dice.

支持人员说我需要在此处发布...

Support says that I need to post here...

推荐答案

这是由于请求中使用了错误的帐户 baseUrl 引起的。当您的集成对给定用户执行身份验证时，如果您使用的是传统身份验证（ X-DocuSign-Authentication 标头），则需要指向以下/ login_information端点作为实时系统：

This is caused by a bad account baseUrl that's being used in the request. When your integration performs authentication for a given user, if you are using Legacy auth (X-DocuSign-Authentication header) then you need to point to the following /login_information endpoint for the live system:

https://www.docusign.net/restapi/v2/login_information

获得响应后，您需要解析返回的 baseUrl 值并将该子域用于后续的API请求。 （请注意，实时系统中有多个子域，例如NA1，NA2，EU等）

When you get the response you then need to parse the baseUrl value that was returned and use that sub-domain for subsequent API requests. (Note that there are multiple sub-domains in the live system such as NA1, NA2, EU, etc)

baseUrl 类似于：

https://na2.docusign.net/restapi/v2/accounts/12345/envelopes

请确保将代码配置为读取该子域并在后续请求中使用，否则，例如，如果您仅使用 www ，您将无法找到正确的帐户端点，并且会收到帐户缺少权限错误。

Make sure you configure your code to read this sub-domain and use in subsequent requests, otherwise you if you simply use www for instance you will not be hitting the correct account endpoint and you'll receive the "Account lacks permissions" error you're receiving.

这篇关于在Docusign API上线时出错的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！