Skip to main content
Blog
Home/Developers

Swagger spec for eSignature REST API v2.1 published to GitHub

Author Inbar Gazit
Inbar GazitSr. Manager, Developer Content and Advocacy
Summary3 min read

Docusign releases new Swagger spec for eSignature API v2.1 published to GitHub

    • Additional Resources

    Table of contents

    As we announced in this blog post, Docusign recently released version 2.1 of our eSignature REST API.Today, we're happy to announce Docusign has also released the eSignature REST API v2.1 Swagger definition file. You can find the newly released version in esignature.rest.swagger-v2.1.json.

    Docusign internal team building the six client SDKs (C#, Java, Node.js, PHP, Python and Ruby) uses this Swagger definition file to help them generate the code for each SDK. You can use it to build your own client library for any coding language or platform. You can also use the Swagger definition file in more creative ways, such as building a drag-and-drop visual designer tool for API consumption.

    Additional Resources

    Author Inbar Gazit
    Inbar GazitSr. Manager, Developer Content and Advocacy

    Inbar Gazit has been with Docusign since 2013 in various engineering roles. Since 2019 he has focused on developer content and advocacy. Inbar works on code examples including the launchers, available on GitHub in eight languages, and helps build sample apps showcasing the various Docusign APIs. He is also active on Docusign Community and StackOverflow, answering your questions. Inbar can be reached at inbar.gazit@docusign.com.

    More posts from this author

    Related posts

    • Developers

      How to bypass Signature Adoption in Docusign embedded signing flows

      Author Arnaud Lesueur
      Arnaud Lesueur
      How to bypass Signature Adoption in Docusign embedded signing flows

    Docusign IAM is the agreement platform your business needs

    Start for FreeExplore Docusign IAM
    Person smiling while presenting