Skip to main content
Blog
Home/

Quick Start API Code Example for C#

Author Larry Kluger
Larry KlugerLead Product Manager for Partner Platforms
Summary3 min read

Check out our new code example in C# to get you up to speed quickly on using the eSignature REST API.

We’ve just released a new Quick Start API Code Example for C#, complete with a 4 minute target="_blank" rel="noopener">installation and demonstration video.

Each quick start code example is created from a Github project that you can download, run, and use to learn Docusign functionality in multiple coding languages. The quick start code examples enable you to try the API while delaying the need to add OAuth to your proof of concept application.

You can use the quick start code get an example program up and running to perform basic operations within minutes. This is ideal for hackathons, learning workflows, and creating proof of concept applications, but it is important to note that applications created using this code use the OAuth Token Generator tool rather than implement a real authentication workflow and are not production-ready.

To learn more about Docusign authentication workflows and which authentication flow is best for your application, see the Authentication Overview.

In addition to the quick start code examples, we’ve released JWT Grant authentication examples, and Authorization Code Grant example launchers.

For production projects, I recommend that you start with the Authorization Code Grant launchers. They’re available now for Node.js and Java. Examples for C# and other languages are also in development.

Many more code examples are on the way, so stay tuned to learn more. Do you have an idea for a code example or larger sample application? Let me know via developers@docusign.com.

Author Larry Kluger
Larry KlugerLead Product Manager for Partner Platforms

Larry Kluger has over 40 years of tech industry experience as a software developer, developer advocate, entrepreneur, and product manager. An award-winning speaker prominent StackOverflow contributor, he enjoys giving talks and helping the ISV and developer communities.

Twitter: @larrykluger

LinkedIn: https://www.linkedin.com/in/larrykluger/

More posts from this author

Related posts

  • Developers

    Select the right tab placement strategy for your Docusign integration

    Author Marty Scholes
    Marty Scholes
    Select the right tab placement strategy for your Docusign integration
  • The Agreement Trap: How Developers Can Break Free with Docusign IAM

    Author Raileen Del Rosario
    Raileen Del Rosario
    The Agreement Trap: How Developers Can Break Free with Docusign IAM
  • Secure, verify, comply: Automate identity checks with Docusign APIs

    Author Niani Byrd
    Niani Byrd
    Secure, verify, comply: Automate identity checks with Docusign APIs

Select the right tab placement strategy for your Docusign integration

Author Marty Scholes
Marty Scholes
Select the right tab placement strategy for your Docusign integration

The Agreement Trap: How Developers Can Break Free with Docusign IAM

Author Raileen Del Rosario
Raileen Del Rosario
The Agreement Trap: How Developers Can Break Free with Docusign IAM

Secure, verify, comply: Automate identity checks with Docusign APIs

Author Niani Byrd
Niani Byrd
Secure, verify, comply: Automate identity checks with Docusign APIs

Discover what's new with Docusign IAM or start with eSignature for free

Explore Docusign IAMTry eSignature for Free
Person smiling while presenting