Web APIs for Django. 🎸
Go to file
2019-03-25 12:19:43 +05:30
docs Document DateTimeField default_timezone argument (#6469) 2019-03-12 21:15:12 -07:00
docs_theme Remove executable bit from static assets (#6484) 2019-03-03 18:39:08 +00:00
licenses Prefer https protocol for links in docs when available 2018-01-15 15:15:21 +01:00
requirements upgraded pytest dependencies (#6492) 2019-03-07 09:22:00 +00:00
rest_framework Merge multiple isinstance() calls to one (#6513) 2019-03-22 12:29:45 +00:00
tests Fix schema generation of ManyRelatedField to detect the child type (#6489) 2019-03-07 11:26:03 +01:00
.gitignore Update .gitignore 2018-05-08 09:21:32 +01:00
.travis.yml Remove Django 2.2 from allowed failure. 2019-02-14 15:57:20 +01:00
codecov.yml Update codecov.yml 2018-10-02 16:57:49 +01:00
CONTRIBUTING.md Use HTTPS URL example for git clone commands. (#6134) 2018-12-19 19:28:03 +01:00
ISSUE_TEMPLATE.md Correct 3rd-party-packages link in issue template. 2019-02-14 12:01:36 +01:00
LICENSE.md Prefer https:// for URLs when available throughout project (#6208) 2018-10-02 08:28:58 +02:00
MANIFEST.in Fix typo to bring locale back to installed files 2017-12-21 12:12:08 +01:00
mkdocs.yml Version 3.9 (#6247) 2018-10-18 10:38:46 +01:00
PULL_REQUEST_TEMPLATE.md Update links after moving to encode org 2017-04-07 10:28:35 -04:00
README.md Update README.md 2019-03-25 12:19:43 +05:30
requirements.txt Fix typos in comments 2015-08-19 03:55:39 +02:00
runtests.py runtests.py: clean up PYTEST_ARGS (#6040) 2018-06-21 14:28:25 +01:00
setup.cfg Drop Django 1.10 support (#5657) 2018-07-06 12:14:31 +02:00
setup.py Add Python 3.7 to classifiers. (#6458) 2019-02-15 10:57:02 +01:00
tox.ini Update tox to use Django 2.2b2. 2019-02-14 15:57:20 +01:00

[Django REST framework][docs]

[![build-status-image]][travis] [![coverage-status-image]][codecov] [![pypi-version]][pypi]

Awesome web-browsable Web APIs.

Full documentation for the project is available at [https://www.django-rest-framework.org/][docs].


Funding

REST framework is a collaboratively funded project. If you use REST framework commercially we strongly encourage you to invest in its continued development by [signing up for a paid plan][funding].

The initial aim is to provide a single full-time position on REST framework. Every single sign-up makes a significant impact towards making that possible.

[![][sentry-img]][sentry-url] [![][stream-img]][stream-url] [![][rollbar-img]][rollbar-url] [![][cadre-img]][cadre-url] [![][kloudless-img]][kloudless-url] [![][release-history-img]][release-history-url] [![][lightson-img]][lightson-url]

Many thanks to all our [wonderful sponsors][sponsors], and in particular to our premium backers, [Sentry][sentry-url], [Stream][stream-url], [Rollbar][rollbar-url], [Cadre][cadre-url], [Kloudless][kloudless-url], [Release History][release-history-url], and [Lights On Software][lightson-url].


Overview

Django REST framework is a powerful and flexible toolkit for building Web APIs.

Some reasons you might want to use REST framework:

  • The [Web browsable API][sandbox] is a huge usability win for your developers.
  • [Authentication policies][authentication] including optional packages for [OAuth1a][oauth1-section] and [OAuth2][oauth2-section].
  • [Serialization][serializers] that supports both [ORM][modelserializer-section] and [non-ORM][serializer-section] data sources.
  • Customizable all the way down - just use [regular function-based views][functionview-section] if you don't need the [more][generic-views] [powerful][viewsets] [features][routers].
  • [Extensive documentation][docs], and [great community support][group].

There is a live example API for testing purposes, [available here][sandbox].

Below: Screenshot from the browsable API Funding

REST framework is a collaboratively funded project. If you use REST framework commercially we strongly encourage you to invest in its continued development by signing up for a paid plan.

The initial aim is to provide a single full-time position on REST framework. Every single sign-up makes a significant impact on making that possible.

Many thanks to all our wonderful sponsors, and in particular to our premium backers, Sentry, Stream, Rollbar, Cadre, Kloudless, Release History, and Lights On Software. Overview

Django REST framework is a powerful and flexible toolkit for building Web APIs.

Some reasons you might want to use REST framework:

The Web-browsable API is a huge usability win for your developers.
Authentication policies including optional packages for OAuth1a and OAuth2.
Serialization that supports both ORM and non-ORM data sources.
Customizable all the way down - just use regular function-based views if you don't need the more powerful features.
Extensive documentation, and great community support.

There is a live example API for testing purposes, available here.

Below: Screenshot from the browsable API

Screenshot Requirements

Python (2.7, 3.4, 3.5, 3.6, 3.7)
Django (1.11, 2.0, 2.1, 2.2)

We highly recommend and only officially support the latest patch release of each Python and Django series. Installation

Install using pip...

pip install djangorestframework

Add 'rest_framework' to your INSTALLED_APPS setting.

INSTALLED_APPS = ( ... 'rest_framework', )

Example

Let's take a look at a quick example of using REST framework to build a simple model-backed API for accessing users and groups.

Startup up a new project like so...

pip install django pip install djangorestframework django-admin startproject example . ./manage.py migrate ./manage.py createsuperuser

Now edit the example/URLs.py module in your project:

from django.conf.URLs import URL, include from django.contrib.auth.models import User from rest_framework import serializers, view sets, routers

Serializers define the API representation.

class UserSerializer(serializers.HyperlinkedModelSerializer): class Meta: model = User fields = ('url', 'username', 'email', 'is_staff')

ViewSets define the view behavior.

class UserViewSet(viewsets.ModelViewSet): queryset = User.objects.all() serializer_class = UserSerializer

Routers provide a way of automatically determining the URL conf.

router = routers.DefaultRouter() router.register(r'users', UserViewSet)

Wire up our API using automatic URL routing.

Additionally, we include login URLs for the browsable API.

URL patterns = [ url(r'^', include(router.urls)), url(r'^api-auth/', include('rest_framework.urls', namespace='rest_framework')) ]

We'd also like to configure a couple of settings for our API.

Add the following to your settings.py module:

INSTALLED_APPS = ( ... # Make sure to include the default installed apps here. 'rest_framework', )

REST_FRAMEWORK = { # Use Django's standard django.contrib.auth permissions, # or allow read-only access for unauthenticated users. 'DEFAULT_PERMISSION_CLASSES': [ 'rest_framework.permissions.DjangoModelPermissionsOrAnonReadOnly' ] }

That's it, we're done!

./manage.py runserver

You can now open the API in your browser at http://127.0.0.1:8000/, and view your new 'users' API. If you use the Login control in the top right corner you'll also be able to add, create and delete users from the system.

You can also interact with the API using command line tools such as curl. For example, to list the user's endpoint:

$ curl -H 'Accept: application/json; indent=4' -u admin:password http://127.0.0.1:8000/users/ [ { "url": "http://127.0.0.1:8000/users/1/", "username": "admin", "email": "admin@example.com", "is_staff": true, } ]

Or to create a new user:

$ curl -X POST -d username=new -d email=new@example.com -d is_staff=false -H 'Accept: application/json; indent=4' -u admin:password http://127.0.0.1:8000/users/ { "url": "http://127.0.0.1:8000/users/2/", "username": "new", "email": "new@example.com", "is_staff": false, }

Documentation & Support

Full documentation for the project is available at https://www.django-rest-framework.org/.

For questions and support, use the REST framework discussion group, or #restframework on Freenode IRC.

You may also want to follow the author on Twitter. Security

If you believe you've found something in Django REST framework which has security implications, please do not raise the issue in a public forum.

Send a description of the issue via email to rest-framework-security@googlegroups.com. The project maintainers will then work with you to resolve any issues where required, prior to any public disclosure.