To use swagger-ui you should take a look at thesource of swagger-ui html page and customize it. This basically requires you to instantiate a SwaggerUi object and call load() on it as below:

window.swaggerUi=newSwaggerUi({discoveryUrl:"http://petstore.swagger.wordnik.com/api/resources.json",dom_id:"swagger-ui-container",apiKey:"special-key",supportHeaderParams:false,headers:{"Authorization":"XXXX","someOtherHeader":"YYYY"},supportedSubmitMethods:['get','post','put']});window.swaggerUi.load();

• discoveryUrl parameter should point to a resource listing url as perSwagger Spec
• dom_id parameter is the the id of a dom element inside which SwaggerUi will put the user interface for swagger
• booleanValues SwaggerUI renders boolean data types as a dropdown. By default it provides a 'true' and 'false' string as the possible choices. You can use this parameter to change the values in dropdown to be something else, for example 0 and 1 by setting booleanValues to new Array(0, 1)
• docExpansion controls how the API listing is displayed. It can be set to 'none' (default), 'list' (shows operations for each resource), or 'full' (fully expanded: shows operations and their details)
• onComplete is a callback function parameter which can be passed to be notified of when SwaggerUI has completed rendering successfully.
• onFailure is a callback function parameter which can be passed to be notified of when SwaggerUI encountered a failure was unable to render.
• All other parameters are explained in greater detail below

swagger-ui supports invocation of all HTTP methods APIs but only GET methods APIs are enabled by default. You can choose to enable other HTTP methods like POST, PUT and DELETE. This can be enabled bysetting the supportedSubmitMethods parameter when creating SwaggerUI instance.

For example if you wanted to enable GET, POST and PUT but not for DELETE, you'd set this as:

supportedSubmitMethods: ['get', 'post', 'put']

Note that for POST/PUT body, you'd need to paste in the request data in an appropriate format which your service can unmarshall

header parameters are supported. However because ofCross-Origin Resource Sharing restrictions, swagger-ui, by default, does not send header parameters. This can be enabled bysetting the supportHeaderParams to true when creating SwaggerUI instance as below:

supportHeaderParams: true

If you have some header parameters which you need to send with every request, use the headers as below:

 headers: { "Authorization": "XXXX", "someOtherHeader": "YYYY" }

If you enter an api key in swagger-ui, it sends a parameter named 'api_key' as a query (or as a header param if you've enabled it as described above). You may not want to use the name 'api_key' as the name of this parameter. You can change its name by setting theapiKeyName parameter when you instantiate a SwaggerUI instance. For example to call it 'sessionId'

apiKeyName: "sessionId"

Create your own fork ofwordnik/swagger-ui

To share your changes,submit a pull request.

Copyright 2011-2013 Wordnik, Inc.

Licensed under the Apache License, Version 2.0 (the "License");you may not use this file except in compliance with the License.You may obtain a copy of the License atapache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, softwaredistributed under the License is distributed on an "AS IS" BASIS,WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.See the License for the specific language governing permissions andlimitations under the License.