Web APIs for Django. 🎸
Go to file
Thodoris Sotiropoulos 4c2d6b9bb7 Do not ignore source when building fields dynamically
This commit fixes the issue when you set the keyword argument `source`
and your have not set the serializer fields explicitly. Then the
construction of field failed because there is not actually any model
field with that name.

However, you are still able to imply the name of model field by
providing the `source` keyword argument.
2016-11-17 18:51:22 +02:00
.tx Update config 2015-12-15 15:22:19 +08:00
docs Correct a small typo in exceptions documentation 2016-11-14 16:58:16 +00:00
docs_theme Funding announcement (#4147) 2016-05-26 11:48:15 +01:00
requirements Deprecate DjangoFilter backend (#4593) 2016-10-20 10:47:09 +01:00
rest_framework Do not ignore source when building fields dynamically 2016-11-17 18:51:22 +02:00
tests Invalidate any existing prefetch cache on PUT requests. (#4668) 2016-11-11 09:44:35 +00:00
.gitignore Fix warnings when running tests (#4047) 2016-04-11 14:13:11 +01:00
.isort.cfg Add types to isort's standard library list. 2015-11-26 15:42:49 +02:00
.travis.yml Version 3.5 (#4525) 2016-10-10 13:03:46 +01:00
CONTRIBUTING.md contributing.md django fix. (#4581) 2016-10-14 11:20:09 +01:00
ISSUE_TEMPLATE.md Create issue and pull request templates 2016-02-22 11:17:02 -04:00
LICENSE.md Update license year range to 2016 2016-01-18 12:28:24 +05:30
MANIFEST.in Separate LICENSE and README to two files. 2015-05-05 14:48:30 +02:00
mkdocs.yml Version 3.5.0 (#4596) 2016-10-20 16:25:40 +01:00
PULL_REQUEST_TEMPLATE.md Create issue and pull request templates 2016-02-22 11:17:02 -04:00
README.md Update sponsor info [ci skip] 2016-08-25 22:27:51 +01:00
requirements.txt Fix typos in comments 2015-08-19 03:55:39 +02:00
runtests.py Schemas & client libraries. (#4179) 2016-07-04 16:38:17 +01:00
setup.cfg Add LICENSE.md to the built wheel (#4270) 2016-07-18 16:08:44 +01:00
setup.py Adds Django/Python Trove Classifiers (#4662) 2016-11-09 12:59:11 +00:00
tox.ini Update versions of Django on tox.ini (#4651) 2016-11-07 11:37:58 +00:00

Django REST framework

build-status-image coverage-status-image pypi-version Gitter

Awesome web-browsable Web APIs.

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


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 towards making that possible.

Many thanks to all our wonderful sponsors, and in particular to our premium backers, Rover, Sentry, Stream, and Machinalis.


Overview

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

Some reasons you might want to use REST framework:

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

Below: Screenshot from the browsable API

Screenshot

Requirements

  • Python (2.7, 3.2, 3.3, 3.4, 3.5)
  • Django (1.8, 1.9, 1.10)

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.py 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, viewsets, 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.
urlpatterns = [
    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 users 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 http://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.