Spotify Web API Console



Does anyone know if the Spotify Web API Console at was generated in any way from their RAML specification(s) (e.g. these ?

If yes, what was the tooling used?

p.s. I have also asked in the API Console page comments.



Hi there!

I am the main developer behind the Spotify API console. It was actually my first hack week project when I joined the company!

To answer your question, yes, the console is generated from the RAML that you linked. I haven’t checked yet, but it could be out of date since the maintainers of the API Console have to maintain two different repos where the RAML file lives (one internal, and the GitHub one you linked).

The backend is written in Python using the Flask framework, and some typical libraries like requests, Flask-Oauthlib, and PyYAML, among others.

What I’ve been doing is trying to release this as open source in three different parts: RAML parser, static documentation generator, and a form generator/application. The RAML parser is already open sourced, called RAMLfications. The static doc generator, griffin is also released, but it’s very alpha. The last part - the form generator/application - is not yet released.

There are also some JavaScript libraries, including Bootstrap, jQuery, Highlight, Linkify, and ZeroClipboard.

Let me know if this helps, or if you have any other questions.

/Lynn Root


Hi Lynn,

This is excellent, answer I was looking for.

I have an extra question regarding your use of Flask, do you feed Flask with the RAML file?
If you do, what Flask extensions do you use?


p.s. I see you are also author of the RAML 1.0 draft for Spotify Web API. Since, as RAML and Web APIs newbie, I really like what Spotify’s API as a comprehensive RAML example, I’ve been trying to help, just a bit :slight_smile: