Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Swagger Play2 Module


This is a module to support the play2 framework from playframework. It is written in scala but can be used with either java or scala-based play2 applications.

Version History

  • swagger-play2 1.3.12 supports play 2.3. If you need 2.2 support, use 1.3.7 or earlier.

  • swagger-play2 1.3.7 supports play 2.2. If you need 2.1 support, please use 1.3.5 or earlier

  • swagger-play2 1.3.6 requires play 2.2.x.

  • swagger-play2 1.2.1 and greater support scala 2.10 and play 2.0 and 2.1.

  • swagger-play2 1.2.0 support scala 2.9.x and play 2.0, please use 1.2.0.


You can depend on pre-built libraries in maven central by adding the following dependency:

val appDependencies: Seq[sbt.ModuleID] = Seq(
  "com.wordnik" %% "swagger-play2" % "1.3.12"

Or you can build from source.

cd modules/swagger-play2

sbt publishLocal

Adding Swagger to your Play2 app

There are just a couple steps to integrate your Play2 app with swagger.

  1. Add the resource listing to your routes file (you can read more about the resource listing here

GET     /api-docs               controllers.ApiHelpController.getResources

  1. Annotate your REST endpoints with Swagger annotations. This allows the Swagger framework to create the api-declaration automatically!

In your controller for, say your "pet" resource:

@Api(value = "/pet", description = "Operations about pets")
class PetApiController extends BaseApiController {

  @ApiOperation(nickname = "getPetById", value = "Find pet by ID", notes = "Returns a pet", response = classOf[models.Pet], httpMethod = "GET")
    new ApiResponse(code = 400, message = "Invalid ID supplied"),
    new ApiResponse(code = 404, message = "Pet not found")))
  def getPetById(
    @ApiParam(value = "ID of the pet to fetch") @PathParam("id") id: String) = Action {


What this does is the following:

  • Tells swagger that the methods in this controller should be described under the /api-docs/pet path

  • The Routes file tells swagger that this API listens to /{id}

  • Describes the operation as a GET with the documentation Find pet by Id with more detailed notes Returns a pet ....

  • Takes the param id, which is a datatype string and a path param

  • Returns error codes 400 and 404, with the messages provided

In the routes file, you then wire this api as follows:

GET     /api-docs/pet            controllers.ApiHelpController.getResource(path = "/pet")

GET     /pet/:id                 controllers.PetApiController.getPetById(id)

This will "attach" the /api-docs/pet api to the swagger resource listing, and the method to the getPetById method above

The ApiParam annotation

Swagger for play has two types of ApiParams--they are ApiParam and ApiParamImplicit. The distinction is that some paramaters (variables) are passed to the method implicitly by the framework. ALL body parameters need to be described with ApiParamImplicit annotations. If they are queryParams or pathParams, you can use ApiParam annotations.

Sample Application

Please take a look here for a full sample application using the Swagger Play2 module with scala, and here for a Java example.

Something went wrong with that request. Please try again.