Interswitch API Documentation; New and Improved

Subscribe to my newsletter and never miss my upcoming articles

1st April 2020 marked the beginning of a new Financial year at Interswitch and I can't help but marvel at what we've been able to achieve in Interswitch Engineering within the last financial year particularly towards improving the experience of developers integrating with Interswitch APIs.

When I joined Interswitch in June 2019, I was assigned to join the Developer Relations team. Our goal was to improve the experience of developers integrating with Interswitch APIs. This was a huge feat in itself, to put it lightly, we had received a lot of bad reviews regarding our APIs ranging from the complexity of the APIs which makes integration worrisome, to lack of proper API documentation and sometimes lack of support. However, the topmost issue from the issues listed above was the documentation. I must say, working to improve the documentation platform for Interswitch gave me the opportunity to test so many platforms before arriving at a decision on which best suits our current needs, it has also improved my understanding of API products in Interswitch and also had me working with internal and external developers to ensure that we tackled existing problems to improve the experience of developers integrating with our APIs.

In this article, I will run you through the process of how Interswitch documentation transformed from this to this, the issues we had with our existing documentation platform, why we chose the new platform and how this new platform addresses the issues in the previous documentation platform.

The Old Documentation Platform - Docbase

                            Docbase homepage

There has been a misconception over the past few years that Interswitch does not have a centralized documentation platform and PDF documents are given to aid developer's integration with our APIs. While the statement above was true at some point, that scenario changed a long time ago. A few years ago, in a bid to have all API documentation in a single place to improve our external developers' experience, we moved our API documentation to docbase built with Wordpress. The move to Docbase was an attempt to solve the issues our users faced when they read our API documentation. While it was able to solve some of those issues, others still persisted.

Disadvantages of the old documentation platform

  1. Lack of proper awareness among developers during project launch - Developers are the primary users of API documentation and as such should be at the forefront of any awareness campaign done at project launch but this wasn't done when Docbase was launched and that made almost everyone in the developer community unaware of the existence of our documentation platform.

  2. Outdated Content - There was a disconnection between API update and documentation update. Oftentimes, the documentation is not updated when the product API is updated and as such made the documentation become obsolete.

  3. A disconnection between our external and internal developers - Any developer can attest to the fact that whenever they experience issues with integration, getting support from an internal developer gets the issue resolved faster either because the internal developer has more understanding of the API or the fact that they can relate more with your problem from a developer's point of view just as you.

Now don't get me wrong, docbase also has its advantages such as its provision of a one-stop platform for all our APIs and a community forum page. However, as most of our external developers could attest to the disadvantages outweigh the advantages and with that the need to sort for improvements and create a better platform for our API documentation that addresses the issues of the docbase.

The New Documentation Platform - Slate

                          Slate product homepage

                    Slate product sub-category homepage

                          Slate API Reference

The new documentation platform was built with slate, a Ruby-based tool that generates a great-looking, three-panelled API documentation static site from a set of markdown files.

To improve our documentation, Slate was chosen for the following reasons:

  1. Open Source - In a bid to promote open source movement, Interswitch has been adopting the use of some open-source tools and our documentation platform is one of them.

  2. Flexibility - Slate's flexibility gave us the freedom to build what we wanted without starting from scratch. Due to the flexibility of slate, we were able to transform it from its original single page three-panelled API documentation static site to a multi-page site with a homepage for all products categories. Each product has its own homepage for product subcategories where necessary, get started guides, and comprehensive API references e.t.c.

    Slate original single page three-panelled API documentation static site

  3. When you write docs with Slate, you're just writing Markdown, which makes it simple to edit and understand.

  4. Slate provides an out-of-the-box syntax highlighting for over 100 languages with no configuration required.

  5. It could be hosted in a public GitHub repository which will make it simple for other developers to make pull requests to the docs if they find typos or want to make suggestions. Interswitch engineering has plans to Open Source it's documentation in the nearest future so that people could have the freedom to report issues and also work on it directly.

Even though Slate offered great features, we knew that we needed to put some internal processes in place to ensure that it doesn't end up like our previous API documentation. To achieve this, the developer relations team assumed the documentation team position and we also ensured that for every API that is built or modified and pushed to production, a corresponding API Reference must be updated on slate and pushed to the documentation team for review.

Additional Features

The developer relations team seeks to bridge the gap between our external and internal developers to ensure that the integration process of our APIs becomes seamless. Here are some other things we've done to ensure that the aforementioned goals come to reality.


  1. Developer Forum - We created a forum that will connect our internal and external developers thereby giving them a place to easily interact, make feature requests, report bugs, suggest edits on documentation, carry out beta testing, etc.

  2. Developer Console - The new developer console provides self-service integration, giving you the ability to access Interswitch product APIs, authentication parameters, Sandbox keys, production keys, documentation and seamless project management.

  3. Admin Dashboard - A dashboard that will be managed internally and used to manage APIs on the developer console. Requests from the developer console would also be handled seamlessly on the admin dashboard.

Conclusion

We might not be where we want to be yet but at Interswitch engineering, we believe that we've taken a bold first step in the right direction to give our developers the better and seamless integration experience they deserve. We are excited about how much we've been able to achieve this past financial year. It's the beginning of a new financial year and we intend to top the last so stay tuned.

No Comments Yet