A toolkit for building well-connected, self-describing web APIs.

Author: Tom Christie. Follow me on Twitter

Full documentation for REST framework is available on http://django-rest-framework.org.

Note that this is the 2.0 version of REST framework. If you are looking for earlier versions please see the 0.4.x branch on GitHub.

Django REST framework is a lightweight library that makes it easy to build Web APIs. It is designed as a modular and easy to customize architecture, based on Django's class based views.

Web APIs built using REST framework are fully self-describing and web browseable - a huge useability win for your developers. It also supports a wide range of media types, authentication and permission policies out of the box.

If you are considering using REST framework for your API, we recommend reading the REST framework 2 announcment which gives a good overview of the framework and it's capabilities.

There is also a sandbox API you can use for testing purposes, available here.

• Python (2.6, 2.7)
• Django (1.3, 1.4, 1.5)

Optional:

• Markdown - Markdown support for the self describing API.
• PyYAML - YAML content type support.
• django-filter - Filtering support.

Install using pip...

pip install djangorestframework

...or clone the project from github.

git clone [email protected]:tomchristie/django-rest-framework.git
pip install -r requirements.txt

To build the docs.

./mkdocs.py

To run the tests.

./rest_framework/runtests/runtests.py

Date: 16th Nov 2012

• Added FileField and ImageField. For use with MultiPartParser.
• Added URLField and SlugField.
• Support for read_only_fields on ModelSerializer classes.
• Support for clients overriding the pagination page sizes. Use the PAGINATE_BY_PARAM setting or set the paginate_by_param attribute on a generic view.
• 201 Responses now return a 'Location' header.
• Bugfix: Serializer fields now respect max_length.

Date: 9th Nov 2012

• Filtering support.
• Bugfix: Support creation of objects with reverse M2M relations.

Date: 7th Nov 2012

• Support use of HTML exception templates. Eg. 403.html
• Hyperlinked fields take optional slug_field, slug_url_kwarg and pk_url_kwarg arguments.
• Bugfix: Deal with optional trailing slashs properly when generating breadcrumbs.
• Bugfix: Make textareas same width as other fields in browsable API.
• Private API change: .get_serializer now uses same instance and data ordering as serializer initialization.

Date: 5th Nov 2012

Warning: Please read this thread regarding the instance and data keyword args before updating to 2.1.0.

• Serializer instance and data keyword args have their position swapped.
• queryset argument is now optional on writable model fields.
• Hyperlinked related fields optionally take slug_field and slug_field_kwarg arguments.
• Support Django's cache framework.
• Minor field improvements. (Don't stringify dicts, more robust many-pk fields.)
• Bugfixes (Support choice field in Browseable API)

Date: 2nd Nov 2012

• Fix issues with pk related fields in the browsable API.

Date: 1st Nov 2012

• Add support for relational fields in the browsable API.
• Added SlugRelatedField and ManySlugRelatedField.
• If PUT creates an instance return '201 Created', instead of '200 OK'.

Date: 30th Oct 2012

• Redesign of core components.
• Fix all of the things.

Copyright (c) 2011, Tom Christie All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.