# API for cert-tools

**URL:** <https://community.blockcerts.org/t/api-for-cert-tools/1688>\
**Category:** Community\
**Created:** [February 6, 2019, 3:53pm UTC](https://community.blockcerts.org/t/api-for-cert-tools/1688 "2019-02-06T15:53:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![divye.gala](https://avatars.discourse-cdn.com/v4/letter/d/3ec8ea/32.png) [@divye.gala](https://community.blockcerts.org/u/divye.gala)\
**Post date:** [February 6, 2019, 3:53pm UTC](https://community.blockcerts.org/t/api-for-cert-tools/1688/1 "2019-02-06T15:53:52Z")

</div>

Hi, I represent Center for 21st Century Universities at Georgia Tech. We are using cert-tools to generate blockchain certificates, and have been recently looking into building a web-app to smoothen the process of generating certificates and issuing them. However, an issue that we are facing is that there is no API to communicate with cert-tools as it uses shell scripts and the filesystem to generate certificate templates and unsigned certificates. This poses a challenge to run a dockerized web-app as it’s a lot of extra steps to communicate with cert-tools. Is it possible for cert-tools to have some APIs in terms of a web-app or Python package for the community to be able to use it better?

---

<div class="post-metadata">

**Author:** ![kim](https://sea2.discourse-cdn.com/flex016/user_avatar/community.blockcerts.org/kim/32/307_2.png) [@kim](https://community.blockcerts.org/u/kim)\
**Post date:** [February 11, 2019, 5:42pm UTC](https://community.blockcerts.org/t/api-for-cert-tools/1688/2 "2019-02-11T17:42:01Z")

</div>

Hi, I think a cert-tools api would be great. You might want to check out the cert-issuer project, where there is work on a web interface, contributed by Yancy Ribbens. Although cert-issuer is further along in the pipeline (i.e. assumes the certificates already exist), you might want to take a look Yancy’s work to see if there are any useful patterns or if they can work together.

Thanks,  
Kim

---

<div class="post-metadata">

**Author:** ![mlisle](https://sea2.discourse-cdn.com/flex016/user_avatar/community.blockcerts.org/mlisle/32/454_2.png) [@mlisle](https://community.blockcerts.org/u/mlisle)\
**Post date:** [February 15, 2019, 8:18pm UTC](https://community.blockcerts.org/t/api-for-cert-tools/1688/3 "2019-02-15T20:18:35Z")

</div>

FYI… we submitted a pull request at [https://github.com/blockchain-certificates/cert-tools/pull/36](https://github.com/blockchain-certificates/cert-tools/pull/36). Curious to hear everyone’s thoughts on this suggestion.

---

<div class="post-metadata">

**Author:** ![kim](https://sea2.discourse-cdn.com/flex016/user_avatar/community.blockcerts.org/kim/32/307_2.png) [@kim](https://community.blockcerts.org/u/kim)\
**Post date:** [February 15, 2019, 11:07pm UTC](https://community.blockcerts.org/t/api-for-cert-tools/1688/4 "2019-02-15T23:07:31Z")

</div>

Thank you @mlisle, these are great changes. I merged the PR
