ramses

We've built something similar with RAML in Python. It's called Ramses: https://github.com/ramses-tech/ramses I like the "single source of truth" concept. It makes a lot of sense IMO. Does it generate the handlers for you or do you have to write them by hand and hook to the Swagger definition?

Uses RAML to generate a RESTful API using Pyramid. Nice. Github: https://github.com/brandicted/ramses/ Docs: https://ramses.readthedocs.org The Pyramid app generated uses Nefertari (ElasticSearch-based views and SQLAlchemy or MongoDB persistence): https://github.com/brandicted/nefertari Nefertari docs: https://nefertari.readthedocs.org

I am surprised that Amazon did not add support to more API description formats like RAML or apiblueprint. It is such a key feature. If I wanted to use this service in front of existing APIs, even only one API, I would not want to go through the work of having to redefine all my endpoints through a web form! Shameless plug: after working on several API projects, I have been researching ways to not have to "code" over and over again what goes into creating endpoints, it became so repetitive. Lately, I turned to RAML (Yaml for REST) and, with 4 other developers, we created an opensource project called Ramses. It creates a fully functional API from a RAML file. It is a bit opinionated but having to "just" edit a Yaml file when building a new API simplified my life. As a bonus, I also get a documentation and a javascript client generated from

Makes you wanna eat APIs for lunch :) * This is the link to the github repo for Ramses: https://github.com/brandicted/ramses