Challenge Overview
Radiogerät: Swiggity Swagger. API Blueprint for JBL Mobile App
Welcome to the Radiogerät Swagger challenge.
In this challenge we'd like you to come up with a Swagger 2.0 spec document for the attached designs. If you're already on the Radiogerät team, you can also find the designs on the gitlab.com repo. If not, post on the forum and we'll add you in for later, repo based challenges. This API document will be the blueprint for the MEAN stack, hybrid mobile app that we're planning.
Final Submission Guidelines
Requirement:
This API is for a data driven mobile app so we want a well-defined RESTful API defined to support the front end that's layed out in the designs.
The data structures and data relationships should be kept fairly simple/flat and can be defined in this challenge based upon the designs themselves. The only somewhat strictly structured data we have defined is for the "Fit Guide". This contains "make", "model" & "year" (note: designs contain "trim" but that is not supported at this time) and returns car and product information. Other data structures such as "products", "videos", "about JBL", and app "users" can be inferred from the designs and defined in your blueprint.
Deliverable for this challenge is to simply be a Swagger 2.0 YAML file that outlines all the endpoints needed to support the designs.
Standard RESTful patterns for resource naming should be followed as well as standard methods on those defined resources.
That's it. Show us how you swagger.