Mixing
Docusign TSP API
up vote
3
down vote
favorite
I have applied for the Docusign TSP Program.
We are following these instructions but we are facing some issues.
https://developers.docusign.com/id-tsp-api/guides/tsp-authentication
When we invoke the following route:
POST /oauth/token
POST oauth/token HTTP/1.1
Host: account-d.docusign.com
Content-Type: application/x-www-form-urlencoded
Authorization: Basic Y2xpZW50SWQ6Y2xpZW50U2VjcmV0
grant_type=authorization_code
&code=SplxlOBeZQQYbYS6WxSbIA
&redirect_uri=https%3A%2F%2Fclient.example.org%2Fcb
This should be the response that we are expecting:
HTTP/1.1 200 OK
Content-Type: application/json
Cache-Control: no-store
Pragma: no-cache
{
"access_token": "(access token example removed for document brevity)",
"expires_in": 28800,
"token_type": "Bearer",
"user_api": "https://{server}.docusign.net"
}
Unfortunately we aren't receiving "user_api", instead we are receiving this:
{
"access_token": "ISSUED_ACCESS_TOKEN",
"token_type": "Bearer",
"refresh_token": "ISSUED_REFRESH_TOKEN",
"expires_in": 28800
}
Are you able to help me?
docusignapi docusign
asked 2 days ago
TSP CMS
161
New contributor
TSP CMS is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
3
down vote
favorite
I have applied for the Docusign TSP Program.
We are following these instructions but we are facing some issues.
https://developers.docusign.com/id-tsp-api/guides/tsp-authentication
When we invoke the following route:
POST /oauth/token
POST oauth/token HTTP/1.1
Host: account-d.docusign.com
Content-Type: application/x-www-form-urlencoded
Authorization: Basic Y2xpZW50SWQ6Y2xpZW50U2VjcmV0
grant_type=authorization_code
&code=SplxlOBeZQQYbYS6WxSbIA
&redirect_uri=https%3A%2F%2Fclient.example.org%2Fcb
This should be the response that we are expecting:
HTTP/1.1 200 OK
Content-Type: application/json
Cache-Control: no-store
Pragma: no-cache
{
"access_token": "(access token example removed for document brevity)",
"expires_in": 28800,
"token_type": "Bearer",
"user_api": "https://{server}.docusign.net"
}
Unfortunately we aren't receiving "user_api", instead we are receiving this:
{
"access_token": "ISSUED_ACCESS_TOKEN",
"token_type": "Bearer",
"refresh_token": "ISSUED_REFRESH_TOKEN",
"expires_in": 28800
}
Are you able to help me?
docusignapi docusign
asked 2 days ago
TSP CMS
161
New contributor
TSP CMS is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Not sure why you're not getting theuser_apikey but another way you may be able to get it is withhttps://www.docusign.net/restapi/v2/login_information, that responses with abase_uri. Could be that it's the same value since it's tied to the user's account.
– JM-AGMS
2 days ago
Hi, I guess that api won't help me, TSP API expects something like /restapi/{version}/signature/ as the base path and this route gives me /restapi/{version}/accounts/{account_id}, which is the base path for the eSignature API. By the way, I should receive that TSP API base route path through the access token request, in the user_api field.
– TSP CMS
20 hours ago
add a comment |
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I have applied for the Docusign TSP Program.
We are following these instructions but we are facing some issues.
https://developers.docusign.com/id-tsp-api/guides/tsp-authentication
When we invoke the following route:
POST /oauth/token
POST oauth/token HTTP/1.1
Host: account-d.docusign.com
Content-Type: application/x-www-form-urlencoded
Authorization: Basic Y2xpZW50SWQ6Y2xpZW50U2VjcmV0
grant_type=authorization_code
&code=SplxlOBeZQQYbYS6WxSbIA
&redirect_uri=https%3A%2F%2Fclient.example.org%2Fcb
This should be the response that we are expecting:
HTTP/1.1 200 OK
Content-Type: application/json
Cache-Control: no-store
Pragma: no-cache
{
"access_token": "(access token example removed for document brevity)",
"expires_in": 28800,
"token_type": "Bearer",
"user_api": "https://{server}.docusign.net"
}
Unfortunately we aren't receiving "user_api", instead we are receiving this:
{
"access_token": "ISSUED_ACCESS_TOKEN",
"token_type": "Bearer",
"refresh_token": "ISSUED_REFRESH_TOKEN",
"expires_in": 28800
}
Are you able to help me?
docusignapi docusign
asked 2 days ago
TSP CMS
161
New contributor
TSP CMS is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I have applied for the Docusign TSP Program.
We are following these instructions but we are facing some issues.
https://developers.docusign.com/id-tsp-api/guides/tsp-authentication
When we invoke the following route:
POST /oauth/token
POST oauth/token HTTP/1.1
Host: account-d.docusign.com
Content-Type: application/x-www-form-urlencoded
Authorization: Basic Y2xpZW50SWQ6Y2xpZW50U2VjcmV0
grant_type=authorization_code
&code=SplxlOBeZQQYbYS6WxSbIA
&redirect_uri=https%3A%2F%2Fclient.example.org%2Fcb
This should be the response that we are expecting:
HTTP/1.1 200 OK
Content-Type: application/json
Cache-Control: no-store
Pragma: no-cache
{
"access_token": "(access token example removed for document brevity)",
"expires_in": 28800,
"token_type": "Bearer",
"user_api": "https://{server}.docusign.net"
}
Unfortunately we aren't receiving "user_api", instead we are receiving this:
{
"access_token": "ISSUED_ACCESS_TOKEN",
"token_type": "Bearer",
"refresh_token": "ISSUED_REFRESH_TOKEN",
"expires_in": 28800
}
Are you able to help me?
docusignapi docusign
docusignapi docusign
asked 2 days ago
TSP CMS
161
New contributor
TSP CMS is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 2 days ago
TSP CMS
161
New contributor
TSP CMS is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 2 days ago
TSP CMS
161
New contributor
TSP CMS is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 2 days ago
TSP CMS
161
asked 2 days ago
TSP CMS
161
161
New contributor
TSP CMS is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
TSP CMS is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
TSP CMS is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Not sure why you're not getting theuser_apikey but another way you may be able to get it is withhttps://www.docusign.net/restapi/v2/login_information, that responses with abase_uri. Could be that it's the same value since it's tied to the user's account.
– JM-AGMS
2 days ago
Hi, I guess that api won't help me, TSP API expects something like /restapi/{version}/signature/ as the base path and this route gives me /restapi/{version}/accounts/{account_id}, which is the base path for the eSignature API. By the way, I should receive that TSP API base route path through the access token request, in the user_api field.
– TSP CMS
20 hours ago
add a comment |
Not sure why you're not getting theuser_apikey but another way you may be able to get it is withhttps://www.docusign.net/restapi/v2/login_information, that responses with abase_uri. Could be that it's the same value since it's tied to the user's account.
– JM-AGMS
2 days ago
Hi, I guess that api won't help me, TSP API expects something like /restapi/{version}/signature/ as the base path and this route gives me /restapi/{version}/accounts/{account_id}, which is the base path for the eSignature API. By the way, I should receive that TSP API base route path through the access token request, in the user_api field.
– TSP CMS
20 hours ago
Not sure why you're not getting the
user_api key but another way you may be able to get it is with https://www.docusign.net/restapi/v2/login_information, that responses with a base_uri. Could be that it's the same value since it's tied to the user's account.– JM-AGMS
2 days ago
Not sure why you're not getting the
user_api key but another way you may be able to get it is with https://www.docusign.net/restapi/v2/login_information, that responses with a base_uri. Could be that it's the same value since it's tied to the user's account.– JM-AGMS
2 days ago
Hi, I guess that api won't help me, TSP API expects something like /restapi/{version}/signature/ as the base path and this route gives me /restapi/{version}/accounts/{account_id}, which is the base path for the eSignature API. By the way, I should receive that TSP API base route path through the access token request, in the user_api field.
– TSP CMS
20 hours ago
Hi, I guess that api won't help me, TSP API expects something like /restapi/{version}/signature/ as the base path and this route gives me /restapi/{version}/accounts/{account_id}, which is the base path for the eSignature API. By the way, I should receive that TSP API base route path through the access token request, in the user_api field.
– TSP CMS
20 hours ago
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
TSP CMS is a new contributor. Be nice, and check out our Code of Conduct.
draft saved
draft discarded
TSP CMS is a new contributor. Be nice, and check out our Code of Conduct.
TSP CMS is a new contributor. Be nice, and check out our Code of Conduct.
TSP CMS is a new contributor. Be nice, and check out our Code of Conduct.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53373650%2fdocusign-tsp-api%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Not sure why you're not getting the
user_apikey but another way you may be able to get it is withhttps://www.docusign.net/restapi/v2/login_information, that responses with abase_uri. Could be that it's the same value since it's tied to the user's account.– JM-AGMS
2 days ago
Hi, I guess that api won't help me, TSP API expects something like /restapi/{version}/signature/ as the base path and this route gives me /restapi/{version}/accounts/{account_id}, which is the base path for the eSignature API. By the way, I should receive that TSP API base route path through the access token request, in the user_api field.
– TSP CMS
20 hours ago