I had created one DocuSign trial account but here i need to Use the DocuSign API then i created developer account(Sandbox) with the same credentials that i used while creating a DocuSign trial account.
Here i am having an issue .. I have tool in which i am using that API to create and send the envelope but to get the envelope status i want to use the pipeline to get the latest envelope status.
But the pipeline does not connect with the developer account and it can connect with the normal account.
Can you please let me know is there any way where we can communicate 2 accounts or can we call API with the normal trial account?
Sandbox accounts are in the Demo environment, Trial accounts are in the Production environment. Those two systems are effectively air-gapped and cannot communicate.
In order to make API calls against your trial account, you will need to authenticate as a member of that trial account.
Related
I'm using this API: https://stripe.com/docs/api/accounts/create
What happens if you try to create an account with a preexisting email? Will the operation fail, or is it possible to have multiple accounts with the same email?
Also, are Connect accounts scoped to your Stripe account, or are they global IDs within the Stripe ecosystem?
Thanks!
It's possible to create multiple Stripe accounts with the same email address. You can test this out by creating multiple accounts in Test mode with the same email value; Stripe won't return an error. In your live application, you should keep track in a database of the mapping between your platform user and the Stripe Connect account you create for them.
Express and Custom accounts can be used only by the platform that created them. Every merchant account on Stripe (regardless of account type) has a unique account ID.
I have a small business where 5 of my customers use docusign. They want to be able to manage their docusign accounts through our website. I have created a docusign api on my end which I tested using my own developer account using my integration and secret keys which I store on my server in the db. I now want to allow my 5 customers to use this api to control their own docusing accounts. Do they all need to have a developer account and make it go live? I'm sure there is a better way and I cant make sense of it.
Do I need to push my app to live as well and purchase an API plan from docusign?
Please help it s hard to find any resource about this.
Do they all need to have a developer account and make it go live?
No, they don't need to. They have a production account and once your app goes live they can use your app with their account. If you want them to test your app in the developer environment first - then yes, they can get a developer account (which is free) to do some testing, but not required at all.
Do I need to push my app to live as well and purchase an API plan from
docusign?
Yes, you need to make your app live so that it can be used by paying customers in production. You would need your own production account to do that. If you are an ISV/Partner - you can get a free one, otherwise you will have to pay for your plan.
I am trying to integrate our web app with DocuSign. We expect our web app customers will authenticate and grant consent to our app to make API calls on behalf of their DocuSign accounts. Then our app will create envelopes (using access tokens to customer DocuSign accounts) and allow our app users to sign them using embedded signing.
We've built a prototype using demo account and everything works like a charm.
The only thing what is still unclear for me is how it is supposed to work after going live.
Am I right that our customer will be charged each envelop sending, since our integration makes call on behalf of their account?
Is it enough for our customer to pay for Standard eSignature Plan to make embedded signing work, or they should choose Enhanced Plans (the one where API feature is listed)
Should our account plan (which holds Integration Key) be at least Advanced Developer to support embedded signing?
Could anyone advise on the matter. Thanks!
Am I right that our customer will be charged each envelope sending, since our integration makes call on behalf of their account?
A. Yes, you're right. If your customer logins in to DocuSign using their own DocuSign user account, then their DocuSign account is charged. Your own DocuSign account is not involved, at all, in this scenario. Your client id (integration key) can be used by any DocuSign account user with their own account, once they grant consent to it.
Is it enough for our customer to pay for Standard eSignature Plan to make embedded signing work, or they should choose Enhanced Plans (the one where API feature is listed)
A. I don't believe that the standard eSignature plan includes support for embedded signing.
Should our account plan (which holds Integration Key) be at least Advanced Developer to support embedded signing?
A. Either Advanced Developer or a "regular" eSig account that supports embedded signing. This is for your testing purposes. If you use a regular account that supports embedded signing then your other company groups can share the account for use in sending out agreements for signature.
Also
Please sign up as an ISV with DocuSign via https://partners.docusign.com
(no charge.) Being a registered partner provides you with additional information and enables you to use the partner use license to sell your app to DocuSign customers.
Pro-tip: use your developer account to automatically test your app. Preferably once a day. New releases are first launched on the developer system about a week before production. DocuSign has thousands of tests to guard against regression bugs. But it is possible for a bug to slip through. If you detect any issues on the developer system then DocuSign will typically stop the production deployment to fix the issue.
Added
Re error message when a feature is not enabled: see this question.
Re which plans include the embedded signing feature: sorry, I don't have that information.
I am currently using a docusign personal plan and I have integration keys setup in the account.Will my integration keys work if I cancel my current plan and downgrade to the free one? I only need the integration key for oauth of other docusign customers and not to send envelopes from my account.
You should not be using a free account for your DocuSign integrations. Free accounts cannot be used to go-live. After you are live, if you downgrade your account, we gracefully allow your app to continue working, but that can be changed at any time, so please contact your sales rep if you have any billing related questions.
If you are an ISV, or SI, and build apps for others, you should apply for a free partner account that can be used to promote integration keys. Check out how to get into this program :
https://www.docusign.com/partners
I have a system in which I am integrating the DocuSign API.
Inside my system my client can send a document to the emails that it defined.
I have a DocuSign account with the Integration Key enabled on my system, how do I register within my account the subaccounts for each of my clients to send their contracts to their clients using the API?
I have already tested the entire Docusign API, I just can not find how to register sub-accounts to send on behalf of each client of mine!
Your question is not too clear. Hopefully this will be of help:
DocuSign does not have "subaccounts."
DocuSign has organizations (which group together an organization's or company's accounts).
Customers often have multiple accounts, with or without the organization capability. Accounts have account-wide settings. So it is common that the HR and Finance departments will have separate accounts, with different settings.
Accounts have one or more members (users). An individual can be a member of more than one account.
An Integration Key (also called a client_id) identifies an application.
An Integration Key (and its app) can be used by any user on any account. The user must give permission for the application to act on his/her behalf.
DocuSign has a developer sandbox (called demo) and multiple production systems (Europe, North America 1, 2, 3, etc). The Integration Keys in demo are entirely separate from those in the production systems.
The "Go-live" process is used to copy an Integration Key from demo to the production systems.