Skip to main content
Blog
Home/

Developer Spotlight: Jim Cote, Liberty Fund

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

Developer Spotlight: Jim Cote, Liberty Fund

After graduating with a history degree, Jim Cote began programming and worked as a software consultant before becoming the Director of Information Services for Liberty Fund, Inc., an educational foundation based in Indianapolis, Indiana. He develops and maintains applications to run Liberty Fund's conference and publishing programs and is an enthusiastic Go language developer.

Liberty Fund runs over one hundred small conferences each year, and prior to implementing Docusign, staff processed hotel contracts, registrations and tax forms manually. Ending the faxing and emailing of documents using Docusign's web application improved their processes immediately. Using eSignature REST API within their internal event/CRM application provided another productivity jump with the automated generation, sending and receiving of tax and registration forms along with other contracts. Implementing Docusign Connect webhooks on Google's App Engine and Cloud Functions allows instant updates to internal databases so users can view document status within Liberty Fund's internal apps. The organization is currently experimenting with implementing the Docusign Click API to allow individuals to register their use of copyrighted material.

After we released our Swagger/OpenAPI specification, Jim created a new Go librarygenerated from the Swagger definition and released the package as open source. Used in Liberty Fund's systems to handle all of their Docusign REST API calls, the package fully implements the version 2 eSignature REST API and much of the new Click API. He expects to release Go libraries for the eSignature REST API v2.1 and the Organization Admin API soon.

In his spare time, Jim enjoys cycling and reading. He may be reached via LinkedIn.

Author Inbar Gazit
Inbar GazitSr. Manager, Developer Content

Inbar Gazit has been with Docusign since 2013 in various engineering roles. Since 2019 he has focused on developer content. 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 StackOverflow, answering your questions. Inbar can be reached at inbar.gazit@docusign.com.

More posts from this author

Related posts

  • Docusign for Developers Public Roadmap: A commitment to innovation and trust
    Developers

    Docusign for Developers Public Roadmap: A commitment to innovation and trust

    Author Julian Macagno
    Julian Macagno
  • LaborEdge Streamlines Healthcare Compliance with a Healthy Dose of Docusign

    LaborEdge Streamlines Healthcare Compliance with a Healthy Dose of Docusign

    Author Karissa Jacobsen
    Karissa Jacobsen
  • Ontology vs Taxonomy vs Data Model

    Ontology vs Taxonomy vs Data Model

    Author Dan Selman
    Dan Selman
Docusign for Developers Public Roadmap: A commitment to innovation and trust

Docusign for Developers Public Roadmap: A commitment to innovation and trust

Author Julian Macagno
Julian Macagno
LaborEdge Streamlines Healthcare Compliance with a Healthy Dose of Docusign

LaborEdge Streamlines Healthcare Compliance with a Healthy Dose of Docusign

Author Karissa Jacobsen
Karissa Jacobsen
Ontology vs Taxonomy vs Data Model

Ontology vs Taxonomy vs Data Model

Author Dan Selman
Dan Selman

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

Explore Docusign IAMTry eSignature for Free
Person smiling while presenting