Skip to content
Swagger client library for Python
Branch: master
Clone or download
CaptainConsternant and matt-jordan Fixed broken imports for python 3.6 (#18)
* Fixing imports for python 3

* Fixing imports for python 3

Fixing imports for python 3

* Update

* Retrocomptability on imports

* Retrocomptability on imports

* python 2 and 3 compability for urllib

* Update
Latest commit 6e7f6b9 Apr 11, 2019


About is a Python library for using Swagger defined API's.

Swagger itself is best described on the Swagger home page:

Swagger is a specification and complete framework implementation for describing, producing, consuming, and visualizing RESTful web services.

The Swagger specification defines how API's may be described using Swagger. also supports a WebSocket extension, allowing a WebSocket to be documented, and auto-generated WebSocket client code.


Install the latest release from PyPI.

$ sudo pip install swaggerpy

Or install from source using the script.

$ sudo ./ install

API will dynamically build an object model from a Swagger-enabled RESTful API.

Here is a simple example using the Asterisk REST Interface

#!/usr/bin/env python

import json

from swaggerpy.client import SwaggerClient
from swaggerpy.http_client import SynchronousHttpClient

http_client = SynchronousHttpClient()
http_client.set_basic_auth('localhost', 'hey', 'peekaboo')

ari = SwaggerClient(

ws ='hello')

for msg_str in iter(lambda: ws.recv(), None):
    msg_json = json.loads(msg_str)
    if msg_json['type'] == 'StasisStart':
        channelId = msg_json['channel']['id']


There are the beginnings of a Mustache-based code generator, but it's not functional... yet.

Data model

The data model presented by the swagger_model module is nearly identical to the original Swagger API resource listing and API declaration. This means that if you add extra custom metadata to your docs (such as a _author or _copyright field), they will carry forward into the object model. I recommend prefixing custom fields with an underscore, to avoid collisions with future versions of Swagger.

There are a few meaningful differences.

  • Resource listing
  • The file and base_dir fields have been added, referencing the original .json file.
  • The objects in a resource_listing's api array contains a field api_declaration, which is the processed result from the referenced API doc.
  • API declaration
  • A file field has been added, referencing the original .json file.


The code is documented using Sphinx, which allows IntelliJ IDEA to do a better job at inferring types for autocompletion.

To keep things isolated, I also recommend installing (and using) virtualenv.

$ sudo pip install virtualenv
$ mkdir -p ~/virtualenv
$ virtualenv ~/virtualenv/swagger
$ . ~/virtualenv/swagger/bin/activate

Setuptools is used for building. Nose is used for unit testing, with the coverage plugin installed to generated code coverage reports. Pass --with-coverage to generate the code coverage report. HTML versions of the reports are put in cover/index.html.

$ ./ develop   # prep for development (install deps, launchers, etc.)
$ ./ nosetests # run unit tests
$ ./ bdist_egg # build distributable


Copyright (c) 2013, Digium, Inc. All rights reserved. is licensed with a BSD 3-Clause License.

You can’t perform that action at this time.