# Interactive API - Tooling?

**URL:** <https://forums.suse.com/t/interactive-api-tooling/2593>\
**Category:** General\
**Created:** [April 25, 2016, 9:09pm UTC](https://forums.suse.com/t/interactive-api-tooling/2593 "2016-04-25T21:09:51Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jlaswell](https://avatars.discourse-cdn.com/v4/letter/j/c2a13f/32.png) [@jlaswell](https://forums.suse.com/u/jlaswell)\
**Post date:** [April 25, 2016, 9:09pm UTC](https://forums.suse.com/t/interactive-api-tooling/2593/1 "2016-04-25T21:09:51Z")

</div>

We have fallen in love with the ability to interact with the Rancher API via the browser. Would anyone know the tooling being used to generate the interactivity for that? We’re hoping to replicate that for some of our applications.

---

<div class="post-metadata">

**Author:** ![vincent](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/vincent/32/7156_2.png) [@vincent](https://forums.suse.com/u/vincent)\
**Post date:** [April 25, 2016, 11:56pm UTC](https://forums.suse.com/t/interactive-api-tooling/2593/2 "2016-04-25T23:56:00Z")

</div>

Not so good news: it’s all custom  
Good news: it’s all open-source:

Spec: [https://github.com/rancher/api-spec](https://github.com/rancher/api-spec)

UI: [https://github.com/rancher/api-ui](https://github.com/rancher/api-ui)

Java server implementation: [https://github.com/rancher/gdapi-java-server](https://github.com/rancher/gdapi-java-server) (the main Rancher API uses this)

Go client/server implementation: [https://github.com/rancher/go-rancher](https://github.com/rancher/go-rancher) (some smaller projects like catalog API use this, but it only implements a smallish portion of the spec)

---

<div class="post-metadata">

**Author:** ![jlaswell](https://avatars.discourse-cdn.com/v4/letter/j/c2a13f/32.png) [@jlaswell](https://forums.suse.com/u/jlaswell)\
**Post date:** [April 26, 2016, 2:27pm UTC](https://forums.suse.com/t/interactive-api-tooling/2593/3 "2016-04-26T14:27:51Z")

</div>

Custom doesn’t bother us! Thanks for the info on the spec as well as the implementation.

We are using api blueprint to render docs, and are wondering if we can take a similar approach to the go-rancher repo using those to generate the schema.

Thanks so much for the info.