Natosha McDade, Yassin Mohamed, Finan H. Berhe, Sean Reed, Steven Demarco Taylor, Breonna Taylor, Ariane McCree, Terrance Franklin, Miles Hall, Darius Tarver, William Green, Samuel David Mallard, Kwame Jones, De’von Bailey, Christopher Whitfield, Anthony Hill, De’Von Bailey, Eric Logan, Jamarion Robinson, Gregory Hill Jr, JaQuavion Slaton, Ryan Twyman, Brandon Webber, Jimmy Atchison, Willie McCoy, Emantic Fitzgerald Bradford J, D’ettrick Griffin, Jemel Roberson, DeAndre Ballard, Botham Shem Jean, Robert Lawrence White, Anthony Lamar Smith, Ramarley Graham, Manuel Loggins Jr, Trayvon Martin, Wendell Allen, Kendrec McDade, Larry Jackson Jr, Jonathan Ferrell, Jordan Baker, Victor White III, Dontre Hamilton, Eric Garner, John Crawford III, Michael Brown, Ezell Ford, Dante Parker, Kajieme Powell, Laquan McDonald, Akai Gurley, Tamir Rice, Rumain Brisbon, Jerame Reid, Charly Keunang, Tony Robinson, Walter Scott, Freddie Gray, Brendon Glenn, Samuel DuBose, Christian Taylor, Jamar Clark, Mario Woods, Quintonio LeGrier, Gregory Gunn, Akiel Denkins, Alton Sterling, Philando Castile, Terrence Sterling, Terence Crutcher, Keith Lamont Scott, Alfred Olango, Jordan Edwards, Stephon Clark, Danny Ray Thomas, DeJuan Guillory, Patrick Harmon, Jonathan Hart, Maurice Granton, Julius Johnson, Jamee Johnson, Michael Dean...
Authentication is the mechanism of associating an incoming request with a set of identifying credentials, such as the user the request came from, or the token that it was signed with. The permission and throttling policies can then use those credentials to determine if the request should be permitted.
+
REST framework provides a number of authentication schemes out of the box, and also allows you to implement custom schemes.
+
Authentication is always run at the very start of the view, before the permission and throttling checks occur, and before any other code is allowed to proceed.
+
The request.user property will typically be set to an instance of the contrib.auth package's User class.
+
The request.auth property is used for any additional authentication information, for example, it may be used to represent an authentication token that the request was signed with.
+
+
Note: Don't forget that authentication by itself won't allow or disallow an incoming request, it simply identifies the credentials that the request was made with.
+
For information on how to setup the permission polices for your API please see the permissions documentation.
The authentication schemes are always defined as a list of classes. REST framework will attempt to authenticate with each class in the list, and will set request.user and request.auth using the return value of the first class that successfully authenticates.
+
If no class authenticates, request.user will be set to an instance of django.contrib.auth.models.AnonymousUser, and request.auth will be set to None.
+
The value of request.user and request.auth for unauthenticated requests can be modified using the UNAUTHENTICATED_USER and UNAUTHENTICATED_TOKEN settings.
HTTP 401 responses must always include a WWW-Authenticate header, that instructs the client how to authenticate. HTTP 403 responses do not include the WWW-Authenticate header.
+
The kind of response that will be used depends on the authentication scheme. Although multiple authentication schemes may be in use, only one scheme may be used to determine the type of response. The first authentication class set on the view is used when determining the type of response.
+
Note that when a request may successfully authenticate, but still be denied permission to perform the request, in which case a 403 Permission Denied response will always be used, regardless of the authentication scheme.
Note that if deploying to Apache using mod_wsgi, the authorization header is not passed through to a WSGI application by default, as it is assumed that authentication will be handled by Apache, rather than at an application level.
+
If you are deploying to Apache, and using any non-session based authentication, you will need to explicitly configure mod_wsgi to pass the required headers through to the application. This can be done by specifying the WSGIPassAuthorization directive in the appropriate context and setting it to 'On'.
+
# this can go in either server config, virtual host, directory or .htaccess
+WSGIPassAuthorization On
+
This authentication scheme uses HTTP Basic Authentication, signed against a user's username and password. Basic authentication is generally only appropriate for testing.
+
If successfully authenticated, BasicAuthentication provides the following credentials.
+
+
request.user will be a Django User instance.
+
request.auth will be None.
+
+
Unauthenticated responses that are denied permission will result in an HTTP 401 Unauthorized response with an appropriate WWW-Authenticate header. For example:
+
WWW-Authenticate: Basic realm="api"
+
+
Note: If you use BasicAuthentication in production you must ensure that your API is only available over https. You should also ensure that your API clients will always re-request the username and password at login, and will never store those details to persistent storage.
This authentication scheme uses a simple token-based HTTP Authentication scheme. Token authentication is appropriate for client-server setups, such as native desktop and mobile clients.
+
To use the TokenAuthentication scheme you'll need to configure the authentication classes to include TokenAuthentication, and additionally include rest_framework.authtoken in your INSTALLED_APPS setting:
Note: Make sure to run manage.py migrate after changing your settings. The rest_framework.authtoken app provides Django database migrations.
+
+
You'll also need to create tokens for your users.
+
from rest_framework.authtoken.models import Token
+
+token = Token.objects.create(user=...)
+print(token.key)
+
+
For clients to authenticate, the token key should be included in the Authorization HTTP header. The key should be prefixed by the string literal "Token", with whitespace separating the two strings. For example:
Note: If you want to use a different keyword in the header, such as Bearer, simply subclass TokenAuthentication and set the keyword class variable.
+
If successfully authenticated, TokenAuthentication provides the following credentials.
+
+
request.user will be a Django User instance.
+
request.auth will be a rest_framework.authtoken.models.Token instance.
+
+
Unauthenticated responses that are denied permission will result in an HTTP 401 Unauthorized response with an appropriate WWW-Authenticate header. For example:
+
WWW-Authenticate: Token
+
+
The curl command line tool may be useful for testing token authenticated APIs. For example:
+
curl -X GET http://127.0.0.1:8000/api/example/ -H 'Authorization: Token 9944b09199c62bcf9418ad846dd0e4bbdfc6ee4b'
+
+
+
Note: If you use TokenAuthentication in production you must ensure that your API is only available over https.
Note that you'll want to ensure you place this code snippet in an installed models.py module, or some other location that will be imported by Django on startup.
+
If you've already created some users, you can generate tokens for all existing users like this:
+
from django.contrib.auth.models import User
+from rest_framework.authtoken.models import Token
+
+for user in User.objects.all():
+ Token.objects.get_or_create(user=user)
+
When using TokenAuthentication, you may want to provide a mechanism for clients to obtain a token given the username and password. REST framework provides a built-in view to provide this behavior. To use it, add the obtain_auth_token view to your URLconf:
Note that the default obtain_auth_token view explicitly uses JSON requests and responses, rather than using default renderer and parser classes in your settings.
+
By default there are no permissions or throttling applied to the obtain_auth_token view. If you do wish to apply throttling you'll need to override the view class,
+and include them using the throttle_classes attribute.
+
If you need a customized version of the obtain_auth_token view, you can do so by subclassing the ObtainAuthToken view class, and using that in your url conf instead.
+
For example, you may return additional user information beyond the token value:
It is also possible to create Tokens manually through admin interface. In case you are using a large user base, we recommend that you monkey patch the TokenAdmin class to customize it to your needs, more specifically by declaring the user field as raw_field.
+
your_app/admin.py:
+
from rest_framework.authtoken.admin import TokenAdmin
+
+TokenAdmin.raw_id_fields = ['user']
+
This authentication scheme uses Django's default session backend for authentication. Session authentication is appropriate for AJAX clients that are running in the same session context as your website.
+
If successfully authenticated, SessionAuthentication provides the following credentials.
+
+
request.user will be a Django User instance.
+
request.auth will be None.
+
+
Unauthenticated responses that are denied permission will result in an HTTP 403 Forbidden response.
+
If you're using an AJAX style API with SessionAuthentication, you'll need to make sure you include a valid CSRF token for any "unsafe" HTTP method calls, such as PUT, PATCH, POST or DELETE requests. See the Django CSRF documentation for more details.
+
Warning: Always use Django's standard login view when creating login pages. This will ensure your login views are properly protected.
+
CSRF validation in REST framework works slightly differently to standard Django due to the need to support both session and non-session based authentication to the same views. This means that only authenticated requests require CSRF tokens, and anonymous requests may be sent without CSRF tokens. This behaviour is not suitable for login views, which should always have CSRF validation applied.
This authentication scheme allows you to delegate authentication to your web server, which sets the REMOTE_USER
+environment variable.
+
To use it, you must have django.contrib.auth.backends.RemoteUserBackend (or a subclass) in your
+AUTHENTICATION_BACKENDS setting. By default, RemoteUserBackend creates User objects for usernames that don't
+already exist. To change this and other behaviour, consult the
+Django documentation.
+
If successfully authenticated, RemoteUserAuthentication provides the following credentials:
+
+
request.user will be a Django User instance.
+
request.auth will be None.
+
+
Consult your web server's documentation for information about configuring an authentication method, e.g.:
To implement a custom authentication scheme, subclass BaseAuthentication and override the .authenticate(self, request) method. The method should return a two-tuple of (user, auth) if authentication succeeds, or None otherwise.
+
In some circumstances instead of returning None, you may want to raise an AuthenticationFailed exception from the .authenticate() method.
+
Typically the approach you should take is:
+
+
If authentication is not attempted, return None. Any other authentication schemes also in use will still be checked.
+
If authentication is attempted but fails, raise a AuthenticationFailed exception. An error response will be returned immediately, regardless of any permissions checks, and without checking any other authentication schemes.
+
+
You may also override the .authenticate_header(self, request) method. If implemented, it should return a string that will be used as the value of the WWW-Authenticate header in a HTTP 401 Unauthorized response.
+
If the .authenticate_header() method is not overridden, the authentication scheme will return HTTP 403 Forbidden responses when an unauthenticated request is denied access.
+
+
Note: When your custom authenticator is invoked by the request object's .user or .auth properties, you may see an AttributeError re-raised as a WrappedAttributeError. This is necessary to prevent the original exception from being suppressed by the outer property access. Python will not recognize that the AttributeError originates from your custom authenticator and will instead assume that the request object does not have a .user or .auth property. These errors should be fixed or otherwise handled by your authenticator.
The Django OAuth Toolkit package provides OAuth 2.0 support and works with Python 3.4+. The package is maintained by Evonove and uses the excellent OAuthLib. The package is well documented, and well supported and is currently our recommended package for OAuth 2.0 support.
JSON Web Token is a fairly new standard which can be used for token-based authentication. Unlike the built-in TokenAuthentication scheme, JWT Authentication doesn't need to use a database to validate a token. A package for JWT authentication is djangorestframework-simplejwt which provides some features as well as a pluggable token blacklist app.
The HawkREST library builds on the Mohawk library to let you work with Hawk signed requests and responses in your API. Hawk lets two parties securely communicate with each other using messages signed by a shared key. It is based on HTTP MAC access authentication (which was based on parts of OAuth 1.0).
Djoser library provides a set of views to handle basic actions such as registration, login, logout, password reset and account activation. The package works with a custom user model and it uses token based authentication. This is a ready to use REST implementation of Django authentication system.
Django-rest-auth library provides a set of REST API endpoints for registration, authentication (including social media authentication), password reset, retrieve and update user details, etc. By having these API endpoints, your client apps such as AngularJS, iOS, Android, and others can communicate to your Django backend site independently via REST APIs for user management.
Django-rest-framework-social-oauth2 library provides an easy way to integrate social plugins (facebook, twitter, google, etc.) to your authentication system and an easy oauth2 setup. With this library, you will be able to authenticate users based on external tokens (e.g. facebook access token), convert these tokens to "in-house" oauth2 tokens and use and generate oauth2 tokens to authenticate your users.
Django-rest-knox library provides models and views to handle token based authentication in a more secure and extensible way than the built-in TokenAuthentication scheme - with Single Page Applications and Mobile clients in mind. It provides per-client tokens, and views to generate them when provided some other authentication (usually basic authentication), to delete the token (providing a server enforced logout) and to delete all tokens (logs out all clients that a user is logged into).
drfpasswordless adds (Medium, Square Cash inspired) passwordless support to Django REST Framework's own TokenAuthentication scheme. Users log in and sign up with a token sent to a contact point like an email address or a mobile number.
Django provides a method_decorator to use
+decorators with class based views. This can be used with
+other cache decorators such as cache_page and
+vary_on_cookie.
HTTP has provisions for several mechanisms for "content negotiation" - the process of selecting the best representation for a given response when there are multiple representations available.
REST framework uses a simple style of content negotiation to determine which media type should be returned to a client, based on the available renderers, the priorities of each of those renderers, and the client's Accept: header. The style used is partly client-driven, and partly server-driven.
+
+
More specific media types are given preference to less specific media types.
+
If multiple media types have the same specificity, then preference is given to based on the ordering of the renderers configured for the given view.
The priorities for each of the given media types would be:
+
+
application/json; indent=4
+
application/json, application/yaml and text/html
+
*/*
+
+
If the requested view was only configured with renderers for YAML and HTML, then REST framework would select whichever renderer was listed first in the renderer_classes list or DEFAULT_RENDERER_CLASSES setting.
+
For more information on the HTTP Accept header, see RFC 2616
+
+
Note: "q" values are not taken into account by REST framework when determining preference. The use of "q" values negatively impacts caching, and in the author's opinion they are an unnecessary and overcomplicated approach to content negotiation.
+
This is a valid approach as the HTTP spec deliberately underspecifies how a server should weight server-based preferences against client-based preferences.
It's unlikely that you'll want to provide a custom content negotiation scheme for REST framework, but you can do so if needed. To implement a custom content negotiation scheme override BaseContentNegotiation.
+
REST framework's content negotiation classes handle selection of both the appropriate parser for the request, and the appropriate renderer for the response, so you should implement both the .select_parser(request, parsers) and .select_renderer(request, renderers, format_suffix) methods.
+
The select_parser() method should return one of the parser instances from the list of available parsers, or None if none of the parsers can handle the incoming request.
+
The select_renderer() method should return a two-tuple of (renderer instance, media type), or raise a NotAcceptable exception.
The default content negotiation class may be set globally, using the DEFAULT_CONTENT_NEGOTIATION_CLASS setting. For example, the following settings would use our example IgnoreClientContentNegotiation class.
REST framework's views handle various exceptions, and deal with returning appropriate error responses.
+
The handled exceptions are:
+
+
Subclasses of APIException raised inside REST framework.
+
Django's Http404 exception.
+
Django's PermissionDenied exception.
+
+
In each case, REST framework will return a response with an appropriate status code and content-type. The body of the response will include any additional details regarding the nature of the error.
+
Most error responses will include a key detail in the body of the response.
Might receive an error response indicating that the DELETE method is not allowed on that resource:
+
HTTP/1.1 405 Method Not Allowed
+Content-Type: application/json
+Content-Length: 42
+
+{"detail": "Method 'DELETE' not allowed."}
+
+
Validation errors are handled slightly differently, and will include the field names as the keys in the response. If the validation error was not specific to a particular field then it will use the "non_field_errors" key, or whatever string value has been set for the NON_FIELD_ERRORS_KEY setting.
+
Any example validation error might look like this:
+
HTTP/1.1 400 Bad Request
+Content-Type: application/json
+Content-Length: 94
+
+{"amount": ["A valid integer is required."], "description": ["This field may not be blank."]}
+
You can implement custom exception handling by creating a handler function that converts exceptions raised in your API views into response objects. This allows you to control the style of error responses used by your API.
+
The function must take a pair of arguments, the first is the exception to be handled, and the second is a dictionary containing any extra context such as the view currently being handled. The exception handler function should either return a Response object, or return None if the exception cannot be handled. If the handler returns None then the exception will be re-raised and Django will return a standard HTTP 500 'server error' response.
+
For example, you might want to ensure that all error responses include the HTTP status code in the body of the response, like so:
+
HTTP/1.1 405 Method Not Allowed
+Content-Type: application/json
+Content-Length: 62
+
+{"status_code": 405, "detail": "Method 'DELETE' not allowed."}
+
+
In order to alter the style of the response, you could write the following custom exception handler:
+
from rest_framework.views import exception_handler
+
+def custom_exception_handler(exc, context):
+ # Call REST framework's default exception handler first,
+ # to get the standard error response.
+ response = exception_handler(exc, context)
+
+ # Now add the HTTP status code to the response.
+ if response is not None:
+ response.data['status_code'] = response.status_code
+
+ return response
+
+
The context argument is not used by the default handler, but can be useful if the exception handler needs further information such as the view currently being handled, which can be accessed as context['view'].
+
The exception handler must also be configured in your settings, using the EXCEPTION_HANDLER setting key. For example:
Note that the exception handler will only be called for responses generated by raised exceptions. It will not be used for any responses returned directly by the view, such as the HTTP_400_BAD_REQUEST responses that are returned by the generic views when serializer validation fails.
The base class for all exceptions raised inside an APIView class or @api_view.
+
To provide a custom exception, subclass APIException and set the .status_code, .default_detail, and default_code attributes on the class.
+
For example, if your API relies on a third party service that may sometimes be unreachable, you might want to implement an exception for the "503 Service Unavailable" HTTP response code. You could do this like so:
There are a number of different properties available for inspecting the status
+of an API exception. You can use these to build custom exception handling
+for your project.
+
The available attributes and methods are:
+
+
.detail - Return the textual description of the error.
+
.get_codes() - Return the code identifier of the error.
+
.get_full_details() - Return both the textual description and the code identifier.
+
+
In most cases the error detail will be a simple item:
+
>>> print(exc.detail)
+You do not have permission to perform this action.
+>>> print(exc.get_codes())
+permission_denied
+>>> print(exc.get_full_details())
+{'message':'You do not have permission to perform this action.','code':'permission_denied'}
+
+
In the case of validation errors the error detail will be either a list or
+dictionary of items:
+
>>> print(exc.detail)
+{"name":"This field is required.","age":"A valid integer is required."}
+>>> print(exc.get_codes())
+{"name":"required","age":"invalid"}
+>>> print(exc.get_full_details())
+{"name":{"message":"This field is required.","code":"required"},"age":{"message":"A valid integer is required.","code":"invalid"}}
+
Raised when an incoming request includes incorrect authentication.
+
By default this exception results in a response with the HTTP status code "401 Unauthenticated", but it may also result in a "403 Forbidden" response, depending on the authentication scheme in use. See the authentication documentation for more details.
Raised when an unauthenticated request fails the permission checks.
+
By default this exception results in a response with the HTTP status code "401 Unauthenticated", but it may also result in a "403 Forbidden" response, depending on the authentication scheme in use. See the authentication documentation for more details.
The ValidationError exception is slightly different from the other APIException classes:
+
+
The detail argument is mandatory, not optional.
+
The detail argument may be a list or dictionary of error details, and may also be a nested data structure.
+
By convention you should import the serializers module and use a fully qualified ValidationError style, in order to differentiate it from Django's built-in validation error. For example. raise serializers.ValidationError('This field must be an integer value.')
+
+
The ValidationError class should be used for serializer and field validation, and by validator classes. It is also raised when calling serializer.is_valid with the raise_exception keyword argument:
+
serializer.is_valid(raise_exception=True)
+
+
The generic views use the raise_exception=True flag, which means that you can override the style of validation error responses globally in your API. To do so, use a custom exception handler, as described above.
+
By default this exception results in a response with the HTTP status code "400 Bad Request".
Django REST Framework provides two error views suitable for providing generic JSON 500 Server Error and
+400 Bad Request responses. (Django's default error views provide HTML responses, which may not be appropriate for an
+API-only application.)
Serializer fields handle converting between primitive values and internal datatypes. They also deal with validating input values, as well as retrieving and setting the values from their parent objects.
+
+
Note: The serializer fields are declared in fields.py, but by convention you should import them using from rest_framework import serializers and refer to fields as serializers.<FieldName>.
Each serializer field class constructor takes at least these arguments. Some Field classes take additional, field-specific arguments, but the following should always be accepted:
Read-only fields are included in the API output, but should not be included in the input during create or update operations. Any 'read_only' fields that are incorrectly included in the serializer input will be ignored.
+
Set this to True to ensure that the field is used when serializing a representation, but is not used when creating or updating an instance during deserialization.
Normally an error will be raised if a field is not supplied during deserialization.
+Set to false if this field is not required to be present during deserialization.
+
Setting this to False also allows the object attribute or dictionary key to be omitted from output when serializing the instance. If the key is not present it will simply not be included in the output representation.
If set, this gives the default value that will be used for the field if no input value is supplied. If not set the default behaviour is to not populate the attribute at all.
+
The default is not applied during partial update operations. In the partial update case only fields that are provided in the incoming data will have a validated value returned.
+
May be set to a function or other callable, in which case the value will be evaluated each time it is used. When called, it will receive no arguments. If the callable has a requires_context = True attribute, then the serializer field will be passed as an argument.
+
For example:
+
class CurrentUserDefault:
+ """
+ May be applied as a `default=...` value on a serializer field.
+ Returns the current user.
+ """
+ requires_context = True
+
+ def __call__(self, serializer_field):
+ return serializer_field.context['request'].user
+
+
When serializing the instance, default will be used if the object attribute or dictionary key is not present in the instance.
+
Note that setting a default value implies that the field is not required. Including both the default and required keyword arguments is invalid and will raise an error.
Normally an error will be raised if None is passed to a serializer field. Set this keyword argument to True if None should be considered a valid value.
+
Note that, without an explicit default, setting this argument to True will imply a default value of null for serialization output, but does not imply a default for input deserialization.
The name of the attribute that will be used to populate the field. May be a method that only takes a self argument, such as URLField(source='get_absolute_url'), or may use dotted notation to traverse attributes, such as EmailField(source='user.email'). When serializing fields with dotted notation, it may be necessary to provide a default value if any object is not present or is empty during attribute traversal.
+
The value source='*' has a special meaning, and is used to indicate that the entire object should be passed through to the field. This can be useful for creating nested representations, or for fields which require access to the complete object in order to determine the output representation.
A list of validator functions which should be applied to the incoming field input, and which either raise a validation error or simply return. Validator functions should typically raise serializers.ValidationError, but Django's built-in ValidationError is also supported for compatibility with validators defined in the Django codebase or third party Django packages.
A value that should be used for pre-populating the value of HTML form fields. You may pass a callable to it, just as
+you may do with any regular Django Field:
A dictionary of key-value pairs that can be used to control how renderers should render the field.
+
Two examples here are 'input_type' and 'base_template':
+
# Use <input type="password"> for the input.
+password = serializers.CharField(
+ style={'input_type': 'password'}
+)
+
+# Use a radio input instead of a select input.
+color_channel = serializers.ChoiceField(
+ choices=['red', 'green', 'blue'],
+ style={'base_template': 'radio.html'}
+)
+
+
For more details see the HTML & Forms documentation.
When using HTML encoded form input be aware that omitting a value will always be treated as setting a field to False, even if it has a default=True option specified. This is because HTML checkbox inputs represent the unchecked state by omitting the value, so REST framework treats omission as if it is an empty checkbox input.
+
Note that Django 2.1 removed the blank kwarg from models.BooleanField.
+Prior to Django 2.1 models.BooleanField fields were always blank=True. Thus
+since Django 2.1 default serializers.BooleanField instances will be generated
+without the required kwarg (i.e. equivalent to required=True) whereas with
+previous versions of Django, default BooleanField instances will be generated
+with a required=False option. If you want to control this behaviour manually,
+explicitly declare the BooleanField on the serializer class, or use the
+extra_kwargs option to set the required flag.
+
Corresponds to django.db.models.fields.BooleanField.
max_length - Validates that the input contains no more than this number of characters.
+
min_length - Validates that the input contains no fewer than this number of characters.
+
allow_blank - If set to True then the empty string should be considered a valid value. If set to False then the empty string is considered invalid and will raise a validation error. Defaults to False.
+
trim_whitespace - If set to True then leading and trailing whitespace is trimmed. Defaults to True.
+
+
The allow_null option is also available for string fields, although its usage is discouraged in favor of allow_blank. It is valid to set both allow_blank=True and allow_null=True, but doing so means that there will be two differing types of empty value permissible for string representations, which can lead to data inconsistencies and subtle application bugs.
A field that ensures the input is a valid UUID string. The to_internal_value method will return a uuid.UUID instance. On output the field will return a string in the canonical hyphenated format, for example:
+
"de305d54-75b4-431b-adb2-eb6b9e546013"
+
+
Signature:UUIDField(format='hex_verbose')
+
+
format: Determines the representation format of the uuid value
+
'hex_verbose' - The canonical hex representation, including hyphens: "5ce0e9a5-5ffa-654b-cee0-1238041fb31a"
+
'hex' - The compact hex representation of the UUID, not including hyphens: "5ce0e9a55ffa654bcee01238041fb31a"
+
'int' - A 128 bit integer representation of the UUID: "123456789012312313134124512351145145114"
+
'urn' - RFC 4122 URN representation of the UUID: "urn:uuid:5ce0e9a5-5ffa-654b-cee0-1238041fb31a"
+ Changing the format parameters only affects representation values. All formats are accepted by to_internal_value
protocol Limits valid inputs to the specified protocol. Accepted values are 'both' (default), 'IPv4' or 'IPv6'. Matching is case insensitive.
+
unpack_ipv4 Unpacks IPv4 mapped addresses like ::ffff:192.0.2.1. If this option is enabled that address would be unpacked to 192.0.2.1. Default is disabled. Can only be used when protocol is set to 'both'.
Corresponds to django.db.models.fields.IntegerField, django.db.models.fields.SmallIntegerField, django.db.models.fields.PositiveIntegerField and django.db.models.fields.PositiveSmallIntegerField.
max_digits The maximum number of digits allowed in the number. It must be either None or an integer greater than or equal to decimal_places.
+
decimal_places The number of decimal places to store with the number.
+
coerce_to_string Set to True if string values should be returned for the representation, or False if Decimal objects should be returned. Defaults to the same value as the COERCE_DECIMAL_TO_STRING settings key, which will be True unless overridden. If Decimal objects are returned by the serializer, then the final output format will be determined by the renderer. Note that setting localize will force the value to True.
+
max_value Validate that the number provided is no greater than this value.
+
min_value Validate that the number provided is no less than this value.
+
localize Set to True to enable localization of input and output based on the current locale. This will also force coerce_to_string to True. Defaults to False. Note that data formatting is enabled if you have set USE_L10N=True in your settings file.
+
rounding Sets the rounding mode used when quantising to the configured precision. Valid values are decimal module rounding modes. Defaults to None.
This field also takes an optional argument, coerce_to_string. If set to True the representation will be output as a string. If set to False the representation will be left as a Decimal instance and the final representation will be determined by the renderer.
+
If unset, this will default to the same value as the COERCE_DECIMAL_TO_STRING setting, which is True unless set otherwise.
format - A string representing the output format. If not specified, this defaults to the same value as the DATETIME_FORMAT settings key, which will be 'iso-8601' unless set. Setting to a format string indicates that to_representation return values should be coerced to string output. Format strings are described below. Setting this value to None indicates that Python datetime objects should be returned by to_representation. In this case the datetime encoding will be determined by the renderer.
+
input_formats - A list of strings representing the input formats which may be used to parse the date. If not specified, the DATETIME_INPUT_FORMATS setting will be used, which defaults to ['iso-8601'].
+
default_timezone - A pytz.timezone representing the timezone. If not specified and the USE_TZ setting is enabled, this defaults to the current timezone. If USE_TZ is disabled, then datetime objects will be naive.
Format strings may either be Python strftime formats which explicitly specify the format, or the special string 'iso-8601', which indicates that ISO 8601 style datetimes should be used. (eg '2013-01-29T12:34:56.000000Z')
+
When a value of None is used for the format datetime objects will be returned by to_representation and the final output representation will determined by the renderer class.
When using ModelSerializer or HyperlinkedModelSerializer, note that any model fields with auto_now=True or auto_now_add=True will use serializer fields that are read_only=True by default.
+
If you want to override this behavior, you'll need to declare the DateTimeField explicitly on the serializer. For example:
+
class CommentSerializer(serializers.ModelSerializer):
+ created = serializers.DateTimeField()
+
+ class Meta:
+ model = Comment
+
format - A string representing the output format. If not specified, this defaults to the same value as the DATE_FORMAT settings key, which will be 'iso-8601' unless set. Setting to a format string indicates that to_representation return values should be coerced to string output. Format strings are described below. Setting this value to None indicates that Python date objects should be returned by to_representation. In this case the date encoding will be determined by the renderer.
+
input_formats - A list of strings representing the input formats which may be used to parse the date. If not specified, the DATE_INPUT_FORMATS setting will be used, which defaults to ['iso-8601'].
Format strings may either be Python strftime formats which explicitly specify the format, or the special string 'iso-8601', which indicates that ISO 8601 style dates should be used. (eg '2013-01-29')
format - A string representing the output format. If not specified, this defaults to the same value as the TIME_FORMAT settings key, which will be 'iso-8601' unless set. Setting to a format string indicates that to_representation return values should be coerced to string output. Format strings are described below. Setting this value to None indicates that Python time objects should be returned by to_representation. In this case the time encoding will be determined by the renderer.
+
input_formats - A list of strings representing the input formats which may be used to parse the date. If not specified, the TIME_INPUT_FORMATS setting will be used, which defaults to ['iso-8601'].
Format strings may either be Python strftime formats which explicitly specify the format, or the special string 'iso-8601', which indicates that ISO 8601 style times should be used. (eg '12:34:56.000000')
A Duration representation.
+Corresponds to django.db.models.fields.DurationField
+
The validated_data for these fields will contain a datetime.timedelta instance.
+The representation is a string following this format '[DD] [HH:[MM:]]ss[.uuuuuu]'.
A field that can accept a value out of a limited set of choices.
+
Used by ModelSerializer to automatically generate fields if the corresponding model field includes a choices=… argument.
+
Signature:ChoiceField(choices)
+
+
choices - A list of valid values, or a list of (key, display_name) tuples.
+
allow_blank - If set to True then the empty string should be considered a valid value. If set to False then the empty string is considered invalid and will raise a validation error. Defaults to False.
+
html_cutoff - If set this will be the maximum number of choices that will be displayed by a HTML select drop down. Can be used to ensure that automatically generated ChoiceFields with very large possible selections do not prevent a template from rendering. Defaults to None.
+
html_cutoff_text - If set this will display a textual indicator if the maximum number of items have been cutoff in an HTML select drop down. Defaults to "More than {count} items…"
+
+
Both the allow_blank and allow_null are valid options on ChoiceField, although it is highly recommended that you only use one and not both. allow_blank should be preferred for textual choices, and allow_null should be preferred for numeric or other non-textual choices.
A field that can accept a set of zero, one or many values, chosen from a limited set of choices. Takes a single mandatory argument. to_internal_value returns a set containing the selected values.
+
Signature:MultipleChoiceField(choices)
+
+
choices - A list of valid values, or a list of (key, display_name) tuples.
+
allow_blank - If set to True then the empty string should be considered a valid value. If set to False then the empty string is considered invalid and will raise a validation error. Defaults to False.
+
html_cutoff - If set this will be the maximum number of choices that will be displayed by a HTML select drop down. Can be used to ensure that automatically generated ChoiceFields with very large possible selections do not prevent a template from rendering. Defaults to None.
+
html_cutoff_text - If set this will display a textual indicator if the maximum number of items have been cutoff in an HTML select drop down. Defaults to "More than {count} items…"
+
+
As with ChoiceField, both the allow_blank and allow_null options are valid, although it is highly recommended that you only use one and not both. allow_blank should be preferred for textual choices, and allow_null should be preferred for numeric or other non-textual choices.
The FileField and ImageField classes are only suitable for use with MultiPartParser or FileUploadParser. Most parsers, such as e.g. JSON don't support file uploads.
+Django's regular FILE_UPLOAD_HANDLERS are used for handling uploaded files.
max_length - Designates the maximum length for the file name.
+
allow_empty_file - Designates if empty files are allowed.
+
use_url - If set to True then URL string values will be used for the output representation. If set to False then filename string values will be used for the output representation. Defaults to the value of the UPLOADED_FILES_USE_URL settings key, which is True unless set otherwise.
max_length - Designates the maximum length for the file name.
+
allow_empty_file - Designates if empty files are allowed.
+
use_url - If set to True then URL string values will be used for the output representation. If set to False then filename string values will be used for the output representation. Defaults to the value of the UPLOADED_FILES_USE_URL settings key, which is True unless set otherwise.
+
+
Requires either the Pillow package or PIL package. The Pillow package is recommended, as PIL is no longer actively maintained.
child - A field instance that should be used for validating the objects in the list. If this argument is not provided then objects in the list will not be validated.
+
allow_empty - Designates if empty lists are allowed.
+
min_length - Validates that the list contains no fewer than this number of elements.
+
max_length - Validates that the list contains no more than this number of elements.
+
+
For example, to validate a list of integers you might use something like the following:
child - A field instance that should be used for validating the values in the dictionary. If this argument is not provided then values in the mapping will not be validated.
+
allow_empty - Designates if empty dictionaries are allowed.
+
+
For example, to create a field that validates a mapping of strings to strings, you would write something like this:
+
document = DictField(child=CharField())
+
+
You can also use the declarative style, as with ListField. For example:
+
class DocumentField(DictField):
+ child = CharField()
+
A field class that validates that the incoming data structure consists of valid JSON primitives. In its alternate binary mode, it will represent and validate JSON-encoded binary strings.
+
Signature: JSONField(binary, encoder)
+
+
binary - If set to True then the field will output and validate a JSON encoded string, rather than a primitive data structure. Defaults to False.
+
encoder - Use this JSON encoder to serialize input object. Defaults to None.
The HiddenField class is usually only needed if you have some validation that needs to run based on some pre-provided field values, but you do not want to expose all of those fields to the end user.
+
For further examples on HiddenField see the validators documentation.
A generic field that can be tied to any arbitrary model field. The ModelField class delegates the task of serialization/deserialization to its associated model field. This field can be used to create serializer fields for custom model fields, without having to create a new custom serializer field.
+
This field is used by ModelSerializer to correspond to custom model field classes.
The ModelField class is generally intended for internal use, but can be used by your API if needed. In order to properly instantiate a ModelField, it must be passed a field that is attached to an instantiated model. For example: ModelField(model_field=MyModel()._meta.get_field('custom_field'))
This is a read-only field. It gets its value by calling a method on the serializer class it is attached to. It can be used to add any sort of data to the serialized representation of your object.
method_name - The name of the method on the serializer to be called. If not included this defaults to get_<field_name>.
+
+
The serializer method referred to by the method_name argument should accept a single argument (in addition to self), which is the object being serialized. It should return whatever you want to be included in the serialized representation of the object. For example:
+
from django.contrib.auth.models import User
+from django.utils.timezone import now
+from rest_framework import serializers
+
+class UserSerializer(serializers.ModelSerializer):
+ days_since_joined = serializers.SerializerMethodField()
+
+ class Meta:
+ model = User
+
+ def get_days_since_joined(self, obj):
+ return (now() - obj.date_joined).days
+
If you want to create a custom field, you'll need to subclass Field and then override either one or both of the .to_representation() and .to_internal_value() methods. These two methods are used to convert between the initial datatype, and a primitive, serializable datatype. Primitive datatypes will typically be any of a number, string, boolean, date/time/datetime or None. They may also be any list or dictionary like object that only contains other primitive objects. Other types might be supported, depending on the renderer that you are using.
+
The .to_representation() method is called to convert the initial datatype into a primitive, serializable datatype.
+
The to_internal_value() method is called to restore a primitive datatype into its internal python representation. This method should raise a serializers.ValidationError if the data is invalid.
+
Note that the WritableField class that was present in version 2.x no longer exists. You should subclass Field and override to_internal_value() if the field supports data input.
Let's look at an example of serializing a class that represents an RGB color value:
+
class Color(object):
+ """
+ A color represented in the RGB colorspace.
+ """
+ def __init__(self, red, green, blue):
+ assert(red >= 0 and green >= 0 and blue >= 0)
+ assert(red < 256 and green < 256 and blue < 256)
+ self.red, self.green, self.blue = red, green, blue
+
+class ColorField(serializers.Field):
+ """
+ Color objects are serialized into 'rgb(#, #, #)' notation.
+ """
+ def to_representation(self, value):
+ return "rgb(%d, %d, %d)" % (value.red, value.green, value.blue)
+
+ def to_internal_value(self, data):
+ data = data.strip('rgb(').rstrip(')')
+ red, green, blue = [int(col) for col in data.split(',')]
+ return Color(red, green, blue)
+
+
By default field values are treated as mapping to an attribute on the object. If you need to customize how the field value is accessed and set you need to override .get_attribute() and/or .get_value().
+
As an example, let's create a field that can be used to represent the class name of the object being serialized:
+
class ClassNameField(serializers.Field):
+ def get_attribute(self, instance):
+ # We pass the object instance onto `to_representation`,
+ # not just the field attribute.
+ return instance
+
+ def to_representation(self, value):
+ """
+ Serialize the value's class name.
+ """
+ return value.__class__.__name__
+
Our ColorField class above currently does not perform any data validation.
+To indicate invalid data, we should raise a serializers.ValidationError, like so:
+
def to_internal_value(self, data):
+ if not isinstance(data, str):
+ msg = 'Incorrect type. Expected a string, but got %s'
+ raise ValidationError(msg % type(data).__name__)
+
+ if not re.match(r'^rgb\([0-9]+,[0-9]+,[0-9]+\)$', data):
+ raise ValidationError('Incorrect format. Expected `rgb(#,#,#)`.')
+
+ data = data.strip('rgb(').rstrip(')')
+ red, green, blue = [int(col) for col in data.split(',')]
+
+ if any([col > 255 or col < 0 for col in (red, green, blue)]):
+ raise ValidationError('Value out of range. Must be between 0 and 255.')
+
+ return Color(red, green, blue)
+
+
The .fail() method is a shortcut for raising ValidationError that takes a message string from the error_messages dictionary. For example:
+
default_error_messages = {
+ 'incorrect_type': 'Incorrect type. Expected a string, but got {input_type}',
+ 'incorrect_format': 'Incorrect format. Expected `rgb(#,#,#)`.',
+ 'out_of_range': 'Value out of range. Must be between 0 and 255.'
+}
+
+def to_internal_value(self, data):
+ if not isinstance(data, str):
+ self.fail('incorrect_type', input_type=type(data).__name__)
+
+ if not re.match(r'^rgb\([0-9]+,[0-9]+,[0-9]+\)$', data):
+ self.fail('incorrect_format')
+
+ data = data.strip('rgb(').rstrip(')')
+ red, green, blue = [int(col) for col in data.split(',')]
+
+ if any([col > 255 or col < 0 for col in (red, green, blue)]):
+ self.fail('out_of_range')
+
+ return Color(red, green, blue)
+
+
This style keeps your error messages cleaner and more separated from your code, and should be preferred.
Using a custom field and source='*' we can provide a nested representation of
+the coordinate pair:
+
class CoordinateField(serializers.Field):
+
+ def to_representation(self, value):
+ ret = {
+ "x": value.x_coordinate,
+ "y": value.y_coordinate
+ }
+ return ret
+
+ def to_internal_value(self, data):
+ ret = {
+ "x_coordinate": data["x"],
+ "y_coordinate": data["y"],
+ }
+ return ret
+
+
+class DataPointSerializer(serializers.ModelSerializer):
+ coordinates = CoordinateField(source='*')
+
+ class Meta:
+ model = DataPoint
+ fields = ['label', 'coordinates']
+
+
Note that this example doesn't handle validation. Partly for that reason, in a
+real project, the coordinate nesting might be better handled with a nested serializer
+using source='*', with two IntegerField instances, each with their own source
+pointing to the relevant field.
+
The key points from the example, though, are:
+
+
+
to_representation is passed the entire DataPoint object and must map from that
+to the desired output.
Unless our field is to be read-only, to_internal_value must map back to a dict
+suitable for updating our target object. With source='*', the return from
+to_internal_value will update the root validated data dictionary, rather than a single key.
For completeness lets do the same thing again but with the nested serializer
+approach suggested above:
+
class NestedCoordinateSerializer(serializers.Serializer):
+ x = serializers.IntegerField(source='x_coordinate')
+ y = serializers.IntegerField(source='y_coordinate')
+
+
+class DataPointSerializer(serializers.ModelSerializer):
+ coordinates = NestedCoordinateSerializer(source='*')
+
+ class Meta:
+ model = DataPoint
+ fields = ['label', 'coordinates']
+
+
Here the mapping between the target and source attribute pairs (x and
+x_coordinate, y and y_coordinate) is handled in the IntegerField
+declarations. It's our NestedCoordinateSerializer that takes source='*'.
+
Our new DataPointSerializer exhibits the same behaviour as the custom field
+approach.
For this reason, the nested serializer approach would be the first to try. You
+would use the custom field approach when the nested serializer becomes infeasible
+or overly complex.
The drf-compound-fields package provides "compound" serializer fields, such as lists of simple values, which can be described by other fields rather than serializers with the many=True option. Also provided are fields for typed dictionaries and values that can be either a specific type or a list of items of that type.
The root QuerySet provided by the Manager describes all objects in the database table. Usually, though, you'll need to select only a subset of the complete set of objects.
The default behavior of REST framework's generic list views is to return the entire queryset for a model manager. Often you will want your API to restrict the items that are returned by the queryset.
+
The simplest way to filter the queryset of any view that subclasses GenericAPIView is to override the .get_queryset() method.
+
Overriding this method allows you to customize the queryset returned by the view in a number of different ways.
You might want to filter the queryset to ensure that only results relevant to the currently authenticated user making the request are returned.
+
You can do so by filtering based on the value of request.user.
+
For example:
+
from myapp.models import Purchase
+from myapp.serializers import PurchaseSerializer
+from rest_framework import generics
+
+class PurchaseList(generics.ListAPIView):
+ serializer_class = PurchaseSerializer
+
+ def get_queryset(self):
+ """
+ This view should return a list of all the purchases
+ for the currently authenticated user.
+ """
+ user = self.request.user
+ return Purchase.objects.filter(purchaser=user)
+
You could then write a view that returned a purchase queryset filtered by the username portion of the URL:
+
class PurchaseList(generics.ListAPIView):
+ serializer_class = PurchaseSerializer
+
+ def get_queryset(self):
+ """
+ This view should return a list of all the purchases for
+ the user as determined by the username portion of the URL.
+ """
+ username = self.kwargs['username']
+ return Purchase.objects.filter(purchaser__username=username)
+
A final example of filtering the initial queryset would be to determine the initial queryset based on query parameters in the url.
+
We can override .get_queryset() to deal with URLs such as http://example.com/api/purchases?username=denvercoder9, and filter the queryset only if the username parameter is included in the URL:
+
class PurchaseList(generics.ListAPIView):
+ serializer_class = PurchaseSerializer
+
+ def get_queryset(self):
+ """
+ Optionally restricts the returned purchases to a given user,
+ by filtering against a `username` query parameter in the URL.
+ """
+ queryset = Purchase.objects.all()
+ username = self.request.query_params.get('username', None)
+ if username is not None:
+ queryset = queryset.filter(purchaser__username=username)
+ return queryset
+
As well as being able to override the default queryset, REST framework also includes support for generic filtering backends that allow you to easily construct complex searches and filters.
+
Generic filters can also present themselves as HTML controls in the browsable API and admin API.
Note that if a filter backend is configured for a view, then as well as being used to filter list views, it will also be used to filter the querysets used for returning a single object.
+
For instance, given the previous example, and a product with an id of 4675, the following URL would either return the corresponding object, or return a 404 response, depending on if the filtering conditions were met by the given product instance:
Note that you can use both an overridden .get_queryset() and generic filtering together, and everything will work as expected. For example, if Product had a many-to-many relationship with User, named purchase, you might want to write a view like this:
+
class PurchasedProductsList(generics.ListAPIView):
+ """
+ Return a list of all the products that the authenticated
+ user has ever purchased, with optional filtering.
+ """
+ model = Product
+ serializer_class = ProductSerializer
+ filterset_class = ProductFilter
+
+ def get_queryset(self):
+ user = self.request.user
+ return user.purchase_set.all()
+
If all you need is simple equality-based filtering, you can set a filterset_fields attribute on the view, or viewset, listing the set of fields you wish to filter against.
For more advanced filtering requirements you can specify a FilterSet class that should be used by the view.
+You can read more about FilterSets in the django-filter documentation.
+It's also recommended that you read the section on DRF integration.
When in use, the browsable API will include a SearchFilter control:
+
+
The SearchFilter class will only be applied if the view has a search_fields attribute set. The search_fields attribute should be a list of names of text type fields on the model, such as CharField or TextField.
By default, searches will use case-insensitive partial matches. The search parameter may contain multiple search terms, which should be whitespace and/or comma separated. If multiple search terms are used then objects will be returned in the list only if all the provided terms are matched.
+
The search behavior may be restricted by prepending various characters to the search_fields.
+
+
'^' Starts-with search.
+
'=' Exact matches.
+
'@' Full-text search. (Currently only supported Django's MySQL backend.)
+
'$' Regex search.
+
+
For example:
+
search_fields = ['=username', '=email']
+
+
By default, the search parameter is named 'search', but this may be overridden with the SEARCH_PARAM setting.
+
To dynamically change search fields based on request content, it's possible to subclass the SearchFilter and override the get_search_fields() function. For example, the following subclass will only search on title if the query parameter title_only is in the request:
It's recommended that you explicitly specify which fields the API should allowing in the ordering filter. You can do this by setting an ordering_fields attribute on the view, like so:
This helps prevent unexpected data leakage, such as allowing users to order against a password hash field or other sensitive data.
+
If you don't specify an ordering_fields attribute on the view, the filter class will default to allowing the user to filter on any readable fields on the serializer specified by the serializer_class attribute.
+
If you are confident that the queryset being used by the view doesn't contain any sensitive data, you can also explicitly specify that a view should allow ordering on any model field or queryset aggregate, by using the special value '__all__'.
If an ordering attribute is set on the view, this will be used as the default ordering.
+
Typically you'd instead control this by setting order_by on the initial queryset, but using the ordering parameter on the view allows you to specify the ordering in a way that it can then be passed automatically as context to a rendered template. This makes it possible to automatically render column headers differently if they are being used to order the results.
You can also provide your own generic filtering backend, or write an installable app for other developers to use.
+
To do so override BaseFilterBackend, and override the .filter_queryset(self, request, queryset, view) method. The method should return a new, filtered queryset.
+
As well as allowing clients to perform searches and filtering, generic filter backends can be useful for restricting which objects should be visible to any given request or user.
For example, you might need to restrict users to only being able to see objects they created.
+
class IsOwnerFilterBackend(filters.BaseFilterBackend):
+ """
+ Filter that only allows users to see their own objects.
+ """
+ def filter_queryset(self, request, queryset, view):
+ return queryset.filter(owner=request.user)
+
+
We could achieve the same behavior by overriding get_queryset() on the views, but using a filter backend allows you to more easily add this restriction to multiple views, or to apply it across the entire API.
Generic filters may also present an interface in the browsable API. To do so you should implement a to_html() method which returns a rendered HTML representation of the filter. This method should have the following signature:
You can also make the filter controls available to the schema autogeneration
+that REST framework provides, by implementing a get_schema_fields() method. This method should have the following signature:
+
get_schema_fields(self, view)
+
The method should return a list of coreapi.Field instances.
The django-rest-framework-filters package works together with the DjangoFilterBackend class, and allows you to easily create filters across relationships, or create multiple filter lookup types for a given field.
django-url-filter provides a safe way to filter data via human-friendly URLs. It works very similar to DRF serializers and fields in a sense that they can be nested except they are called filtersets and filters. That provides easy way to filter related data. Also this library is generic-purpose so it can be used to filter other sources of data and not only Django QuerySets.
drf-url-filter is a simple Django app to apply filters on drf ModelViewSet's Queryset in a clean, simple and configurable way. It also supports validations on incoming query params and their values. A beautiful python package Voluptuous is being used for validations on the incoming query parameters. The best part about voluptuous is you can define your own validations as per your query params requirements.
A common pattern for Web APIs is to use filename extensions on URLs to provide an endpoint for a given media type. For example, 'http://example.com/api/users.json' to serve a JSON representation.
+
Adding format-suffix patterns to each individual entry in the URLconf for your API is error-prone and non-DRY, so REST framework provides a shortcut to adding these patterns to your URLConf.
Returns a URL pattern list which includes format suffix patterns appended to each of the URL patterns provided.
+
Arguments:
+
+
urlpatterns: Required. A URL pattern list.
+
suffix_required: Optional. A boolean indicating if suffixes in the URLs should be optional or mandatory. Defaults to False, meaning that suffixes are optional by default.
+
allowed: Optional. A list or tuple of valid format suffixes. If not provided, a wildcard format suffix pattern will be used.
If using the i18n_patterns function provided by Django, as well as format_suffix_patterns you should make sure that the i18n_patterns function is applied as the final, or outermost function. For example:
An alternative to the format suffixes is to include the requested format in a query parameter. REST framework provides this option by default, and it is used in the browsable API to switch between differing available representations.
+
To select a representation using its short format, use the format query parameter. For example: http://example.com/organizations/?format=csv.
+
The name of this query parameter can be modified using the URL_FORMAT_OVERRIDE setting. Set the value to None to disable this behavior.
There seems to be a view among some of the Web community that filename extensions are not a RESTful pattern, and that HTTP Accept headers should always be used instead.
+
It is actually a misconception. For example, take the following quote from Roy Fielding discussing the relative merits of query parameter media-type indicators vs. file extension media-type indicators:
+
“That's why I always prefer extensions. Neither choice has anything to do with REST.” — Roy Fielding, REST discuss mailing list
+
The quote does not mention Accept headers, but it does make it clear that format suffixes should be considered an acceptable pattern.
Django’s generic views... were developed as a shortcut for common usage patterns... They take certain common idioms and patterns found in view development and abstract them so that you can quickly write common views of data without having to repeat yourself.
One of the key benefits of class-based views is the way they allow you to compose bits of reusable behavior. REST framework takes advantage of this by providing a number of pre-built views that provide for commonly used patterns.
+
The generic views provided by REST framework allow you to quickly build API views that map closely to your database models.
+
If the generic views don't suit the needs of your API, you can drop down to using the regular APIView class, or reuse the mixins and base classes used by the generic views to compose your own set of reusable generic views.
For more complex cases you might also want to override various methods on the view class. For example.
+
class UserList(generics.ListCreateAPIView):
+ queryset = User.objects.all()
+ serializer_class = UserSerializer
+ permission_classes = [IsAdminUser]
+
+ def list(self, request):
+ # Note the use of `get_queryset()` instead of `self.queryset`
+ queryset = self.get_queryset()
+ serializer = UserSerializer(queryset, many=True)
+ return Response(serializer.data)
+
+
For very simple cases you might want to pass through any class attributes using the .as_view() method. For example, your URLconf might include something like the following entry:
The following attributes control the basic view behavior.
+
+
queryset - The queryset that should be used for returning objects from this view. Typically, you must either set this attribute, or override the get_queryset() method. If you are overriding a view method, it is important that you call get_queryset() instead of accessing this property directly, as queryset will get evaluated once, and those results will be cached for all subsequent requests.
+
serializer_class - The serializer class that should be used for validating and deserializing input, and for serializing output. Typically, you must either set this attribute, or override the get_serializer_class() method.
+
lookup_field - The model field that should be used to for performing object lookup of individual model instances. Defaults to 'pk'. Note that when using hyperlinked APIs you'll need to ensure that both the API views and the serializer classes set the lookup fields if you need to use a custom value.
+
lookup_url_kwarg - The URL keyword argument that should be used for object lookup. The URL conf should include a keyword argument corresponding to this value. If unset this defaults to using the same value as lookup_field.
+
+
Pagination:
+
The following attributes are used to control pagination when used with list views.
+
+
pagination_class - The pagination class that should be used when paginating list results. Defaults to the same value as the DEFAULT_PAGINATION_CLASS setting, which is 'rest_framework.pagination.PageNumberPagination'. Setting pagination_class=None will disable pagination on this view.
+
+
Filtering:
+
+
filter_backends - A list of filter backend classes that should be used for filtering the queryset. Defaults to the same value as the DEFAULT_FILTER_BACKENDS setting.
Returns the queryset that should be used for list views, and that should be used as the base for lookups in detail views. Defaults to returning the queryset specified by the queryset attribute.
+
This method should always be used rather than accessing self.queryset directly, as self.queryset gets evaluated only once, and those results are cached for all subsequent requests.
+
May be overridden to provide dynamic behavior, such as returning a queryset, that is specific to the user making the request.
+
For example:
+
def get_queryset(self):
+ user = self.request.user
+ return user.accounts.all()
+
Note that if your API doesn't include any object level permissions, you may optionally exclude the self.check_object_permissions, and simply return the object from the get_object_or_404 lookup.
Returns the class that should be used for the serializer. Defaults to returning the serializer_class attribute.
+
May be overridden to provide dynamic behavior, such as using different serializers for read and write operations, or providing different serializers to different types of users.
The following methods are provided by the mixin classes, and provide easy overriding of the object save or deletion behavior.
+
+
perform_create(self, serializer) - Called by CreateModelMixin when saving a new object instance.
+
perform_update(self, serializer) - Called by UpdateModelMixin when saving an existing object instance.
+
perform_destroy(self, instance) - Called by DestroyModelMixin when deleting an object instance.
+
+
These hooks are particularly useful for setting attributes that are implicit in the request, but are not part of the request data. For instance, you might set an attribute on the object based on the request user, or based on a URL keyword argument.
These override points are also particularly useful for adding behavior that occurs before or after saving an object, such as emailing a confirmation, or logging the update.
You can also use these hooks to provide additional validation, by raising a ValidationError(). This can be useful if you need some validation logic to apply at the point of database save. For example:
+
def perform_create(self, serializer):
+ queryset = SignupRequest.objects.filter(user=self.request.user)
+ if queryset.exists():
+ raise ValidationError('You have already signed up')
+ serializer.save(user=self.request.user)
+
+
Note: These methods replace the old-style version 2.x pre_save, post_save, pre_delete and post_delete methods, which are no longer available.
+
Other methods:
+
You won't typically need to override the following methods, although you might need to call into them if you're writing custom views using GenericAPIView.
+
+
get_serializer_context(self) - Returns a dictionary containing any extra context that should be supplied to the serializer. Defaults to including 'request', 'view' and 'format' keys.
+
get_serializer(self, instance=None, data=None, many=False, partial=False) - Returns a serializer instance.
+
get_paginated_response(self, data) - Returns a paginated style Response object.
+
paginate_queryset(self, queryset) - Paginate a queryset if required, either returning a page object, or None if pagination is not configured for this view.
+
filter_queryset(self, queryset) - Given a queryset, filter it with whichever filter backends are in use, returning a new queryset.
The mixin classes provide the actions that are used to provide the basic view behavior. Note that the mixin classes provide action methods rather than defining the handler methods, such as .get() and .post(), directly. This allows for more flexible composition of behavior.
+
The mixin classes can be imported from rest_framework.mixins.
Provides a .list(request, *args, **kwargs) method, that implements listing a queryset.
+
If the queryset is populated, this returns a 200 OK response, with a serialized representation of the queryset as the body of the response. The response data may optionally be paginated.
Provides a .create(request, *args, **kwargs) method, that implements creating and saving a new model instance.
+
If an object is created this returns a 201 Created response, with a serialized representation of the object as the body of the response. If the representation contains a key named url, then the Location header of the response will be populated with that value.
+
If the request data provided for creating the object was invalid, a 400 Bad Request response will be returned, with the error details as the body of the response.
Provides a .retrieve(request, *args, **kwargs) method, that implements returning an existing model instance in a response.
+
If an object can be retrieved this returns a 200 OK response, with a serialized representation of the object as the body of the response. Otherwise it will return a 404 Not Found.
Provides a .update(request, *args, **kwargs) method, that implements updating and saving an existing model instance.
+
Also provides a .partial_update(request, *args, **kwargs) method, which is similar to the update method, except that all fields for the update will be optional. This allows support for HTTP PATCH requests.
+
If an object is updated this returns a 200 OK response, with a serialized representation of the object as the body of the response.
+
If the request data provided for updating the object was invalid, a 400 Bad Request response will be returned, with the error details as the body of the response.
The following classes are the concrete generic views. If you're using generic views this is normally the level you'll be working at unless you need heavily customized behavior.
+
The view classes can be imported from rest_framework.generics.
Often you'll want to use the existing generic views, but use some slightly customized behavior. If you find yourself reusing some bit of customized behavior in multiple places, you might want to refactor the behavior into a common class that you can then just apply to any view or viewset as needed.
For example, if you need to lookup objects based on multiple fields in the URL conf, you could create a mixin class like the following:
+
class MultipleFieldLookupMixin(object):
+ """
+ Apply this mixin to any view or viewset to get multiple field filtering
+ based on a `lookup_fields` attribute, instead of the default single field filtering.
+ """
+ def get_object(self):
+ queryset = self.get_queryset() # Get the base queryset
+ queryset = self.filter_queryset(queryset) # Apply any filter backends
+ filter = {}
+ for field in self.lookup_fields:
+ if self.kwargs[field]: # Ignore empty fields.
+ filter[field] = self.kwargs[field]
+ obj = get_object_or_404(queryset, **filter) # Lookup the object
+ self.check_object_permissions(self.request, obj)
+ return obj
+
+
You can then simply apply this mixin to a view or viewset anytime you need to apply the custom behavior.
If you are using a mixin across multiple views, you can take this a step further and create your own set of base views that can then be used throughout your project. For example:
Using custom base classes is a good option if you have custom behavior that consistently needs to be repeated across a large number of views throughout your project.
Prior to version 3.0 the REST framework mixins treated PUT as either an update or a create operation, depending on if the object already existed or not.
+
Allowing PUT as create operations is problematic, as it necessarily exposes information about the existence or non-existence of objects. It's also not obvious that transparently allowing re-creating of previously deleted instances is necessarily a better default behavior than simply returning 404 responses.
+
Both styles "PUT as 404" and "PUT as create" can be valid in different circumstances, but from version 3.0 onwards we now use 404 behavior as the default, due to it being simpler and more obvious.
+
If you need to generic PUT-as-create behavior you may want to include something like this AllowPUTAsCreateMixin class as a mixin to your views.
[The OPTIONS] method allows a client to determine the options and/or requirements associated with a resource, or the capabilities of a server, without implying a resource action or initiating a resource retrieval.
REST framework includes a configurable mechanism for determining how your API should respond to OPTIONS requests. This allows you to return API schema or other resource information.
+
There are not currently any widely adopted conventions for exactly what style of response should be returned for HTTP OPTIONS requests, so we provide an ad-hoc style that returns some useful information.
+
Here's an example response that demonstrates the information that is returned by default.
The REST framework package only includes a single metadata class implementation, named SimpleMetadata. If you want to use an alternative style you'll need to implement a custom metadata class.
If you have specific requirements for creating schema endpoints that are accessed with regular GET requests, you might consider re-using the metadata API for doing so.
+
For example, the following additional route could be used on a viewset to provide a linkable schema endpoint.
+
@action(methods=['GET'], detail=False)
+def schema(self, request):
+ meta = self.metadata_class()
+ data = meta.determine_metadata(request, self)
+ return Response(data)
+
+
There are a couple of reasons that you might choose to take this approach, including that OPTIONS responses are not cacheable.
If you want to provide a custom metadata class you should override BaseMetadata and implement the determine_metadata(self, request, view) method.
+
Useful things that you might want to do could include returning schema information, using a format such as JSON schema, or returning debug information to admin users.
The following class could be used to limit the information that is returned to OPTIONS requests.
+
class MinimalMetadata(BaseMetadata):
+ """
+ Don't include field and other information for `OPTIONS` requests.
+ Just return the name and description.
+ """
+ def determine_metadata(self, request, view):
+ return {
+ 'name': view.get_view_name(),
+ 'description': view.get_view_description()
+ }
+
+
Then configure your settings to use this custom class:
drf-schema-adapter is a set of tools that makes it easier to provide schema information to frontend frameworks and libraries. It provides a metadata mixin as well as 2 metadata classes and several adapters suitable to generate json-schema as well as schema information readable by various libraries.
+
You can also write your own adapter to work with your specific frontend.
+If you wish to do so, it also provides an exporter that can export those schema information to json files.
REST framework includes support for customizable pagination styles. This allows you to modify how large result sets are split into individual pages of data.
+
The pagination API can support either:
+
+
Pagination links that are provided as part of the content of the response.
+
Pagination links that are included in response headers, such as Content-Range or Link.
+
+
The built-in styles currently all use links included as part of the content of the response. This style is more accessible when using the browsable API.
+
Pagination is only performed automatically if you're using the generic views or viewsets. If you're using a regular APIView, you'll need to call into the pagination API yourself to ensure you return a paginated response. See the source code for the mixins.ListModelMixin and generics.GenericAPIView classes for an example.
+
Pagination can be turned off by setting the pagination class to None.
The pagination style may be set globally, using the DEFAULT_PAGINATION_CLASS and PAGE_SIZE setting keys. For example, to use the built-in limit/offset pagination, you would do something like this:
Note that you need to set both the pagination class, and the page size that should be used. Both DEFAULT_PAGINATION_CLASS and PAGE_SIZE are None by default.
+
You can also set the pagination class on an individual view by using the pagination_class attribute. Typically you'll want to use the same pagination style throughout your API, although you might want to vary individual aspects of the pagination, such as default or maximum page size, on a per-view basis.
If you want to modify particular aspects of the pagination style, you'll want to override one of the pagination classes, and set the attributes that you want to change.
The PageNumberPagination class includes a number of attributes that may be overridden to modify the pagination style.
+
To set these attributes you should override the PageNumberPagination class, and then enable your custom pagination class as above.
+
+
django_paginator_class - The Django Paginator class to use. Default is django.core.paginator.Paginator, which should be fine for most use cases.
+
page_size - A numeric value indicating the page size. If set, this overrides the PAGE_SIZE setting. Defaults to the same value as the PAGE_SIZE settings key.
+
page_query_param - A string value indicating the name of the query parameter to use for the pagination control.
+
page_size_query_param - If set, this is a string value indicating the name of a query parameter that allows the client to set the page size on a per-request basis. Defaults to None, indicating that the client may not control the requested page size.
+
max_page_size - If set, this is a numeric value indicating the maximum allowable requested page size. This attribute is only valid if page_size_query_param is also set.
+
last_page_strings - A list or tuple of string values indicating values that may be used with the page_query_param to request the final page in the set. Defaults to ('last',)
+
template - The name of a template to use when rendering pagination controls in the browsable API. May be overridden to modify the rendering style, or set to None to disable HTML pagination controls completely. Defaults to "rest_framework/pagination/numbers.html".
This pagination style mirrors the syntax used when looking up multiple database records. The client includes both a "limit" and an
+"offset" query parameter. The limit indicates the maximum number of items to return, and is equivalent to the page_size in other styles. The offset indicates the starting position of the query in relation to the complete set of unpaginated items.
+
Request:
+
GET https://api.example.org/accounts/?limit=100&offset=400
+
Optionally, you may also set a PAGE_SIZE key. If the PAGE_SIZE parameter is also used then the limit query parameter will be optional, and may be omitted by the client.
+
On GenericAPIView subclasses you may also set the pagination_class attribute to select LimitOffsetPagination on a per-view basis.
The LimitOffsetPagination class includes a number of attributes that may be overridden to modify the pagination style.
+
To set these attributes you should override the LimitOffsetPagination class, and then enable your custom pagination class as above.
+
+
default_limit - A numeric value indicating the limit to use if one is not provided by the client in a query parameter. Defaults to the same value as the PAGE_SIZE settings key.
+
limit_query_param - A string value indicating the name of the "limit" query parameter. Defaults to 'limit'.
+
offset_query_param - A string value indicating the name of the "offset" query parameter. Defaults to 'offset'.
+
max_limit - If set this is a numeric value indicating the maximum allowable limit that may be requested by the client. Defaults to None.
+
template - The name of a template to use when rendering pagination controls in the browsable API. May be overridden to modify the rendering style, or set to None to disable HTML pagination controls completely. Defaults to "rest_framework/pagination/numbers.html".
The cursor-based pagination presents an opaque "cursor" indicator that the client may use to page through the result set. This pagination style only presents forward and reverse controls, and does not allow the client to navigate to arbitrary positions.
+
Cursor based pagination requires that there is a unique, unchanging ordering of items in the result set. This ordering might typically be a creation timestamp on the records, as this presents a consistent ordering to paginate against.
+
Cursor based pagination is more complex than other schemes. It also requires that the result set presents a fixed ordering, and does not allow the client to arbitrarily index into the result set. However it does provide the following benefits:
+
+
Provides a consistent pagination view. When used properly CursorPagination ensures that the client will never see the same item twice when paging through records, even when new items are being inserted by other clients during the pagination process.
+
Supports usage with very large datasets. With extremely large datasets pagination using offset-based pagination styles may become inefficient or unusable. Cursor based pagination schemes instead have fixed-time properties, and do not slow down as the dataset size increases.
Proper use of cursor based pagination requires a little attention to detail. You'll need to think about what ordering you want the scheme to be applied against. The default is to order by "-created". This assumes that there must be a 'created' timestamp field on the model instances, and will present a "timeline" style paginated view, with the most recently added items first.
+
You can modify the ordering by overriding the 'ordering' attribute on the pagination class, or by using the OrderingFilter filter class together with CursorPagination. When used with OrderingFilter you should strongly consider restricting the fields that the user may order by.
+
Proper usage of cursor pagination should have an ordering field that satisfies the following:
+
+
Should be an unchanging value, such as a timestamp, slug, or other field that is only set once, on creation.
+
Should be unique, or nearly unique. Millisecond precision timestamps are a good example. This implementation of cursor pagination uses a smart "position plus offset" style that allows it to properly support not-strictly-unique values as the ordering.
+
Should be a non-nullable value that can be coerced to a string.
Using an ordering field that does not satisfy these constraints will generally still work, but you'll be losing some of the benefits of cursor pagination.
+
For more technical details on the implementation we use for cursor pagination, the "Building cursors for the Disqus API" blog post gives a good overview of the basic approach.
The CursorPagination class includes a number of attributes that may be overridden to modify the pagination style.
+
To set these attributes you should override the CursorPagination class, and then enable your custom pagination class as above.
+
+
page_size = A numeric value indicating the page size. If set, this overrides the PAGE_SIZE setting. Defaults to the same value as the PAGE_SIZE settings key.
+
cursor_query_param = A string value indicating the name of the "cursor" query parameter. Defaults to 'cursor'.
+
ordering = This should be a string, or list of strings, indicating the field against which the cursor based pagination will be applied. For example: ordering = 'slug'. Defaults to -created. This value may also be overridden by using OrderingFilter on the view.
+
template = The name of a template to use when rendering pagination controls in the browsable API. May be overridden to modify the rendering style, or set to None to disable HTML pagination controls completely. Defaults to "rest_framework/pagination/previous_and_next.html".
To create a custom pagination serializer class you should subclass pagination.BasePagination and override the paginate_queryset(self, queryset, request, view=None) and get_paginated_response(self, data) methods:
+
+
The paginate_queryset method is passed the initial queryset and should return an iterable object that contains only the data in the requested page.
+
The get_paginated_response method is passed the serialized page data and should return a Response instance.
+
+
Note that the paginate_queryset method may set state on the pagination instance, that may later be used by the get_paginated_response method.
Suppose we want to replace the default pagination output style with a modified format that includes the next and previous links under in a nested 'links' key. We could specify a custom pagination class like so:
Note that if you care about how the ordering of keys is displayed in responses in the browsable API you might choose to use an OrderedDict when constructing the body of paginated responses, but this is optional.
API responses for list endpoints will now include a Link header, instead of including the pagination links as part of the body of the response, for example:
+
+
A custom pagination style, using the 'Link' header'
You can also make the pagination controls available to the schema autogeneration
+that REST framework provides, by implementing a get_schema_fields() method. This method should have the following signature:
+
get_schema_fields(self, view)
+
The method should return a list of coreapi.Field instances.
By default using the pagination classes will cause HTML pagination controls to be displayed in the browsable API. There are two built-in display styles. The PageNumberPagination and LimitOffsetPagination classes display a list of page numbers with previous and next controls. The CursorPagination class displays a simpler style that only displays a previous and next control.
You can override the templates that render the HTML pagination controls. The two built-in styles are:
+
+
rest_framework/pagination/numbers.html
+
rest_framework/pagination/previous_and_next.html
+
+
Providing a template with either of these paths in a global template directory will override the default rendering for the relevant pagination classes.
+
Alternatively you can disable HTML pagination controls completely by subclassing on of the existing classes, setting template = None as an attribute on the class. You'll then need to configure your DEFAULT_PAGINATION_CLASS settings key to use your custom class as the default pagination style.
The low-level API for determining if a pagination class should display the controls or not is exposed as a display_page_controls attribute on the pagination instance. Custom pagination classes should be set to True in the paginate_queryset method if they require the HTML pagination controls to be displayed.
+
The .to_html() and .get_html_context() methods may also be overridden in a custom pagination class in order to further customize how the controls are rendered.
Machine interacting web services tend to use more
+structured formats for sending data than form-encoded, since they're
+sending more complex data than simple forms
REST framework includes a number of built in Parser classes, that allow you to accept requests with various media types. There is also support for defining your own custom parsers, which gives you the flexibility to design the media types that your API accepts.
The set of valid parsers for a view is always defined as a list of classes. When request.data is accessed, REST framework will examine the Content-Type header on the incoming request, and determine which parser to use to parse the request content.
+
+
Note: When developing client applications always remember to make sure you're setting the Content-Type header when sending data in an HTTP request.
+
If you don't set the content type, most clients will default to using 'application/x-www-form-urlencoded', which may not be what you wanted.
+
As an example, if you are sending json encoded data using jQuery with the .ajax() method, you should make sure to include the contentType: 'application/json' setting.
The default set of parsers may be set globally, using the DEFAULT_PARSER_CLASSES setting. For example, the following settings would allow only requests with JSON content, instead of the default of JSON or form data.
Parses raw file upload content. The request.data property will be a dictionary with a single key 'file' containing the uploaded file.
+
If the view used with FileUploadParser is called with a filename URL keyword argument, then that argument will be used as the filename.
+
If it is called without a filename URL keyword argument, then the client must set the filename in the Content-Disposition HTTP header. For example Content-Disposition: attachment; filename=upload.jpg.
The FileUploadParser is for usage with native clients that can upload the file as a raw data request. For web-based uploads, or for native clients with multipart upload support, you should use the MultiPartParser instead.
+
Since this parser's media_type matches any content type, FileUploadParser should generally be the only parser set on an API view.
+
FileUploadParser respects Django's standard FILE_UPLOAD_HANDLERS setting, and the request.upload_handlers attribute. See the Django documentation for more details.
To implement a custom parser, you should override BaseParser, set the .media_type property, and implement the .parse(self, stream, media_type, parser_context) method.
+
The method should return the data that will be used to populate the request.data property.
Optional. If provided, this is the media type of the incoming request content.
+
Depending on the request's Content-Type: header, this may be more specific than the renderer's media_type attribute, and may include media type parameters. For example "text/plain; charset=utf-8".
REST framework YAML provides YAML parsing and rendering support. It was previously included directly in the REST framework package, and is now instead supported as a third-party package.
REST Framework XML provides a simple informal XML format. It was previously included directly in the REST framework package, and is now instead supported as a third-party package.
MessagePack is a fast, efficient binary serialization format. Juan Riaza maintains the djangorestframework-msgpack package which provides MessagePack renderer and parser support for REST framework.
djangorestframework-camel-case provides camel case JSON renderers and parsers for REST framework. This allows serializers to use Python-style underscored field names, but be exposed in the API as Javascript-style camel case field names. It is maintained by Vitaly Babiy.
Authentication or identification by itself is not usually sufficient to gain access to information or code. For that, the entity requesting access must have authorization.
Together with authentication and throttling, permissions determine whether a request should be granted or denied access.
+
Permission checks are always run at the very start of the view, before any other code is allowed to proceed. Permission checks will typically use the authentication information in the request.user and request.auth properties to determine if the incoming request should be permitted.
+
Permissions are used to grant or deny access for different classes of users to different parts of the API.
+
The simplest style of permission would be to allow access to any authenticated user, and deny access to any unauthenticated user. This corresponds to the IsAuthenticated class in REST framework.
+
A slightly less strict style of permission would be to allow full access to authenticated users, but allow read-only access to unauthenticated users. This corresponds to the IsAuthenticatedOrReadOnly class in REST framework.
Permissions in REST framework are always defined as a list of permission classes.
+
Before running the main body of the view each permission in the list is checked.
+If any permission check fails an exceptions.PermissionDenied or exceptions.NotAuthenticated exception will be raised, and the main body of the view will not run.
+
When the permissions checks fail either a "403 Forbidden" or a "401 Unauthorized" response will be returned, according to the following rules:
+
+
The request was successfully authenticated, but permission was denied. — An HTTP 403 Forbidden response will be returned.
+
The request was not successfully authenticated, and the highest priority authentication class does not use WWW-Authenticate headers. — An HTTP 403 Forbidden response will be returned.
+
The request was not successfully authenticated, and the highest priority authentication class does use WWW-Authenticate headers. — An HTTP 401 Unauthorized response, with an appropriate WWW-Authenticate header will be returned.
REST framework permissions also support object-level permissioning. Object level permissions are used to determine if a user should be allowed to act on a particular object, which will typically be a model instance.
+
Object level permissions are run by REST framework's generic views when .get_object() is called.
+As with view level permissions, an exceptions.PermissionDenied exception will be raised if the user is not allowed to act on the given object.
+
If you're writing your own views and want to enforce object level permissions,
+or if you override the get_object method on a generic view, then you'll need to explicitly call the .check_object_permissions(request, obj) method on the view at the point at which you've retrieved the object.
+
This will either raise a PermissionDenied or NotAuthenticated exception, or simply return if the view has the appropriate permissions.
Note: With the exception of DjangoObjectPermissions, the provided
+permission classes in rest_framework.permissionsdo not implement the
+methods necessary to check object permissions.
+
If you wish to use the provided permission classes in order to check object
+permissions, you must subclass them and implement the
+has_object_permission() method described in the Custom
+permissions section (below).
For performance reasons the generic views will not automatically apply object level permissions to each instance in a queryset when returning a list of objects.
+
Often when you're using object level permissions you'll also want to filter the queryset appropriately, to ensure that users only have visibility onto instances that they are permitted to view.
Note: when you set new permission classes through class attribute or decorators you're telling the view to ignore the default list set over the settings.py file.
+
Provided they inherit from rest_framework.permissions.BasePermission, permissions can be composed using standard Python bitwise operators. For example, IsAuthenticatedOrReadOnly could be written:
The AllowAny permission class will allow unrestricted access, regardless of if the request was authenticated or unauthenticated.
+
This permission is not strictly required, since you can achieve the same result by using an empty list or tuple for the permissions setting, but you may find it useful to specify this class because it makes the intention explicit.
The IsAuthenticatedOrReadOnly will allow authenticated users to perform any request. Requests for unauthorised users will only be permitted if the request method is one of the "safe" methods; GET, HEAD or OPTIONS.
+
This permission is suitable if you want to your API to allow read permissions to anonymous users, and only allow write permissions to authenticated users.
This permission class ties into Django's standard django.contrib.authmodel permissions. This permission must only be applied to views that have a .queryset property set. Authorization will only be granted if the user is authenticated and has the relevant model permissions assigned.
+
+
POST requests require the user to have the add permission on the model.
+
PUT and PATCH requests require the user to have the change permission on the model.
+
DELETE requests require the user to have the delete permission on the model.
+
+
The default behaviour can also be overridden to support custom model permissions. For example, you might want to include a view model permission for GET requests.
+
To use custom model permissions, override DjangoModelPermissions and set the .perms_map property. Refer to the source code for details.
If you're using this permission with a view that uses an overridden get_queryset() method there may not be a queryset attribute on the view. In this case we suggest also marking the view with a sentinel queryset, so that this class can determine the required permissions. For example:
+
queryset = User.objects.none() # Required for DjangoModelPermissions
+
This permission class ties into Django's standard object permissions framework that allows per-object permissions on models. In order to use this permission class, you'll also need to add a permission backend that supports object-level permissions, such as django-guardian.
+
As with DjangoModelPermissions, this permission must only be applied to views that have a .queryset property or .get_queryset() method. Authorization will only be granted if the user is authenticated and has the relevant per-object permissions and relevant model permissions assigned.
+
+
POST requests require the user to have the add permission on the model instance.
+
PUT and PATCH requests require the user to have the change permission on the model instance.
+
DELETE requests require the user to have the delete permission on the model instance.
+
+
Note that DjangoObjectPermissionsdoes not require the django-guardian package, and should support other object-level backends equally well.
+
As with DjangoModelPermissions you can use custom model permissions by overriding DjangoObjectPermissions and setting the .perms_map property. Refer to the source code for details.
+
+
Note: If you need object level view permissions for GET, HEAD and OPTIONS requests and are using django-guardian for your object-level permissions backend, you'll want to consider using the DjangoObjectPermissionsFilter class provided by the djangorestframework-guardian package. It ensures that list endpoints only return results including objects for which the user has appropriate view permissions.
To implement a custom permission, override BasePermission and implement either, or both, of the following methods:
+
+
.has_permission(self, request, view)
+
.has_object_permission(self, request, view, obj)
+
+
The methods should return True if the request should be granted access, and False otherwise.
+
If you need to test if a request is a read operation or a write operation, you should check the request method against the constant SAFE_METHODS, which is a tuple containing 'GET', 'OPTIONS' and 'HEAD'. For example:
+
if request.method in permissions.SAFE_METHODS:
+ # Check permissions for read-only request
+else:
+ # Check permissions for write request
+
+
+
Note: The instance-level has_object_permission method will only be called if the view-level has_permission checks have already passed. Also note that in order for the instance-level checks to run, the view code should explicitly call .check_object_permissions(request, obj). If you are using the generic views then this will be handled for you by default. (Function-based views will need to check object permissions explicitly, raising PermissionDenied on failure.)
+
+
Custom permissions will raise a PermissionDenied exception if the test fails. To change the error message associated with the exception, implement a message attribute directly on your custom permission. Otherwise the default_detail attribute from PermissionDenied will be used.
The following is an example of a permission class that checks the incoming request's IP address against a blacklist, and denies the request if the IP has been blacklisted.
+
from rest_framework import permissions
+
+class BlacklistPermission(permissions.BasePermission):
+ """
+ Global permission check for blacklisted IPs.
+ """
+
+ def has_permission(self, request, view):
+ ip_addr = request.META['REMOTE_ADDR']
+ blacklisted = Blacklist.objects.filter(ip_addr=ip_addr).exists()
+ return not blacklisted
+
+
As well as global permissions, that are run against all incoming requests, you can also create object-level permissions, that are only run against operations that affect a particular object instance. For example:
+
class IsOwnerOrReadOnly(permissions.BasePermission):
+ """
+ Object-level permission to only allow owners of an object to edit it.
+ Assumes the model instance has an `owner` attribute.
+ """
+
+ def has_object_permission(self, request, view, obj):
+ # Read permissions are allowed to any request,
+ # so we'll always allow GET, HEAD or OPTIONS requests.
+ if request.method in permissions.SAFE_METHODS:
+ return True
+
+ # Instance must have an attribute named `owner`.
+ return obj.owner == request.user
+
+
Note that the generic views will check the appropriate object level permissions, but if you're writing your own custom views, you'll need to make sure you check the object level permission checks yourself. You can do so by calling self.check_object_permissions(request, obj) from the view once you have the object instance. This call will raise an appropriate APIException if any object-level permission checks fail, and will otherwise simply return.
+
Also note that the generic views will only check the object-level permissions for views that retrieve a single model instance. If you require object-level filtering of list views, you'll need to filter the queryset separately. See the filtering documentation for more details.
The Django REST - Access Policy package provides a way to define complex access rules in declarative policy classes that are attached to view sets or function-based views. The policies are defined in JSON in a format similar to AWS' Identity & Access Management policies.
The Composed Permissions package provides a simple way to define complex and multi-depth (with logic operators) permission objects, using small and reusable components.
The REST Condition package is another extension for building complex permissions in a simple and convenient way. The extension allows you to combine permissions with logical operators.
The DRY Rest Permissions package provides the ability to define different permissions for individual default and custom actions. This package is made for apps with permissions that are derived from relationships defined in the app's data model. It also supports permission checks being returned to a client app through the API's serializer. Additionally it supports adding permissions to the default and custom list actions to restrict the data they retrieve per user.
The Django REST Framework API Key package provides permissions classes, models and helpers to add API key authorization to your API. It can be used to authorize internal or third-party backends and services (i.e. machines) which do not have a user account. API keys are stored securely using Django's password hashing infrastructure, and they can be viewed, edited and revoked at anytime in the Django admin.
Relational fields are used to represent model relationships. They can be applied to ForeignKey, ManyToManyField and OneToOneField relationships, as well as to reverse relationships, and custom relationships such as GenericForeignKey.
+
+
Note: The relational fields are declared in relations.py, but by convention you should import them from the serializers module, using from rest_framework import serializers and refer to fields as serializers.<FieldName>.
When using the ModelSerializer class, serializer fields and relationships will be automatically generated for you. Inspecting these automatically generated fields can be a useful tool for determining how to customize the relationship style.
+
To do so, open the Django shell, using python manage.py shell, then import the serializer class, instantiate it, and print the object representation…
+
>>> from myapp.serializers import AccountSerializer
+>>> serializer = AccountSerializer()
+>>> print(repr(serializer))
+AccountSerializer():
+ id = IntegerField(label='ID', read_only=True)
+ name = CharField(allow_blank=True, max_length=100, required=False)
+ owner = PrimaryKeyRelatedField(queryset=User.objects.all())
+
In order to explain the various types of relational fields, we'll use a couple of simple models for our examples. Our models will be for music albums, and the tracks listed on each album.
+
class Album(models.Model):
+ album_name = models.CharField(max_length=100)
+ artist = models.CharField(max_length=100)
+
+class Track(models.Model):
+ album = models.ForeignKey(Album, related_name='tracks', on_delete=models.CASCADE)
+ order = models.IntegerField()
+ title = models.CharField(max_length=100)
+ duration = models.IntegerField()
+
+ class Meta:
+ unique_together = ['album', 'order']
+ ordering = ['order']
+
+ def __str__(self):
+ return '%d: %s' % (self.order, self.title)
+
By default this field is read-write, although you can change this behavior using the read_only flag.
+
Arguments:
+
+
queryset - The queryset used for model instance lookups when validating the field input. Relationships must either set a queryset explicitly, or set read_only=True.
+
many - If applied to a to-many relationship, you should set this argument to True.
+
allow_null - If set to True, the field will accept values of None or the empty string for nullable relationships. Defaults to False.
+
pk_field - Set to a field to control serialization/deserialization of the primary key's value. For example, pk_field=UUIDField(format='hex') would serialize a UUID primary key into its compact hex representation.
By default this field is read-write, although you can change this behavior using the read_only flag.
+
+
Note: This field is designed for objects that map to a URL that accepts a single URL keyword argument, as set using the lookup_field and lookup_url_kwarg arguments.
+
This is suitable for URLs that contain a single primary key or slug argument as part of the URL.
+
If you require more complex hyperlinked representation you'll need to customize the field, as described in the custom hyperlinked fields section, below.
+
+
Arguments:
+
+
view_name - The view name that should be used as the target of the relationship. If you're using the standard router classes this will be a string with the format <modelname>-detail. required.
+
queryset - The queryset used for model instance lookups when validating the field input. Relationships must either set a queryset explicitly, or set read_only=True.
+
many - If applied to a to-many relationship, you should set this argument to True.
+
allow_null - If set to True, the field will accept values of None or the empty string for nullable relationships. Defaults to False.
+
lookup_field - The field on the target that should be used for the lookup. Should correspond to a URL keyword argument on the referenced view. Default is 'pk'.
+
lookup_url_kwarg - The name of the keyword argument defined in the URL conf that corresponds to the lookup field. Defaults to using the same value as lookup_field.
+
format - If using format suffixes, hyperlinked fields will use the same format suffix for the target unless overridden by using the format argument.
By default this field is read-write, although you can change this behavior using the read_only flag.
+
When using SlugRelatedField as a read-write field, you will normally want to ensure that the slug field corresponds to a model field with unique=True.
+
Arguments:
+
+
slug_field - The field on the target that should be used to represent it. This should be a field that uniquely identifies any given instance. For example, username. required
+
queryset - The queryset used for model instance lookups when validating the field input. Relationships must either set a queryset explicitly, or set read_only=True.
+
many - If applied to a to-many relationship, you should set this argument to True.
+
allow_null - If set to True, the field will accept values of None or the empty string for nullable relationships. Defaults to False.
This field can be applied as an identity relationship, such as the 'url' field on a HyperlinkedModelSerializer. It can also be used for an attribute on the object. For example, the following serializer:
+
class AlbumSerializer(serializers.HyperlinkedModelSerializer):
+ track_listing = serializers.HyperlinkedIdentityField(view_name='track-list')
+
+ class Meta:
+ model = Album
+ fields = ['album_name', 'artist', 'track_listing']
+
view_name - The view name that should be used as the target of the relationship. If you're using the standard router classes this will be a string with the format <model_name>-detail. required.
+
lookup_field - The field on the target that should be used for the lookup. Should correspond to a URL keyword argument on the referenced view. Default is 'pk'.
+
lookup_url_kwarg - The name of the keyword argument defined in the URL conf that corresponds to the lookup field. Defaults to using the same value as lookup_field.
+
format - If using format suffixes, hyperlinked fields will use the same format suffix for the target unless overridden by using the format argument.
As opposed to previously discussed references to another entity, the referred entity can instead also be embedded or nested
+in the representation of the object that refers to it.
+Such nested relationships can be expressed by using serializers as fields.
+
If the field is used to represent a to-many relationship, you should add the many=True flag to the serializer field.
By default nested serializers are read-only. If you want to support write-operations to a nested serializer field you'll need to create create() and/or update() methods in order to explicitly specify how the child relationships should be saved.
+
class TrackSerializer(serializers.ModelSerializer):
+ class Meta:
+ model = Track
+ fields = ['order', 'title', 'duration']
+
+class AlbumSerializer(serializers.ModelSerializer):
+ tracks = TrackSerializer(many=True)
+
+ class Meta:
+ model = Album
+ fields = ['album_name', 'artist', 'tracks']
+
+ def create(self, validated_data):
+ tracks_data = validated_data.pop('tracks')
+ album = Album.objects.create(**validated_data)
+ for track_data in tracks_data:
+ Track.objects.create(album=album, **track_data)
+ return album
+
+>>> data = {
+ 'album_name': 'The Grey Album',
+ 'artist': 'Danger Mouse',
+ 'tracks': [
+ {'order': 1, 'title': 'Public Service Announcement', 'duration': 245},
+ {'order': 2, 'title': 'What More Can I Say', 'duration': 264},
+ {'order': 3, 'title': 'Encore', 'duration': 159},
+ ],
+}
+>>> serializer = AlbumSerializer(data=data)
+>>> serializer.is_valid()
+True
+>>> serializer.save()
+<Album: Album object>
+
In rare cases where none of the existing relational styles fit the representation you need,
+you can implement a completely custom relational field, that describes exactly how the
+output representation should be generated from the model instance.
+
To implement a custom relational field, you should override RelatedField, and implement the .to_representation(self, value) method. This method takes the target of the field as the value argument, and should return the representation that should be used to serialize the target. The value argument will typically be a model instance.
+
If you want to implement a read-write relational field, you must also implement the .to_internal_value(self, data) method.
+
To provide a dynamic queryset based on the context, you can also override .get_queryset(self) instead of specifying .queryset on the class or when initializing the field.
This custom field would then serialize to the following representation.
+
{
+ 'album_name': 'Sometimes I Wish We Were an Eagle',
+ 'artist': 'Bill Callahan',
+ 'tracks': [
+ 'Track 1: Jim Cain (04:39)',
+ 'Track 2: Eid Ma Clack Shaw (04:19)',
+ 'Track 3: The Wind and the Dove (04:34)',
+ ...
+ ]
+}
+
If you want to support a writable hyperlinked field then you'll also want to override get_object, in order to map incoming URLs back to the object they represent. For read-only hyperlinked fields there is no need to override this method.
+
The return value of this method should the object that corresponds to the matched URL conf arguments.
This cannot be represented with the default implementation, which accepts only a single lookup field.
+
In this case we'd need to override HyperlinkedRelatedField to get the behavior we want:
+
from rest_framework import serializers
+from rest_framework.reverse import reverse
+
+class CustomerHyperlink(serializers.HyperlinkedRelatedField):
+ # We define these as class attributes, so we don't need to pass them as arguments.
+ view_name = 'customer-detail'
+ queryset = Customer.objects.all()
+
+ def get_url(self, obj, view_name, request, format):
+ url_kwargs = {
+ 'organization_slug': obj.organization.slug,
+ 'customer_pk': obj.pk
+ }
+ return reverse(view_name, kwargs=url_kwargs, request=request, format=format)
+
+ def get_object(self, view_name, view_args, view_kwargs):
+ lookup_kwargs = {
+ 'organization__slug': view_kwargs['organization_slug'],
+ 'pk': view_kwargs['customer_pk']
+ }
+ return self.get_queryset().get(**lookup_kwargs)
+
+
Note that if you wanted to use this style together with the generic views then you'd also need to override .get_object on the view in order to get the correct lookup behavior.
+
Generally we recommend a flat style for API representations where possible, but the nested URL style can also be reasonable when used in moderation.
The queryset argument is only ever required for writable relationship field, in which case it is used for performing the model instance lookup, that maps from the primitive user input, into a model instance.
+
In version 2.x a serializer class could sometimes automatically determine the queryset argument if a ModelSerializer class was being used.
+
This behavior is now replaced with always using an explicit queryset argument for writable relational fields.
+
Doing so reduces the amount of hidden 'magic' that ModelSerializer provides, makes the behavior of the field more clear, and ensures that it is trivial to move between using the ModelSerializer shortcut, or using fully explicit Serializer classes.
The built-in __str__ method of the model will be used to generate string representations of the objects used to populate the choices property. These choices are used to populate select HTML inputs in the browsable API.
+
To provide customized representations for such inputs, override display_value() of a RelatedField subclass. This method will receive a model object, and should return a string suitable for representing it. For example:
When rendered in the browsable API relational fields will default to only displaying a maximum of 1000 selectable items. If more items are present then a disabled option with "More than 1000 items…" will be displayed.
+
This behavior is intended to prevent a template from being unable to render in an acceptable timespan due to a very large number of relationships being displayed.
+
There are two keyword arguments you can use to control this behavior:
+
+
html_cutoff - If set this will be the maximum number of choices that will be displayed by a HTML select drop down. Set to None to disable any limiting. Defaults to 1000.
+
html_cutoff_text - If set this will display a textual indicator if the maximum number of items have been cutoff in an HTML select drop down. Defaults to "More than {count} items…"
+
+
You can also control these globally using the settings HTML_SELECT_CUTOFF and HTML_SELECT_CUTOFF_TEXT.
+
In cases where the cutoff is being enforced you may want to instead use a plain input field in the HTML form. You can do so using the style keyword argument. For example:
Note that reverse relationships are not automatically included by the ModelSerializer and HyperlinkedModelSerializer classes. To include a reverse relationship, you must explicitly add it to the fields list. For example:
+
class AlbumSerializer(serializers.ModelSerializer):
+ class Meta:
+ fields = ['tracks', ...]
+
+
You'll normally want to ensure that you've set an appropriate related_name argument on the relationship, that you can use as the field name. For example:
+
class Track(models.Model):
+ album = models.ForeignKey(Album, related_name='tracks', on_delete=models.CASCADE)
+ ...
+
+
If you have not set a related name for the reverse relationship, you'll need to use the automatically generated related name in the fields argument. For example:
+
class AlbumSerializer(serializers.ModelSerializer):
+ class Meta:
+ fields = ['track_set', ...]
+
If you want to serialize a generic foreign key, you need to define a custom field, to determine explicitly how you want to serialize the targets of the relationship.
+
For example, given the following model for a tag, which has a generic relationship with other arbitrary models:
And the following two models, which may have associated tags:
+
class Bookmark(models.Model):
+ """
+ A bookmark consists of a URL, and 0 or more descriptive tags.
+ """
+ url = models.URLField()
+ tags = GenericRelation(TaggedItem)
+
+
+class Note(models.Model):
+ """
+ A note consists of some text, and 0 or more descriptive tags.
+ """
+ text = models.CharField(max_length=1000)
+ tags = GenericRelation(TaggedItem)
+
+
We could define a custom field that could be used to serialize tagged instances, using the type of each instance to determine how it should be serialized.
+
class TaggedObjectRelatedField(serializers.RelatedField):
+ """
+ A custom field to use for the `tagged_object` generic relationship.
+ """
+
+ def to_representation(self, value):
+ """
+ Serialize tagged objects to a simple textual representation.
+ """
+ if isinstance(value, Bookmark):
+ return 'Bookmark: ' + value.url
+ elif isinstance(value, Note):
+ return 'Note: ' + value.text
+ raise Exception('Unexpected type of tagged object')
+
+
If you need the target of the relationship to have a nested representation, you can use the required serializers inside the .to_representation() method:
+
def to_representation(self, value):
+ """
+ Serialize bookmark instances using a bookmark serializer,
+ and note instances using a note serializer.
+ """
+ if isinstance(value, Bookmark):
+ serializer = BookmarkSerializer(value)
+ elif isinstance(value, Note):
+ serializer = NoteSerializer(value)
+ else:
+ raise Exception('Unexpected type of tagged object')
+
+ return serializer.data
+
+
Note that reverse generic keys, expressed using the GenericRelation field, can be serialized using the regular relational field types, since the type of the target in the relationship is always known.
Before a TemplateResponse instance can be returned to the client, it must be rendered. The rendering process takes the intermediate representation of template and context, and turns it into the final byte stream that can be served to the client.
REST framework includes a number of built in Renderer classes, that allow you to return responses with various media types. There is also support for defining your own custom renderers, which gives you the flexibility to design your own media types.
The set of valid renderers for a view is always defined as a list of classes. When a view is entered REST framework will perform content negotiation on the incoming request, and determine the most appropriate renderer to satisfy the request.
+
The basic process of content negotiation involves examining the request's Accept header, to determine which media types it expects in the response. Optionally, format suffixes on the URL may be used to explicitly request a particular representation. For example the URL http://example.com/api/users_count.json might be an endpoint that always returns JSON data.
The default set of renderers may be set globally, using the DEFAULT_RENDERER_CLASSES setting. For example, the following settings would use JSON as the main media type and also include the self describing API.
It's important when specifying the renderer classes for your API to think about what priority you want to assign to each media type. If a client underspecifies the representations it can accept, such as sending an Accept: */* header, or not including an Accept header at all, then REST framework will select the first renderer in the list to use for the response.
+
For example if your API serves JSON responses and the HTML browsable API, you might want to make JSONRenderer your default renderer, in order to send JSON responses to clients that do not specify an Accept header.
+
If your API includes views that can serve both regular webpages and API responses depending on the request, then you might consider making TemplateHTMLRenderer your default renderer, in order to play nicely with older browsers that send broken accept headers.
Renders the request data into JSON, using utf-8 encoding.
+
Note that the default style is to include unicode characters, and render the response using a compact style with no unnecessary whitespace:
+
{"unicode black star":"★","value":999}
+
+
The client may additionally include an 'indent' media type parameter, in which case the returned JSON will be indented. For example Accept: application/json; indent=4.
Renders data to HTML, using Django's standard template rendering.
+Unlike other renderers, the data passed to the Response does not need to be serialized. Also, unlike other renderers, you may want to include a template_name argument when creating the Response.
+
The TemplateHTMLRenderer will create a RequestContext, using the response.data as the context dict, and determine a template name to use to render the context.
+
The template name is determined by (in order of preference):
+
+
An explicit template_name argument passed to the response.
+
An explicit .template_name attribute set on this class.
+
The return result of calling view.get_template_names().
+
+
An example of a view that uses TemplateHTMLRenderer:
+
class UserDetail(generics.RetrieveAPIView):
+ """
+ A view that returns a templated HTML representation of a given user.
+ """
+ queryset = User.objects.all()
+ renderer_classes = [TemplateHTMLRenderer]
+
+ def get(self, request, *args, **kwargs):
+ self.object = self.get_object()
+ return Response({'user': self.object}, template_name='user_detail.html')
+
+
You can use TemplateHTMLRenderer either to return regular HTML pages using REST framework, or to return both HTML and API responses from a single endpoint.
+
If you're building websites that use TemplateHTMLRenderer along with other renderer classes, you should consider listing TemplateHTMLRenderer as the first class in the renderer_classes list, so that it will be prioritised first even for browsers that send poorly formed ACCEPT: headers.
A simple renderer that simply returns pre-rendered HTML. Unlike other renderers, the data passed to the response object should be a string representing the content to be returned.
+
An example of a view that uses StaticHTMLRenderer:
You can use StaticHTMLRenderer either to return regular HTML pages using REST framework, or to return both HTML and API responses from a single endpoint.
This renderer will determine which other renderer would have been given highest priority, and use that to display an API style response within the HTML page.
By default the response content will be rendered with the highest priority renderer apart from BrowsableAPIRenderer. If you need to customize this behavior, for example to use HTML as the default return format, but use JSON in the browsable API, you can do so by overriding the get_default_renderer() method. For example:
+
class CustomBrowsableAPIRenderer(BrowsableAPIRenderer):
+ def get_default_renderer(self, view):
+ return JSONRenderer()
+
This renderer is suitable for CRUD-style web APIs that should also present a user-friendly interface for managing the data.
+
Note that views that have nested or list serializers for their input won't work well with the AdminRenderer, as the HTML forms are unable to properly support them.
+
Note: The AdminRenderer is only able to include links to detail pages when a properly configured URL_FIELD_NAME (url by default) attribute is present in the data. For HyperlinkedModelSerializer this will be the case, but for ModelSerializer or plain Serializer classes you'll need to make sure to include the field explicitly. For example here we use models get_absolute_url method:
+
class AccountSerializer(serializers.ModelSerializer):
+ url = serializers.CharField(source='get_absolute_url', read_only=True)
+
+ class Meta:
+ model = Account
+
Renders data returned by a serializer into an HTML form. The output of this renderer does not include the enclosing <form> tags, a hidden CSRF input or any submit buttons.
+
This renderer is not intended to be used directly, but can instead be used in templates by passing a serializer instance to the render_form template tag.
This renderer is used for rendering HTML multipart form data. It is not suitable as a response renderer, but is instead used for creating test requests, using REST framework's test client and test request factory.
To implement a custom renderer, you should override BaseRenderer, set the .media_type and .format properties, and implement the .render(self, data, media_type=None, renderer_context=None) method.
+
The method should return a bytestring, which will be used as the body of the HTTP response.
Optional. If provided, this is the accepted media type, as determined by the content negotiation stage.
+
Depending on the client's Accept: header, this may be more specific than the renderer's media_type attribute, and may include media type parameters. For example "application/json; nested=true".
Note that if a renderer class returns a unicode string, then the response content will be coerced into a bytestring by the Response class, with the charset attribute set on the renderer used to determine the encoding.
+
If the renderer returns a bytestring representing raw binary content, you should set a charset value of None, which will ensure the Content-Type header of the response will not have a charset value set.
+
In some cases you may also want to set the render_style attribute to 'binary'. Doing so will also ensure that the browsable API will not attempt to display the binary content as a string.
+
class JPEGRenderer(renderers.BaseRenderer):
+ media_type = 'image/jpeg'
+ format = 'jpg'
+ charset = None
+ render_style = 'binary'
+
+ def render(self, data, media_type=None, renderer_context=None):
+ return data
+
In some cases you might want your view to use different serialization styles depending on the accepted media type. If you need to do this you can access request.accepted_renderer to determine the negotiated renderer that will be used for the response.
+
For example:
+
@api_view(['GET'])
+@renderer_classes([TemplateHTMLRenderer, JSONRenderer])
+def list_users(request):
+ """
+ A view that can return JSON or HTML representations
+ of the users in the system.
+ """
+ queryset = Users.objects.filter(active=True)
+
+ if request.accepted_renderer.format == 'html':
+ # TemplateHTMLRenderer takes a context dict,
+ # and additionally requires a 'template_name'.
+ # It does not require serialization.
+ data = {'users': queryset}
+ return Response(data, template_name='list_users.html')
+
+ # JSONRenderer requires serialized data as normal.
+ serializer = UserSerializer(instance=queryset)
+ data = serializer.data
+ return Response(data)
+
In some cases you might want a renderer to serve a range of media types.
+In this case you can underspecify the media types it should respond to, by using a media_type value such as image/*, or */*.
+
If you underspecify the renderer's media type, you should make sure to specify the media type explicitly when you return the response, using the content_type attribute. For example:
For the purposes of many Web APIs, simple JSON responses with hyperlinked relations may be sufficient. If you want to fully embrace RESTful design and HATEOAS you'll need to consider the design and usage of your media types in more detail.
+
In the words of Roy Fielding, "A REST API should spend almost all of its descriptive effort in defining the media type(s) used for representing resources and driving application state, or in defining extended relation names and/or hypertext-enabled mark-up for existing standard media types.".
Typically a renderer will behave the same regardless of if it's dealing with a regular response, or with a response caused by an exception being raised, such as an Http404 or PermissionDenied exception, or a subclass of APIException.
+
If you're using either the TemplateHTMLRenderer or the StaticHTMLRenderer and an exception is raised, the behavior is slightly different, and mirrors Django's default handling of error views.
+
Exceptions raised and handled by an HTML renderer will attempt to render using one of the following methods, by order of precedence.
+
+
Load and render a template named {status_code}.html.
+
Load and render a template named api_exception.html.
+
Render the HTTP status code and text, for example "404 Not Found".
+
+
Templates will render with a RequestContext which includes the status_code and details keys.
+
Note: If DEBUG=True, Django's standard traceback error page will be displayed instead of rendering the HTTP status code and text.
REST framework YAML provides YAML parsing and rendering support. It was previously included directly in the REST framework package, and is now instead supported as a third-party package.
REST Framework XML provides a simple informal XML format. It was previously included directly in the REST framework package, and is now instead supported as a third-party package.
REST framework JSONP provides JSONP rendering support. It was previously included directly in the REST framework package, and is now instead supported as a third-party package.
+
+
Warning: If you require cross-domain AJAX requests, you should generally be using the more modern approach of CORS as an alternative to JSONP. See the CORS documentation for more details.
MessagePack is a fast, efficient binary serialization format. Juan Riaza maintains the djangorestframework-msgpack package which provides MessagePack renderer and parser support for REST framework.
XLSX is the world's most popular binary spreadsheet format. Tim Allen of The Wharton School maintains drf-renderer-xlsx, which renders an endpoint as an XLSX spreadsheet using OpenPyXL, and allows the client to download it. Spreadsheets can be styled on a per-view basis.
To avoid having a file streamed without a filename (which the browser will often default to the filename "download", with no extension), we need to use a mixin to override the Content-Disposition header. If no filename is provided, it will default to export.xlsx. For example:
Comma-separated values are a plain-text tabular data format, that can be easily imported into spreadsheet applications. Mjumbe Poe maintains the djangorestframework-csv package which provides CSV renderer support for REST framework.
UltraJSON is an optimized C JSON encoder which can give significantly faster JSON rendering. Jacob Haslehurst maintains the drf-ujson-renderer package which implements JSON rendering using the UJSON package.
djangorestframework-camel-case provides camel case JSON renderers and parsers for REST framework. This allows serializers to use Python-style underscored field names, but be exposed in the API as Javascript-style camel case field names. It is maintained by Vitaly Babiy.
Django REST Pandas provides a serializer and renderers that support additional data processing and output via the Pandas DataFrame API. Django REST Pandas includes renderers for Pandas-style CSV files, Excel workbooks (both .xls and .xlsx), and a number of other formats. It is maintained by S. Andrew Sheppard as part of the wq Project.
REST framework's Request class extends the standard HttpRequest, adding support for REST framework's flexible request parsing and request authentication.
REST framework's Request objects provide flexible request parsing that allows you to treat requests with JSON data or other media types in the same way that you would normally deal with form data.
request.data returns the parsed content of the request body. This is similar to the standard request.POST and request.FILES attributes except that:
+
+
It includes all parsed content, including file and non-file inputs.
+
It supports parsing the content of HTTP methods other than POST, meaning that you can access the content of PUT and PATCH requests.
+
It supports REST framework's flexible request parsing, rather than just supporting form data. For example you can handle incoming JSON data in the same way that you handle incoming form data.
request.query_params is a more correctly named synonym for request.GET.
+
For clarity inside your code, we recommend using request.query_params instead of the Django's standard request.GET. Doing so will help keep your codebase more correct and obvious - any HTTP method type may include query parameters, not just GET requests.
The APIView class or @api_view decorator will ensure that this property is automatically set to a list of Parser instances, based on the parser_classes set on the view or based on the DEFAULT_PARSER_CLASSES setting.
+
You won't typically need to access this property.
+
+
Note: If a client sends malformed content, then accessing request.data may raise a ParseError. By default REST framework's APIView class or @api_view decorator will catch the error and return a 400 Bad Request response.
+
If a client sends a request with a content-type that cannot be parsed then a UnsupportedMediaType exception will be raised, which by default will be caught and return a 415 Unsupported Media Type response.
The request exposes some properties that allow you to determine the result of the content negotiation stage. This allows you to implement behaviour such as selecting a different serialization schemes for different media types.
request.auth returns any additional authentication context. The exact behavior of request.auth depends on the authentication policy being used, but it may typically be an instance of the token that the request was authenticated against.
+
If the request is unauthenticated, or if no additional context is present, the default value of request.auth is None.
The APIView class or @api_view decorator will ensure that this property is automatically set to a list of Authentication instances, based on the authentication_classes set on the view or based on the DEFAULT_AUTHENTICATORS setting.
+
You won't typically need to access this property.
+
+
Note: You may see a WrappedAttributeError raised when calling the .user or .auth properties. These errors originate from an authenticator as a standard AttributeError, however it's necessary that they be re-raised as a different exception type in order to prevent them from being suppressed by the outer property access. Python will not recognize that the AttributeError originates from the authenticator and will instead assume that the request object does not have a .user or .auth property. The authenticator will need to be fixed.
request.content_type, returns a string object representing the media type of the HTTP request's body, or an empty string if no media type was provided.
+
You won't typically need to directly access the request's content type, as you'll normally rely on REST framework's default request parsing behavior.
+
If you do need to access the content type of the request you should use the .content_type property in preference to using request.META.get('HTTP_CONTENT_TYPE'), as it provides transparent support for browser-based non-form content.
As REST framework's Request extends Django's HttpRequest, all the other standard attributes and methods are also available. For example the request.META and request.session dictionaries are available as normal.
+
Note that due to implementation reasons the Request class does not inherit from HttpRequest class, but instead extends the class using composition.
Unlike basic HttpResponse objects, TemplateResponse objects retain the details of the context that was provided by the view to compute the response. The final output of the response is not computed until it is needed, later in the response process.
REST framework supports HTTP content negotiation by providing a Response class which allows you to return content that can be rendered into multiple content types, depending on the client request.
+
The Response class subclasses Django's SimpleTemplateResponse. Response objects are initialised with data, which should consist of native Python primitives. REST framework then uses standard HTTP content negotiation to determine how it should render the final response content.
+
There's no requirement for you to use the Response class, you can also return regular HttpResponse or StreamingHttpResponse objects from your views if required. Using the Response class simply provides a nicer interface for returning content-negotiated Web API responses, that can be rendered to multiple formats.
+
Unless you want to heavily customize REST framework for some reason, you should always use an APIView class or @api_view function for views that return Response objects. Doing so ensures that the view can perform content negotiation and select the appropriate renderer for the response, before it is returned from the view.
Unlike regular HttpResponse objects, you do not instantiate Response objects with rendered content. Instead you pass in unrendered data, which may consist of any Python primitives.
+
The renderers used by the Response class cannot natively handle complex datatypes such as Django model instances, so you need to serialize the data into primitive datatypes before creating the Response object.
+
You can use REST framework's Serializer classes to perform this data serialization, or use your own custom serialization.
+
Arguments:
+
+
data: The serialized data for the response.
+
status: A status code for the response. Defaults to 200. See also status codes.
+
template_name: A template name to use if HTMLRenderer is selected.
+
headers: A dictionary of HTTP headers to use in the response.
+
content_type: The content type of the response. Typically, this will be set automatically by the renderer as determined by content negotiation, but there may be some cases where you need to specify the content type explicitly.
The Response class extends SimpleTemplateResponse, and all the usual attributes and methods are also available on the response. For example you can set headers on the response in the standard way:
As with any other TemplateResponse, this method is called to render the serialized data of the response into the final response content. When .render() is called, the response content will be set to the result of calling the .render(data, accepted_media_type, renderer_context) method on the accepted_renderer instance.
+
You won't typically need to call .render() yourself, as it's handled by Django's standard response cycle.
The central feature that distinguishes the REST architectural style from other network-based styles is its emphasis on a uniform interface between components.
As a rule, it's probably better practice to return absolute URIs from your Web APIs, such as http://example.com/foobar, rather than returning relative URIs, such as /foobar.
+
The advantages of doing so are:
+
+
It's more explicit.
+
It leaves less work for your API clients.
+
There's no ambiguity about the meaning of the string when it's found in representations such as JSON that do not have a native URI type.
+
It makes it easy to do things like markup HTML representations with hyperlinks.
+
+
REST framework provides two utility functions to make it more simple to return absolute URIs from your Web API.
+
There's no requirement for you to use them, but if you do then the self-describing API will be able to automatically hyperlink its output for you, which makes browsing the API much easier.
Resource routing allows you to quickly declare all of the common routes for a given resourceful controller. Instead of declaring separate routes for your index... a resourceful route declares them in a single line of code.
Some Web frameworks such as Rails provide functionality for automatically determining how the URLs for an application should be mapped to the logic that deals with handling incoming requests.
+
REST framework adds support for automatic URL routing to Django, and provides you with a simple, quick and consistent way of wiring your view logic to a set of URLs.
There are two mandatory arguments to the register() method:
+
+
prefix - The URL prefix to use for this set of routes.
+
viewset - The viewset class.
+
+
Optionally, you may also specify an additional argument:
+
+
basename - The base to use for the URL names that are created. If unset the basename will be automatically generated based on the queryset attribute of the viewset, if it has one. Note that if the viewset does not include a queryset attribute then you must set basename when registering the viewset.
+
+
The example above would generate the following URL patterns:
Note: The basename argument is used to specify the initial part of the view name pattern. In the example above, that's the user or account part.
+
Typically you won't need to specify the basename argument, but if you have a viewset where you've defined a custom get_queryset method, then the viewset may not have a .queryset attribute set. If you try to register that viewset you'll see an error like this:
+
'basename' argument not specified, and could not automatically determine the name from the viewset, as it does not have a '.queryset' attribute.
+
+
This means you'll need to explicitly set the basename argument when registering the viewset, as it could not be automatically determined from the model name.
The .urls attribute on a router instance is simply a standard list of URL patterns. There are a number of different styles for how you can include these URLs.
+
For example, you can append router.urls to a list of existing views...
Note: If using namespacing with hyperlinked serializers you'll also need to ensure that any view_name parameters
+on the serializers correctly reflect the namespace. In the examples above you'd need to include a parameter such as
+view_name='app_name:user-detail' for serializer fields hyperlinked to the user detail view.
+
The automatic view_name generation uses a pattern like %(model_name)-detail. Unless your models names actually clash
+you may be better off not namespacing your Django REST Framework views when using hyperlinked serializers.
A viewset may mark extra actions for routing by decorating a method with the @action decorator. These extra actions will be included in the generated routes. For example, given the set_password method on the UserViewSet class:
By default, the URL pattern is based on the method name, and the URL name is the combination of the ViewSet.basename and the hyphenated method name.
+If you don't want to use the defaults for either of these values, you can instead provide the url_path and url_name arguments to the @action decorator.
+
For example, if you want to change the URL for our custom action to ^users/{pk}/change-password/$, you could write:
This router includes routes for the standard set of list, create, retrieve, update, partial_update and destroy actions. The viewset can also mark additional methods to be routed, using the @action decorator.
+
+
URL Style
HTTP Method
Action
URL Name
+
{prefix}/
GET
list
{basename}-list
+
POST
create
+
{prefix}/{url_path}/
GET, or as specified by `methods` argument
`@action(detail=False)` decorated method
{basename}-{url_name}
+
{prefix}/{lookup}/
GET
retrieve
{basename}-detail
+
PUT
update
+
PATCH
partial_update
+
DELETE
destroy
+
{prefix}/{lookup}/{url_path}/
GET, or as specified by `methods` argument
`@action(detail=True)` decorated method
{basename}-{url_name}
+
+
+
By default the URLs created by SimpleRouter are appended with a trailing slash.
+This behavior can be modified by setting the trailing_slash argument to False when instantiating the router. For example:
+
router = SimpleRouter(trailing_slash=False)
+
+
Trailing slashes are conventional in Django, but are not used by default in some other frameworks such as Rails. Which style you choose to use is largely a matter of preference, although some javascript frameworks may expect a particular routing style.
+
The router will match lookup values containing any characters except slashes and period characters. For a more restrictive (or lenient) lookup pattern, set the lookup_value_regex attribute on the viewset. For example, you can limit the lookup to valid UUIDs:
This router is similar to SimpleRouter as above, but additionally includes a default API root view, that returns a response containing hyperlinks to all the list views. It also generates routes for optional .json style format suffixes.
+
+
URL Style
HTTP Method
Action
URL Name
+
[.format]
GET
automatically generated root view
api-root
+
{prefix}/[.format]
GET
list
{basename}-list
+
POST
create
+
{prefix}/{url_path}/[.format]
GET, or as specified by `methods` argument
`@action(detail=False)` decorated method
{basename}-{url_name}
+
{prefix}/{lookup}/[.format]
GET
retrieve
{basename}-detail
+
PUT
update
+
PATCH
partial_update
+
DELETE
destroy
+
{prefix}/{lookup}/{url_path}/[.format]
GET, or as specified by `methods` argument
`@action(detail=True)` decorated method
{basename}-{url_name}
+
+
+
As with SimpleRouter the trailing slashes on the URL routes can be removed by setting the trailing_slash argument to False when instantiating the router.
Implementing a custom router isn't something you'd need to do very often, but it can be useful if you have specific requirements about how the URLs for your API are structured. Doing so allows you to encapsulate the URL structure in a reusable way that ensures you don't have to write your URL patterns explicitly for each new view.
+
The simplest way to implement a custom router is to subclass one of the existing router classes. The .routes attribute is used to template the URL patterns that will be mapped to each viewset. The .routes attribute is a list of Route named tuples.
+
The arguments to the Route named tuple are:
+
url: A string representing the URL to be routed. May include the following format strings:
+
+
{prefix} - The URL prefix to use for this set of routes.
+
{lookup} - The lookup field used to match against a single instance.
+
{trailing_slash} - Either a '/' or an empty string, depending on the trailing_slash argument.
+
+
mapping: A mapping of HTTP method names to the view methods
+
name: The name of the URL as used in reverse calls. May include the following format string:
+
+
{basename} - The base to use for the URL names that are created.
+
+
initkwargs: A dictionary of any additional arguments that should be passed when instantiating the view. Note that the detail, basename, and suffix arguments are reserved for viewset introspection and are also used by the browsable API to generate the view name and breadcrumb links.
You can also customize how the @action decorator is routed. Include the DynamicRoute named tuple in the .routes list, setting the detail argument as appropriate for the list-based and detail-based routes. In addition to detail, the arguments to DynamicRoute are:
+
url: A string representing the URL to be routed. May include the same format strings as Route, and additionally accepts the {url_path} format string.
+
name: The name of the URL as used in reverse calls. May include the following format strings:
+
+
{basename} - The base to use for the URL names that are created.
+
{url_name} - The url_name provided to the @action.
+
+
initkwargs: A dictionary of any additional arguments that should be passed when instantiating the view.
Let's take a look at the routes our CustomReadOnlyRouter would generate for a simple viewset.
+
views.py:
+
class UserViewSet(viewsets.ReadOnlyModelViewSet):
+ """
+ A viewset that provides the standard actions
+ """
+ queryset = User.objects.all()
+ serializer_class = UserSerializer
+ lookup_field = 'username'
+
+ @action(detail=True)
+ def group_names(self, request, pk=None):
+ """
+ Returns a list of all the group names that the given
+ user belongs to.
+ """
+ user = self.get_object()
+ groups = user.groups.all()
+ return Response([group.name for group in groups])
+
If you want to provide totally custom behavior, you can override BaseRouter and override the get_urls(self) method. The method should inspect the registered viewsets and return a list of URL patterns. The registered prefix, viewset and basename tuples may be inspected by accessing the self.registry attribute.
+
You may also want to override the get_default_basename(self, viewset) method, or else always explicitly set the basename argument when registering your viewsets with the router.
The wq.db package provides an advanced ModelRouter class (and singleton instance) that extends DefaultRouter with a register_model() API. Much like Django's admin.site.register, the only required argument to rest.router.register_model is a model class. Reasonable defaults for a url prefix, serializer, and viewset will be inferred from the model and global configuration.
A machine-readable [schema] describes what resources are available via the API, what their URLs are, how they are represented and what operations they support.
+
— Heroku, [JSON Schema for the Heroku Platform API][cite]
+
+
API schemas are a useful tool that allow for a range of use cases, including
+generating reference documentation, or driving dynamic client libraries that
+can interact with your API.
+
Django REST Framework provides support for automatic generation of
+OpenAPI schemas.
If your schema is static, you can use the generateschema management command:
+
./manage.py generateschema > openapi-schema.yml
+
+
+
Once you've generated a schema in this way you can annotate it with any
+additional information that cannot be automatically inferred by the schema
+generator.
+
You might want to check your API schema into version control and update it
+with each new release, or serve the API schema from your site's static media.
If you require a dynamic schema, because foreign key choices depend on database
+values, for example, you can route a SchemaView that will generate and serve
+your schema on demand.
+
To route a SchemaView, use the get_schema_view() helper.
+
In urls.py:
+
from rest_framework.schemas import get_schema_view
+
+urlpatterns = [
+ # ...
+ # Use the `get_schema_view()` helper to add a `SchemaView` to project URLs.
+ # * `title` and `description` parameters are passed to `SchemaGenerator`.
+ # * Provide view name for use with `reverse()`.
+ path('openapi', get_schema_view(
+ title="Your Project",
+ description="API for all things …",
+ version="1.0.0"
+ ), name='openapi-schema'),
+ # ...
+]
+
urlconf: A string representing the import path to the URL conf that you want
+ to generate an API schema for. This defaults to the value of Django's
+ ROOT_URLCONF setting.
generator_class: May be used to specify a SchemaGenerator subclass to be
+ passed to the SchemaView.
+
+
authentication_classes: May be used to specify the list of authentication
+ classes that will apply to the schema endpoint. Defaults to
+ settings.DEFAULT_AUTHENTICATION_CLASSES
+
permission_classes: May be used to specify the list of permission classes
+ that will apply to the schema endpoint. Defaults to
+ settings.DEFAULT_PERMISSION_CLASSES.
+
renderer_classes: May be used to pass the set of renderer classes that can
+ be used to render the API root endpoint.
In order to customize the top-level schema sublass
+rest_framework.schemas.openapi.SchemaGenerator and provide it as an argument
+to the generateschema command or get_schema_view() helper function.
By default, view introspection is performed by an AutoSchema instance
+accessible via the schema attribute on APIView. This provides the
+appropriate Open API operation object for the view,
+request method and path:
In compiling the schema, SchemaGenerator calls view.schema.get_operation()
+for each view, allowed method, and path.
+
+
Note: For basic APIView subclasses, default introspection is essentially
+limited to the URL kwarg path parameters. For GenericAPIView
+subclasses, which includes all the provided class based views, AutoSchema will
+attempt to introspect serializer, pagination and filter fields, as well as
+provide richer path field descriptions. (The key hooks here are the relevant
+GenericAPIView attributes and methods: get_serializer, pagination_class,
+filter_backends and so on.)
+
+
In order to customize the operation generation, you should provide an AutoSchema subclass, overriding get_operation() as you need:
+
from rest_framework.views import APIView
+ from rest_framework.schemas.openapi import AutoSchema
+
+ class CustomSchema(AutoSchema):
+ def get_operation(...):
+ # Implement custom introspection here (or in other sub-methods)
+
+ class CustomView(APIView):
+ """APIView subclass with custom schema introspection."""
+ schema = CustomSchema()
+
+
This provides complete control over view introspection.
+
You may disable schema generation for a view by setting schema to None:
+
class CustomView(APIView):
+ ...
+ schema = None # Will not appear in schema
+
Expanding the usefulness of the serializers is something that we would
+like to address. However, it's not a trivial problem, and it
+will take some serious design work.
Serializers allow complex data such as querysets and model instances to be converted to native Python datatypes that can then be easily rendered into JSON, XML or other content types. Serializers also provide deserialization, allowing parsed data to be converted back into complex types, after first validating the incoming data.
+
The serializers in REST framework work very similarly to Django's Form and ModelForm classes. We provide a Serializer class which gives you a powerful, generic way to control the output of your responses, as well as a ModelSerializer class which provides a useful shortcut for creating serializers that deal with model instances and querysets.
If we want to be able to return complete object instances based on the validated data we need to implement one or both of the .create() and .update() methods. For example:
If your object instances correspond to Django models you'll also want to ensure that these methods save the object to the database. For example, if Comment was a Django model, the methods might look like this:
Now when deserializing data, we can call .save() to return an object instance, based on the validated data.
+
comment = serializer.save()
+
+
Calling .save() will either create a new instance, or update an existing instance, depending on if an existing instance was passed when instantiating the serializer class:
+
# .save() will create a new instance.
+serializer = CommentSerializer(data=data)
+
+# .save() will update the existing `comment` instance.
+serializer = CommentSerializer(comment, data=data)
+
+
Both the .create() and .update() methods are optional. You can implement either neither, one, or both of them, depending on the use-case for your serializer class.
Sometimes you'll want your view code to be able to inject additional data at the point of saving the instance. This additional data might include information like the current user, the current time, or anything else that is not part of the request data.
+
You can do so by including additional keyword arguments when calling .save(). For example:
+
serializer.save(owner=request.user)
+
+
Any additional keyword arguments will be included in the validated_data argument when .create() or .update() are called.
In some cases the .create() and .update() method names may not be meaningful. For example, in a contact form we may not be creating new instances, but instead sending an email or other message.
+
In these cases you might instead choose to override .save() directly, as being more readable and meaningful.
When deserializing data, you always need to call is_valid() before attempting to access the validated data, or save an object instance. If any validation errors occur, the .errors property will contain a dictionary representing the resulting error messages. For example:
+
serializer = CommentSerializer(data={'email': 'foobar', 'content': 'baz'})
+serializer.is_valid()
+# False
+serializer.errors
+# {'email': ['Enter a valid e-mail address.'], 'created': ['This field is required.']}
+
+
Each key in the dictionary will be the field name, and the values will be lists of strings of any error messages corresponding to that field. The non_field_errors key may also be present, and will list any general validation errors. The name of the non_field_errors key may be customized using the NON_FIELD_ERRORS_KEY REST framework setting.
+
When deserializing a list of items, errors will be returned as a list of dictionaries representing each of the deserialized items.
The .is_valid() method takes an optional raise_exception flag that will cause it to raise a serializers.ValidationError exception if there are validation errors.
+
These exceptions are automatically dealt with by the default exception handler that REST framework provides, and will return HTTP 400 Bad Request responses by default.
+
# Return a 400 response if the data was invalid.
+serializer.is_valid(raise_exception=True)
+
You can specify custom field-level validation by adding .validate_<field_name> methods to your Serializer subclass. These are similar to the .clean_<field_name> methods on Django forms.
+
These methods take a single argument, which is the field value that requires validation.
+
Your validate_<field_name> methods should return the validated value or raise a serializers.ValidationError. For example:
+
from rest_framework import serializers
+
+class BlogPostSerializer(serializers.Serializer):
+ title = serializers.CharField(max_length=100)
+ content = serializers.CharField()
+
+ def validate_title(self, value):
+ """
+ Check that the blog post is about Django.
+ """
+ if 'django' not in value.lower():
+ raise serializers.ValidationError("Blog post is not about Django")
+ return value
+
+
+
Note: If your <field_name> is declared on your serializer with the parameter required=False then this validation step will not take place if the field is not included.
To do any other validation that requires access to multiple fields, add a method called .validate() to your Serializer subclass. This method takes a single argument, which is a dictionary of field values. It should raise a serializers.ValidationError if necessary, or just return the validated values. For example:
+
from rest_framework import serializers
+
+class EventSerializer(serializers.Serializer):
+ description = serializers.CharField(max_length=100)
+ start = serializers.DateTimeField()
+ finish = serializers.DateTimeField()
+
+ def validate(self, data):
+ """
+ Check that start is before finish.
+ """
+ if data['start'] > data['finish']:
+ raise serializers.ValidationError("finish must occur after start")
+ return data
+
Individual fields on a serializer can include validators, by declaring them on the field instance, for example:
+
def multiple_of_ten(value):
+ if value % 10 != 0:
+ raise serializers.ValidationError('Not a multiple of ten')
+
+class GameRecord(serializers.Serializer):
+ score = IntegerField(validators=[multiple_of_ten])
+ ...
+
+
Serializer classes can also include reusable validators that are applied to the complete set of field data. These validators are included by declaring them on an inner Meta class, like so:
+
class EventSerializer(serializers.Serializer):
+ name = serializers.CharField()
+ room_number = serializers.IntegerField(choices=[101, 102, 103, 201])
+ date = serializers.DateField()
+
+ class Meta:
+ # Each room only has one event per day.
+ validators = UniqueTogetherValidator(
+ queryset=Event.objects.all(),
+ fields=['room_number', 'date']
+ )
+
When passing an initial object or queryset to a serializer instance, the object will be made available as .instance. If no initial object is passed then the .instance attribute will be None.
+
When passing data to a serializer instance, the unmodified data will be made available as .initial_data. If the data keyword argument is not passed then the .initial_data attribute will not exist.
By default, serializers must be passed values for all required fields or they will raise validation errors. You can use the partial argument in order to allow partial updates.
+
# Update `comment` with partial data
+serializer = CommentSerializer(comment, data={'content': 'foo bar'}, partial=True)
+
The previous examples are fine for dealing with objects that only have simple datatypes, but sometimes we also need to be able to represent more complex objects, where some of the attributes of an object might not be simple datatypes such as strings, dates or integers.
+
The Serializer class is itself a type of Field, and can be used to represent relationships where one object type is nested inside another.
+
class UserSerializer(serializers.Serializer):
+ email = serializers.EmailField()
+ username = serializers.CharField(max_length=100)
+
+class CommentSerializer(serializers.Serializer):
+ user = UserSerializer()
+ content = serializers.CharField(max_length=200)
+ created = serializers.DateTimeField()
+
+
If a nested representation may optionally accept the None value you should pass the required=False flag to the nested serializer.
+
class CommentSerializer(serializers.Serializer):
+ user = UserSerializer(required=False) # May be an anonymous user.
+ content = serializers.CharField(max_length=200)
+ created = serializers.DateTimeField()
+
+
Similarly if a nested representation should be a list of items, you should pass the many=True flag to the nested serialized.
+
class CommentSerializer(serializers.Serializer):
+ user = UserSerializer(required=False)
+ edits = EditItemSerializer(many=True) # A nested list of 'edit' items.
+ content = serializers.CharField(max_length=200)
+ created = serializers.DateTimeField()
+
When dealing with nested representations that support deserializing the data, any errors with nested objects will be nested under the field name of the nested object.
+
serializer = CommentSerializer(data={'user': {'email': 'foobar', 'username': 'doe'}, 'content': 'baz'})
+serializer.is_valid()
+# False
+serializer.errors
+# {'user': {'email': ['Enter a valid e-mail address.']}, 'created': ['This field is required.']}
+
+
Similarly, the .validated_data property will include nested data structures.
For updates you'll want to think carefully about how to handle updates to relationships. For example if the data for the relationship is None, or not provided, which of the following should occur?
+
+
Set the relationship to NULL in the database.
+
Delete the associated instance.
+
Ignore the data and leave the instance as it is.
+
Raise a validation error.
+
+
Here's an example for an .update() method on our previous UserSerializer class.
+
def update(self, instance, validated_data):
+ profile_data = validated_data.pop('profile')
+ # Unless the application properly enforces that this field is
+ # always set, the follow could raise a `DoesNotExist`, which
+ # would need to be handled.
+ profile = instance.profile
+
+ instance.username = validated_data.get('username', instance.username)
+ instance.email = validated_data.get('email', instance.email)
+ instance.save()
+
+ profile.is_premium_member = profile_data.get(
+ 'is_premium_member',
+ profile.is_premium_member
+ )
+ profile.has_support_contract = profile_data.get(
+ 'has_support_contract',
+ profile.has_support_contract
+ )
+ profile.save()
+
+ return instance
+
+
Because the behavior of nested creates and updates can be ambiguous, and may require complex dependencies between related models, REST framework 3 requires you to always write these methods explicitly. The default ModelSerializer.create() and .update() methods do not include support for writable nested representations.
+
There are however, third-party packages available such as DRF Writable Nested that support automatic writable nested representations.
An alternative to saving multiple related instances in the serializer is to write custom model manager classes that handle creating the correct instances.
+
For example, suppose we wanted to ensure that User instances and Profile instances are always created together as a pair. We might write a custom manager class that looks something like this:
This manager class now more nicely encapsulates that user instances and profile instances are always created at the same time. Our .create() method on the serializer class can now be re-written to use the new manager method.
To serialize a queryset or list of objects instead of a single object instance, you should pass the many=True flag when instantiating the serializer. You can then pass a queryset or list of objects to be serialized.
+
queryset = Book.objects.all()
+serializer = BookSerializer(queryset, many=True)
+serializer.data
+# [
+# {'id': 0, 'title': 'The electric kool-aid acid test', 'author': 'Tom Wolfe'},
+# {'id': 1, 'title': 'If this is a man', 'author': 'Primo Levi'},
+# {'id': 2, 'title': 'The wind-up bird chronicle', 'author': 'Haruki Murakami'}
+# ]
+
The default behavior for deserializing multiple objects is to support multiple object creation, but not support multiple object updates. For more information on how to support or customize either of these cases, see the ListSerializer documentation below.
There are some cases where you need to provide extra context to the serializer in addition to the object being serialized. One common case is if you're using a serializer that includes hyperlinked relations, which requires the serializer to have access to the current request so that it can properly generate fully qualified URLs.
+
You can provide arbitrary additional context by passing a context argument when instantiating the serializer. For example:
The context dictionary can be used within any serializer field logic, such as a custom .to_representation() method, by accessing the self.context attribute.
Often you'll want serializer classes that map closely to Django model definitions.
+
The ModelSerializer class provides a shortcut that lets you automatically create a Serializer class with fields that correspond to the Model fields.
+
The ModelSerializer class is the same as a regular Serializer class, except that:
+
+
It will automatically generate a set of fields for you, based on the model.
+
It will automatically generate validators for the serializer, such as unique_together validators.
+
It includes simple default implementations of .create() and .update().
+
+
Declaring a ModelSerializer looks like this:
+
class AccountSerializer(serializers.ModelSerializer):
+ class Meta:
+ model = Account
+ fields = ['id', 'account_name', 'users', 'created']
+
+
By default, all the model fields on the class will be mapped to a corresponding serializer fields.
+
Any relationships such as foreign keys on the model will be mapped to PrimaryKeyRelatedField. Reverse relationships are not included by default unless explicitly included as specified in the serializer relations documentation.
Serializer classes generate helpful verbose representation strings, that allow you to fully inspect the state of their fields. This is particularly useful when working with ModelSerializers where you want to determine what set of fields and validators are being automatically created for you.
+
To do so, open the Django shell, using python manage.py shell, then import the serializer class, instantiate it, and print the object representation…
+
>>> from myapp.serializers import AccountSerializer
+>>> serializer = AccountSerializer()
+>>> print(repr(serializer))
+AccountSerializer():
+ id = IntegerField(label='ID', read_only=True)
+ name = CharField(allow_blank=True, max_length=100, required=False)
+ owner = PrimaryKeyRelatedField(queryset=User.objects.all())
+
If you only want a subset of the default fields to be used in a model serializer, you can do so using fields or exclude options, just as you would with a ModelForm. It is strongly recommended that you explicitly set all fields that should be serialized using the fields attribute. This will make it less likely to result in unintentionally exposing data when your models change.
+
For example:
+
class AccountSerializer(serializers.ModelSerializer):
+ class Meta:
+ model = Account
+ fields = ['id', 'account_name', 'users', 'created']
+
+
You can also set the fields attribute to the special value '__all__' to indicate that all fields in the model should be used.
+
For example:
+
class AccountSerializer(serializers.ModelSerializer):
+ class Meta:
+ model = Account
+ fields = '__all__'
+
+
You can set the exclude attribute to a list of fields to be excluded from the serializer.
+
For example:
+
class AccountSerializer(serializers.ModelSerializer):
+ class Meta:
+ model = Account
+ exclude = ['users']
+
+
In the example above, if the Account model had 3 fields account_name, users, and created, this will result in the fields account_name and created to be serialized.
+
The names in the fields and exclude attributes will normally map to model fields on the model class.
+
Alternatively names in the fields options can map to properties or methods which take no arguments that exist on the model class.
+
Since version 3.3.0, it is mandatory to provide one of the attributes fields or exclude.
The default ModelSerializer uses primary keys for relationships, but you can also easily generate nested representations using the depth option:
+
class AccountSerializer(serializers.ModelSerializer):
+ class Meta:
+ model = Account
+ fields = ['id', 'account_name', 'users', 'created']
+ depth = 1
+
+
The depth option should be set to an integer value that indicates the depth of relationships that should be traversed before reverting to a flat representation.
+
If you want to customize the way the serialization is done you'll need to define the field yourself.
You can add extra fields to a ModelSerializer or override the default fields by declaring fields on the class, just as you would for a Serializer class.
+
class AccountSerializer(serializers.ModelSerializer):
+ url = serializers.CharField(source='get_absolute_url', read_only=True)
+ groups = serializers.PrimaryKeyRelatedField(many=True)
+
+ class Meta:
+ model = Account
+
+
Extra fields can correspond to any property or callable on the model.
You may wish to specify multiple fields as read-only. Instead of adding each field explicitly with the read_only=True attribute, you may use the shortcut Meta option, read_only_fields.
+
This option should be a list or tuple of field names, and is declared as follows:
+
class AccountSerializer(serializers.ModelSerializer):
+ class Meta:
+ model = Account
+ fields = ['id', 'account_name', 'users', 'created']
+ read_only_fields = ['account_name']
+
+
Model fields which have editable=False set, and AutoField fields will be set to read-only by default, and do not need to be added to the read_only_fields option.
+
+
Note: There is a special-case where a read-only field is part of a unique_together constraint at the model level. In this case the field is required by the serializer class in order to validate the constraint, but should also not be editable by the user.
+
The right way to deal with this is to specify the field explicitly on the serializer, providing both the read_only=True and default=… keyword arguments.
+
One example of this is a read-only relation to the currently authenticated User which is unique_together with another identifier. In this case you would declare the user field like so:
+
user = serializers.PrimaryKeyRelatedField(read_only=True, default=serializers.CurrentUserDefault())
+
There is also a shortcut allowing you to specify arbitrary additional keyword arguments on fields, using the extra_kwargs option. As in the case of read_only_fields, this means you do not need to explicitly declare the field on the serializer.
+
This option is a dictionary, mapping field names to a dictionary of keyword arguments. For example:
+
class CreateUserSerializer(serializers.ModelSerializer):
+ class Meta:
+ model = User
+ fields = ['email', 'username', 'password']
+ extra_kwargs = {'password': {'write_only': True}}
+
+ def create(self, validated_data):
+ user = User(
+ email=validated_data['email'],
+ username=validated_data['username']
+ )
+ user.set_password(validated_data['password'])
+ user.save()
+ return user
+
+
Please keep in mind that, if the field has already been explicitly declared on the serializer class, then the extra_kwargs option will be ignored.
When serializing model instances, there are a number of different ways you might choose to represent relationships. The default representation for ModelSerializer is to use the primary keys of the related instances.
+
Alternative representations include serializing using hyperlinks, serializing complete nested representations, or serializing with a custom representation.
The ModelSerializer class also exposes an API that you can override in order to alter how serializer fields are automatically determined when instantiating the serializer.
+
Normally if a ModelSerializer does not generate the fields you need by default then you should either add them to the class explicitly, or simply use a regular Serializer class instead. However in some cases you may want to create a new base class that defines how the serializer fields are created for any given model.
A mapping of Django model classes to REST framework serializer classes. You can override this mapping to alter the default serializer classes that should be used for each model class.
The following methods are called to determine the class and keyword arguments for each field that should be automatically included on the serializer. Each of these methods should return a two tuple of (field_class, field_kwargs).
Called when the field name did not map to any model field or model property.
+The default implementation raises an error, although subclasses may customize this behavior.
The HyperlinkedModelSerializer class is similar to the ModelSerializer class except that it uses hyperlinks to represent relationships, rather than primary keys.
+
By default the serializer will include a url field instead of a primary key field.
+
The url field will be represented using a HyperlinkedIdentityField serializer field, and any relationships on the model will be represented using a HyperlinkedRelatedField serializer field.
+
You can explicitly include the primary key by adding it to the fields option, for example:
+
class AccountSerializer(serializers.HyperlinkedModelSerializer):
+ class Meta:
+ model = Account
+ fields = ['url', 'id', 'account_name', 'users', 'created']
+
Doing so will ensure that the hyperlinks can include an appropriate hostname,
+so that the resulting representation uses fully qualified URLs, such as:
+
http://api.example.com/accounts/1/
+
+
Rather than relative URLs, such as:
+
/accounts/1/
+
+
If you do want to use relative URLs, you should explicitly pass {'request': None}
+in the serializer context.
There needs to be a way of determining which views should be used for hyperlinking to model instances.
+
By default hyperlinks are expected to correspond to a view name that matches the style '{model_name}-detail', and looks up the instance by a pk keyword argument.
+
You can override a URL field view name and lookup field by using either, or both of, the view_name and lookup_field options in the extra_kwargs setting, like so:
Tip: Properly matching together hyperlinked representations and your URL conf can sometimes be a bit fiddly. Printing the repr of a HyperlinkedModelSerializer instance is a particularly useful way to inspect exactly which view names and lookup fields the relationships are expected to map too.
The ListSerializer class provides the behavior for serializing and validating multiple objects at once. You won't typically need to use ListSerializer directly, but should instead simply pass many=True when instantiating a serializer.
+
When a serializer is instantiated and many=True is passed, a ListSerializer instance will be created. The serializer class then becomes a child of the parent ListSerializer
+
The following argument can also be passed to a ListSerializer field or a serializer that is passed many=True:
There are a few use cases when you might want to customize the ListSerializer behavior. For example:
+
+
You want to provide particular validation of the lists, such as checking that one element does not conflict with another element in a list.
+
You want to customize the create or update behavior of multiple objects.
+
+
For these cases you can modify the class that is used when many=True is passed, by using the list_serializer_class option on the serializer Meta class.
+
For example:
+
class CustomListSerializer(serializers.ListSerializer):
+ ...
+
+class CustomSerializer(serializers.Serializer):
+ ...
+ class Meta:
+ list_serializer_class = CustomListSerializer
+
The default implementation for multiple object creation is to simply call .create() for each item in the list. If you want to customize this behavior, you'll need to customize the .create() method on ListSerializer class that is used when many=True is passed.
+
For example:
+
class BookListSerializer(serializers.ListSerializer):
+ def create(self, validated_data):
+ books = [Book(**item) for item in validated_data]
+ return Book.objects.bulk_create(books)
+
+class BookSerializer(serializers.Serializer):
+ ...
+ class Meta:
+ list_serializer_class = BookListSerializer
+
By default the ListSerializer class does not support multiple updates. This is because the behavior that should be expected for insertions and deletions is ambiguous.
+
To support multiple updates you'll need to do so explicitly. When writing your multiple update code make sure to keep the following in mind:
+
+
How do you determine which instance should be updated for each item in the list of data?
+
How should insertions be handled? Are they invalid, or do they create new objects?
+
How should removals be handled? Do they imply object deletion, or removing a relationship? Should they be silently ignored, or are they invalid?
+
How should ordering be handled? Does changing the position of two items imply any state change or is it ignored?
+
+
You will need to add an explicit id field to the instance serializer. The default implicitly-generated id field is marked as read_only. This causes it to be removed on updates. Once you declare it explicitly, it will be available in the list serializer's update method.
+
Here's an example of how you might choose to implement multiple updates:
+
class BookListSerializer(serializers.ListSerializer):
+ def update(self, instance, validated_data):
+ # Maps for id->instance and id->data item.
+ book_mapping = {book.id: book for book in instance}
+ data_mapping = {item['id']: item for item in validated_data}
+
+ # Perform creations and updates.
+ ret = []
+ for book_id, data in data_mapping.items():
+ book = book_mapping.get(book_id, None)
+ if book is None:
+ ret.append(self.child.create(data))
+ else:
+ ret.append(self.child.update(book, data))
+
+ # Perform deletions.
+ for book_id, book in book_mapping.items():
+ if book_id not in data_mapping:
+ book.delete()
+
+ return ret
+
+class BookSerializer(serializers.Serializer):
+ # We need to identify elements in the list using their primary key,
+ # so use a writable field here, rather than the default which would be read-only.
+ id = serializers.IntegerField()
+ ...
+
+ class Meta:
+ list_serializer_class = BookListSerializer
+
+
It is possible that a third party package may be included alongside the 3.1 release that provides some automatic support for multiple update operations, similar to the allow_add_remove behavior that was present in REST framework 2.
When a serializer with many=True is instantiated, we need to determine which arguments and keyword arguments should be passed to the .__init__() method for both the child Serializer class, and for the parent ListSerializer class.
+
The default implementation is to pass all arguments to both classes, except for validators, and any custom keyword arguments, both of which are assumed to be intended for the child serializer class.
+
Occasionally you might need to explicitly specify how the child and parent classes should be instantiated when many=True is passed. You can do so by using the many_init class method.
+
@classmethod
+ def many_init(cls, *args, **kwargs):
+ # Instantiate the child serializer.
+ kwargs['child'] = cls()
+ # Instantiate the parent list serializer.
+ return CustomListSerializer(*args, **kwargs)
+
BaseSerializer class that can be used to easily support alternative serialization and deserialization styles.
+
This class implements the same basic API as the Serializer class:
+
+
.data - Returns the outgoing primitive representation.
+
.is_valid() - Deserializes and validates incoming data.
+
.validated_data - Returns the validated incoming data.
+
.errors - Returns any errors during validation.
+
.save() - Persists the validated data into an object instance.
+
+
There are four methods that can be overridden, depending on what functionality you want the serializer class to support:
+
+
.to_representation() - Override this to support serialization, for read operations.
+
.to_internal_value() - Override this to support deserialization, for write operations.
+
.create() and .update() - Override either or both of these to support saving instances.
+
+
Because this class provides the same interface as the Serializer class, you can use it with the existing generic class-based views exactly as you would for a regular Serializer or ModelSerializer.
+
The only difference you'll notice when doing so is the BaseSerializer classes will not generate HTML forms in the browsable API. This is because the data they return does not include all the field information that would allow each field to be rendered into a suitable HTML input.
To implement a read-only serializer using the BaseSerializer class, we just need to override the .to_representation() method. Let's take a look at an example using a simple Django model:
+
class HighScore(models.Model):
+ created = models.DateTimeField(auto_now_add=True)
+ player_name = models.CharField(max_length=10)
+ score = models.IntegerField()
+
+
It's simple to create a read-only serializer for converting HighScore instances into primitive data types.
To create a read-write serializer we first need to implement a .to_internal_value() method. This method returns the validated values that will be used to construct the object instance, and may raise a serializers.ValidationError if the supplied data is in an incorrect format.
+
Once you've implemented .to_internal_value(), the basic validation API will be available on the serializer, and you will be able to use .is_valid(), .validated_data and .errors.
+
If you want to also support .save() you'll need to also implement either or both of the .create() and .update() methods.
+
Here's a complete example of our previous HighScoreSerializer, that's been updated to support both read and write operations.
+
class HighScoreSerializer(serializers.BaseSerializer):
+ def to_internal_value(self, data):
+ score = data.get('score')
+ player_name = data.get('player_name')
+
+ # Perform the data validation.
+ if not score:
+ raise serializers.ValidationError({
+ 'score': 'This field is required.'
+ })
+ if not player_name:
+ raise serializers.ValidationError({
+ 'player_name': 'This field is required.'
+ })
+ if len(player_name) > 10:
+ raise serializers.ValidationError({
+ 'player_name': 'May not be more than 10 characters.'
+ })
+
+ # Return the validated values. This will be available as
+ # the `.validated_data` property.
+ return {
+ 'score': int(score),
+ 'player_name': player_name
+ }
+
+ def to_representation(self, instance):
+ return {
+ 'score': instance.score,
+ 'player_name': instance.player_name
+ }
+
+ def create(self, validated_data):
+ return HighScore.objects.create(**validated_data)
+
The BaseSerializer class is also useful if you want to implement new generic serializer classes for dealing with particular serialization styles, or for integrating with alternative storage backends.
+
The following class is an example of a generic serializer that can handle coercing arbitrary objects into primitive representations.
+
class ObjectSerializer(serializers.BaseSerializer):
+ """
+ A read-only serializer that coerces arbitrary complex objects
+ into primitive representations.
+ """
+ def to_representation(self, instance):
+ output = {}
+ for attribute_name in dir(instance):
+ attribute = getattr(instance, attribute_name)
+ if attribute_name.startswith('_'):
+ # Ignore private attributes.
+ pass
+ elif hasattr(attribute, '__call__'):
+ # Ignore methods and other callables.
+ pass
+ elif isinstance(attribute, (str, int, bool, float, type(None))):
+ # Primitive types can be passed through unmodified.
+ output[attribute_name] = attribute
+ elif isinstance(attribute, list):
+ # Recursively deal with items in lists.
+ output[attribute_name] = [
+ self.to_representation(item) for item in attribute
+ ]
+ elif isinstance(attribute, dict):
+ # Recursively deal with items in dictionaries.
+ output[attribute_name] = {
+ str(key): self.to_representation(value)
+ for key, value in attribute.items()
+ }
+ else:
+ # Force anything else to its string representation.
+ output[attribute_name] = str(attribute)
+ return output
+
If you need to alter the serialization or deserialization behavior of a serializer class, you can do so by overriding the .to_representation() or .to_internal_value() methods.
+
Some reasons this might be useful include...
+
+
Adding new behavior for new serializer base classes.
+
Modifying the behavior slightly for an existing class.
+
Improving serialization performance for a frequently accessed API endpoint that returns lots of data.
Takes the object instance that requires serialization, and should return a primitive representation. Typically this means returning a structure of built-in Python datatypes. The exact types that can be handled will depend on the render classes you have configured for your API.
+
May be overridden in order to modify the representation style. For example:
+
def to_representation(self, instance):
+ """Convert `username` to lowercase."""
+ ret = super().to_representation(instance)
+ ret['username'] = ret['username'].lower()
+ return ret
+
Takes the unvalidated incoming data as input and should return the validated data that will be made available as serializer.validated_data. The return value will also be passed to the .create() or .update() methods if .save() is called on the serializer class.
+
If any of the validation fails, then the method should raise a serializers.ValidationError(errors). The errors argument should be a dictionary mapping field names (or settings.NON_FIELD_ERRORS_KEY) to a list of error messages. If you don't need to alter deserialization behavior and instead want to provide object-level validation, it's recommended that you instead override the .validate() method.
+
The data argument passed to this method will normally be the value of request.data, so the datatype it provides will depend on the parser classes you have configured for your API.
Similar to Django forms, you can extend and reuse serializers through inheritance. This allows you to declare a common set of fields or methods on a parent class that can then be used in a number of serializers. For example,
Like Django's Model and ModelForm classes, the inner Meta class on serializers does not implicitly inherit from it's parents' inner Meta classes. If you want the Meta class to inherit from a parent class you must do so explicitly. For example:
+
class AccountSerializer(MyBaseSerializer):
+ class Meta(MyBaseSerializer.Meta):
+ model = Account
+
+
Typically we would recommend not using inheritance on inner Meta classes, but instead declaring all options explicitly.
+
Additionally, the following caveats apply to serializer inheritance:
+
+
Normal Python name resolution rules apply. If you have multiple base classes that declare a Meta inner class, only the first one will be used. This means the child’s Meta, if it exists, otherwise the Meta of the first parent, etc.
+
+
It’s possible to declaratively remove a Field inherited from a parent class by setting the name to be None on the subclass.
However, you can only use this technique to opt out from a field defined declaratively by a parent class; it won’t prevent the ModelSerializer from generating a default field. To opt-out from default fields, see Specifying which fields to include.
Once a serializer has been initialized, the dictionary of fields that are set on the serializer may be accessed using the .fields attribute. Accessing and modifying this attribute allows you to dynamically modify the serializer.
+
Modifying the fields argument directly allows you to do interesting things such as changing the arguments on serializer fields at runtime, rather than at the point of declaring the serializer.
For example, if you wanted to be able to set which fields should be used by a serializer at the point of initializing it, you could create a serializer class like so:
+
class DynamicFieldsModelSerializer(serializers.ModelSerializer):
+ """
+ A ModelSerializer that takes an additional `fields` argument that
+ controls which fields should be displayed.
+ """
+
+ def __init__(self, *args, **kwargs):
+ # Don't pass the 'fields' arg up to the superclass
+ fields = kwargs.pop('fields', None)
+
+ # Instantiate the superclass normally
+ super(DynamicFieldsModelSerializer, self).__init__(*args, **kwargs)
+
+ if fields is not None:
+ # Drop any fields that are not specified in the `fields` argument.
+ allowed = set(fields)
+ existing = set(self.fields)
+ for field_name in existing - allowed:
+ self.fields.pop(field_name)
+
+
This would then allow you to do the following:
+
>>> class UserSerializer(DynamicFieldsModelSerializer):
+>>> class Meta:
+>>> model = User
+>>> fields = ['id', 'username', 'email']
+>>>
+>>> print(UserSerializer(user))
+{'id': 2, 'username': 'jonwatts', 'email': 'jon@example.com'}
+>>>
+>>> print(UserSerializer(user, fields=('id', 'email')))
+{'id': 2, 'email': 'jon@example.com'}
+
REST framework 2 provided an API to allow developers to override how a ModelSerializer class would automatically generate the default set of fields.
+
This API included the .get_field(), .get_pk_field() and other methods.
+
Because the serializers have been fundamentally redesigned with 3.0 this API no longer exists. You can still modify the fields that get created but you'll need to refer to the source code, and be aware that if the changes you make are against private bits of API then they may be subject to change.
The django-rest-marshmallow package provides an alternative implementation for serializers, using the python marshmallow library. It exposes the same API as the REST framework serializers, and can be used as a drop-in replacement in some use-cases.
The serpy package is an alternative implementation for serializers that is built for speed. Serpy serializes complex datatypes to simple native types. The native types can be easily converted to JSON or any other format needed.
The django-rest-framework-mongoengine package provides a MongoEngineModelSerializer serializer class that supports using MongoDB as the storage layer for Django REST framework.
The dynamic-rest package extends the ModelSerializer and ModelViewSet interfaces, adding API query parameters for filtering, sorting, and including / excluding all fields and relationships defined by your serializers.
The drf-flex-fields package extends the ModelSerializer and ModelViewSet to provide commonly used functionality for dynamically setting fields and expanding primitive fields to nested models, both from URL parameters and your serializer class definitions.
The django-rest-framework-serializer-extensions
+package provides a collection of tools to DRY up your serializers, by allowing
+fields to be defined on a per-view/request basis. Fields can be whitelisted,
+blacklisted and child serializers can be optionally expanded.
The html-json-forms package provides an algorithm and serializer for processing <form> submissions per the (inactive) HTML JSON Form specification. The serializer facilitates processing of arbitrarily nested JSON structures within HTML. For example, <input name="items[0][id]" value="5"> will be interpreted as {"items": [{"id": "5"}]}.
If you need to access the values of REST framework's API settings in your project,
+you should use the api_settings object. For example.
+
from rest_framework.settings import api_settings
+
+print(api_settings.DEFAULT_AUTHENTICATION_CLASSES)
+
+
The api_settings object will check for any user-defined settings, and otherwise fall back to the default values. Any setting that uses string import paths to refer to a class will automatically import and return the referenced class, instead of the string literal.
A list or tuple of authentication classes, that determines the default set of authenticators used when accessing the request.user or request.auth properties.
A list or tuple of permission classes, that determines the default set of permissions checked at the start of a view. Permission must be granted by every class in the list.
The default class to use for queryset pagination. If set to None, pagination
+is disabled by default. See the pagination documentation for further guidance on
+setting and
+modifying the pagination style.
If set, this value will restrict the set of versions that may be returned by the versioning scheme, and will raise an error if the provided version if not in this set.
The class that should be used to initialize request.user for unauthenticated requests.
+(If removing authentication entirely, e.g. by removing django.contrib.auth from
+INSTALLED_APPS, set UNAUTHENTICATED_USER to None.)
The renderer classes that are supported when building test requests.
+
The format of any of these renderer classes may be used when constructing a test request, for example: client.post('/users', {'username': 'jamie'}, format='json')
If set, this maps the 'pk' identifier in the URL conf onto the actual field
+name when generating a schema path parameter. Typically this will be 'id'.
+This gives a more suitable representation as "primary key" is an implementation
+detail, whereas "identifier" is a more general concept.
If set, this is used to map internal viewset method names onto external action
+names used in the schema generation. This allows us to generate names that
+are more suitable for an external representation than those that are used
+internally in the codebase.
The name of a URL parameter that may be used to override the default content negotiation Accept header behavior, by using a format=… query parameter in the request URL.
+
For example: http://example.com/organizations/?format=csv
+
If the value of this setting is None then URL format overrides will be disabled.
The name of a parameter in the URL conf that may be used to provide a format suffix. This setting is applied when using format_suffix_patterns to include suffixed URL patterns.
+
For example: http://example.com/organizations.csv/
A format string that should be used by default for rendering the output of DateTimeField serializer fields. If None, then DateTimeField serializer fields will return Python datetime objects, and the datetime encoding will be determined by the renderer.
+
May be any of None, 'iso-8601' or a Python strftime format string.
A format string that should be used by default for rendering the output of DateField serializer fields. If None, then DateField serializer fields will return Python date objects, and the date encoding will be determined by the renderer.
+
May be any of None, 'iso-8601' or a Python strftime format string.
A format string that should be used by default for rendering the output of TimeField serializer fields. If None, then TimeField serializer fields will return Python time objects, and the time encoding will be determined by the renderer.
+
May be any of None, 'iso-8601' or a Python strftime format string.
When set to True, JSON responses will allow unicode characters in responses. For example:
+
{"unicode black star":"★"}
+
+
When set to False, JSON responses will escape non-ascii characters, like so:
+
{"unicode black star":"\u2605"}
+
+
Both styles conform to RFC 4627, and are syntactically valid JSON. The unicode style is preferred as being more user-friendly when inspecting API responses.
When set to True, JSON rendering and parsing will only observe syntactically valid JSON, raising an exception for the extended float values (nan, inf, -inf) accepted by Python's json module. This is the recommended setting, as these values are not generally supported. e.g., neither Javascript's JSON.Parse nor PostgreSQL's JSON data type accept these values.
+
When set to False, JSON rendering and parsing will be permissive. However, these values are still invalid and will need to be specially handled in your code.
When returning decimal objects in API representations that do not support a native decimal type, it is normally best to return the value as a string. This avoids the loss of precision that occurs with binary floating point implementations.
+
When set to True, the serializer DecimalField class will return strings instead of Decimal objects. When set to False, serializers will return Decimal objects, which the default JSON encoder will return as floats.
The following settings are used to generate the view names and descriptions, as used in responses to OPTIONS requests, and as used in the browsable API.
A string representing the function that should be used when generating view names.
+
This should be a function with the following signature:
+
view_name(self)
+
+
+
self: The view instance. Typically the name function would inspect the name of the class when generating a descriptive name, by accessing self.__class__.__name__.
+
+
If the view instance inherits ViewSet, it may have been initialized with several optional arguments:
+
+
name: A name explicitly provided to a view in the viewset. Typically, this value should be used as-is when provided.
+
suffix: Text used when differentiating individual views in a viewset. This argument is mutually exclusive to name.
+
detail: Boolean that differentiates an individual view in a viewset as either being a 'list' or 'detail' view.
A string representing the function that should be used when generating view descriptions.
+
This setting can be changed to support markup styles other than the default markdown. For example, you can use it to support rst markup in your view docstrings being output in the browsable API.
+
This should be a function with the following signature:
+
view_description(self, html=False)
+
+
+
self: The view instance. Typically the description function would inspect the docstring of the class when generating a description, by accessing self.__class__.__doc__
+
html: A boolean indicating if HTML output is required. True when used in the browsable API, and False when used in generating OPTIONS responses.
+
+
If the view instance inherits ViewSet, it may have been initialized with several optional arguments:
+
+
description: A description explicitly provided to the view in the viewset. Typically, this is set by extra viewset actions, and should be used as-is.
A string representing the function that should be used when returning a response for any given exception. If the function returns None, a 500 error will be raised.
+
This setting can be changed to support error responses other than the default {"detail": "Failure..."} responses. For example, you can use it to provide API responses like {"errors": [{"message": "Failure...", "code": ""} ...]}.
+
This should be a function with the following signature:
An integer of 0 or more, that may be used to specify the number of application proxies that the API runs behind. This allows throttling to more accurately identify client IP addresses. If set to None then less strict IP matching will be used by the throttle classes.
418 I'm a teapot - Any attempt to brew coffee with a teapot should result in the error code "418 I'm a teapot". The resulting entity body MAY be short and stout.
+
— RFC 2324, Hyper Text Coffee Pot Control Protocol
+
+
Using bare status codes in your responses isn't recommended. REST framework includes a set of named constants that you can use to make your code more obvious and readable.
+
from rest_framework import status
+from rest_framework.response import Response
+
+def empty_view(self):
+ content = {'please move along': 'nothing to see here'}
+ return Response(content, status=status.HTTP_404_NOT_FOUND)
+
+
The full set of HTTP status codes included in the status module is listed below.
+
The module also includes a set of helper functions for testing if a status code is in a given range.
The 4xx class of status code is intended for cases in which the client seems to have erred. Except when responding to a HEAD request, the server SHOULD include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition.
Response status codes beginning with the digit "5" indicate cases in which the server is aware that it has erred or is incapable of performing the request. Except when responding to a HEAD request, the server SHOULD include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition.
The APIRequestFactory class supports an almost identical API to Django's standard RequestFactory class. This means that the standard .get(), .post(), .put(), .patch(), .delete(), .head() and .options() methods are all available.
+
from rest_framework.test import APIRequestFactory
+
+# Using the standard RequestFactory API to create a form POST request
+factory = APIRequestFactory()
+request = factory.post('/notes/', {'title': 'new idea'})
+
Methods which create a request body, such as post, put and patch, include a format argument, which make it easy to generate requests using a content type other than multipart form data. For example:
+
# Create a JSON POST request
+factory = APIRequestFactory()
+request = factory.post('/notes/', {'title': 'new idea'}, format='json')
+
+
By default the available formats are 'multipart' and 'json'. For compatibility with Django's existing RequestFactory the default format is 'multipart'.
One difference worth noting between Django's RequestFactory and REST framework's APIRequestFactory is that multipart form data will be encoded for methods other than just .post().
+
For example, using APIRequestFactory, you can make a form PUT request like so:
When testing views directly using a request factory, it's often convenient to be able to directly authenticate the request, rather than having to construct the correct authentication credentials.
+
To forcibly authenticate a request, use the force_authenticate() method.
+
from rest_framework.test import force_authenticate
+
+factory = APIRequestFactory()
+user = User.objects.get(username='olivia')
+view = AccountDetail.as_view()
+
+# Make an authenticated request to the view...
+request = factory.get('/accounts/django-superstars/')
+force_authenticate(request, user=user)
+response = view(request)
+
+
The signature for the method is force_authenticate(request, user=None, token=None). When making the call, either or both of the user and token may be set.
+
For example, when forcibly authenticating using a token, you might do something like the following:
+
user = User.objects.get(username='olivia')
+request = factory.get('/accounts/django-superstars/')
+force_authenticate(request, user=user, token=user.auth_token)
+
+
+
Note: force_authenticate directly sets request.user to the in-memory user instance. If you are re-using the same user instance across multiple tests that update the saved user state, you may need to call refresh_from_db() between tests.
+
+
Note: When using APIRequestFactory, the object that is returned is Django's standard HttpRequest, and not REST framework's Request object, which is only generated once the view is called.
+
This means that setting attributes directly on the request object may not always have the effect you expect. For example, setting .token directly will have no effect, and setting .user directly will only work if session authentication is being used.
+
# Request will only authenticate if `SessionAuthentication` is in use.
+request = factory.get('/accounts/django-superstars/')
+request.user = user
+response = view(request)
+
By default, requests created with APIRequestFactory will not have CSRF validation applied when passed to a REST framework view. If you need to explicitly turn CSRF validation on, you can do so by setting the enforce_csrf_checks flag when instantiating the factory.
Note: It's worth noting that Django's standard RequestFactory doesn't need to include this option, because when using regular Django the CSRF validation takes place in middleware, which is not run when testing views directly. When using REST framework, CSRF validation takes place inside the view, so the request factory needs to disable view-level CSRF checks.
The APIClient class supports the same request interface as Django's standard Client class. This means that the standard .get(), .post(), .put(), .patch(), .delete(), .head() and .options() methods are all available. For example:
The login method functions exactly as it does with Django's regular Client class. This allows you to authenticate requests against any views which include SessionAuthentication.
+
# Make all requests in the context of a logged in session.
+client = APIClient()
+client.login(username='lauren', password='secret')
+
+
To logout, call the logout method as usual.
+
# Log out
+client.logout()
+
+
The login method is appropriate for testing APIs that use session authentication, for example web sites which include AJAX interaction with the API.
The credentials method can be used to set headers that will then be included on all subsequent requests by the test client.
+
from rest_framework.authtoken.models import Token
+from rest_framework.test import APIClient
+
+# Include an appropriate `Authorization:` header on all requests.
+token = Token.objects.get(user__username='lauren')
+client = APIClient()
+client.credentials(HTTP_AUTHORIZATION='Token ' + token.key)
+
+
Note that calling credentials a second time overwrites any existing credentials. You can unset any existing credentials by calling the method with no arguments.
+
# Stop including any credentials
+client.credentials()
+
+
The credentials method is appropriate for testing APIs that require authentication headers, such as basic authentication, OAuth1a and OAuth2 authentication, and simple token authentication schemes.
Sometimes you may want to bypass authentication entirely and force all requests by the test client to be automatically treated as authenticated.
+
This can be a useful shortcut if you're testing the API but don't want to have to construct valid authentication credentials in order to make test requests.
+
user = User.objects.get(username='lauren')
+client = APIClient()
+client.force_authenticate(user=user)
+
+
To unauthenticate subsequent requests, call force_authenticate setting the user and/or token to None.
By default CSRF validation is not applied when using APIClient. If you need to explicitly enable CSRF validation, you can do so by setting the enforce_csrf_checks flag when instantiating the client.
+
client = APIClient(enforce_csrf_checks=True)
+
+
As usual CSRF validation will only apply to any session authenticated views. This means CSRF validation will only occur if the client has been logged in by calling login().
REST framework also includes a client for interacting with your application
+using the popular Python library, requests. This may be useful if:
+
+
You are expecting to interface with the API primarily from another Python service,
+and want to test the service at the same level as the client will see.
+
You want to write tests in such a way that they can also be run against a staging or
+live environment. (See "Live tests" below.)
+
+
This exposes exactly the same interface as if you were using a requests session
+directly.
The RequestsClient class is useful if you want to write tests that solely interact with the service interface. This is a little stricter than using the standard Django test client, as it means that all interactions should be via the API.
+
If you're using RequestsClient you'll want to ensure that test setup, and results assertions are performed as regular API calls, rather than interacting with the database models directly. For example, rather than checking that Customer.objects.count() == 3 you would list the customers endpoint, and ensure that it contains three records.
If you're using SessionAuthentication then you'll need to include a CSRF token
+for any POST, PUT, PATCH or DELETE requests.
+
You can do so by following the same flow that a JavaScript based client would use.
+First make a GET request in order to obtain a CRSF token, then present that
+token in the following request.
With careful usage both the RequestsClient and the CoreAPIClient provide
+the ability to write test cases that can run either in development, or be run
+directly against your staging server or production environment.
+
Using this style to create basic tests of a few core piece of functionality is
+a powerful way to validate your live service. Doing so may require some careful
+attention to setup and teardown to ensure that the tests run in a way that they
+do not directly affect customer data.
REST framework includes the following test case classes, that mirror the existing Django test case classes, but use APIClient instead of Django's default Client.
You can use any of REST framework's test case classes as you would for the regular Django test case classes. The self.client attribute will be an APIClient instance.
+
from django.urls import reverse
+from rest_framework import status
+from rest_framework.test import APITestCase
+from myproject.apps.core.models import Account
+
+class AccountTests(APITestCase):
+ def test_create_account(self):
+ """
+ Ensure we can create a new account object.
+ """
+ url = reverse('account-list')
+ data = {'name': 'DabApps'}
+ response = self.client.post(url, data, format='json')
+ self.assertEqual(response.status_code, status.HTTP_201_CREATED)
+ self.assertEqual(Account.objects.count(), 1)
+ self.assertEqual(Account.objects.get().name, 'DabApps')
+
REST framework also provides a test case class for isolating urlpatterns on a per-class basis. Note that this inherits from Django's SimpleTestCase, and will most likely need to be mixed with another test case class.
When checking the validity of test responses it's often more convenient to inspect the data that the response was created with, rather than inspecting the fully rendered response.
+
For example, it's easier to inspect response.data:
If you're testing views directly using APIRequestFactory, the responses that are returned will not yet be rendered, as rendering of template responses is performed by Django's internal request-response cycle. In order to access response.content, you'll first need to render the response.
The default format used to make test requests may be set using the TEST_REQUEST_DEFAULT_FORMAT setting key. For example, to always use JSON for test requests by default instead of standard multipart form requests, set the following in your settings.py file:
If you need to test requests using something other than multipart or json requests, you can do so by setting the TEST_REQUEST_RENDERER_CLASSES setting.
+
For example, to add support for using format='html' in test requests, you might have something like this in your settings.py file.
Throttling is similar to permissions, in that it determines if a request should be authorized. Throttles indicate a temporary state, and are used to control the rate of requests that clients can make to an API.
+
As with permissions, multiple throttles may be used. Your API might have a restrictive throttle for unauthenticated requests, and a less restrictive throttle for authenticated requests.
+
Another scenario where you might want to use multiple throttles would be if you need to impose different constraints on different parts of the API, due to some services being particularly resource-intensive.
+
Multiple throttles can also be used if you want to impose both burst throttling rates, and sustained throttling rates. For example, you might want to limit a user to a maximum of 60 requests per minute, and 1000 requests per day.
+
Throttles do not necessarily only refer to rate-limiting requests. For example a storage service might also need to throttle against bandwidth, and a paid data service might want to throttle against a certain number of a records being accessed.
As with permissions and authentication, throttling in REST framework is always defined as a list of classes.
+
Before running the main body of the view each throttle in the list is checked.
+If any throttle check fails an exceptions.Throttled exception will be raised, and the main body of the view will not run.
The X-Forwarded-For HTTP header and REMOTE_ADDR WSGI variable are used to uniquely identify client IP addresses for throttling. If the X-Forwarded-For header is present then it will be used, otherwise the value of the REMOTE_ADDR variable from the WSGI environment will be used.
+
If you need to strictly identify unique client IP addresses, you'll need to first configure the number of application proxies that the API runs behind by setting the NUM_PROXIES setting. This setting should be an integer of zero or more. If set to non-zero then the client IP will be identified as being the last IP address in the X-Forwarded-For header, once any application proxy IP addresses have first been excluded. If set to zero, then the REMOTE_ADDR value will always be used as the identifying IP address.
+
It is important to understand that if you configure the NUM_PROXIES setting, then all clients behind a unique NAT'd gateway will be treated as a single client.
+
Further context on how the X-Forwarded-For header works, and identifying a remote client IP can be found here.
The throttle classes provided by REST framework use Django's cache backend. You should make sure that you've set appropriate cache settings. The default value of LocMemCache backend should be okay for simple setups. See Django's cache documentation for more details.
+
If you need to use a cache other than 'default', you can do so by creating a custom throttle class and setting the cache attribute. For example:
You'll need to remember to also set your custom throttle class in the 'DEFAULT_THROTTLE_CLASSES' settings key, or using the throttle_classes view attribute.
The AnonRateThrottle will only ever throttle unauthenticated users. The IP address of the incoming request is used to generate a unique key to throttle against.
+
The allowed request rate is determined from one of the following (in order of preference).
+
+
The rate property on the class, which may be provided by overriding AnonRateThrottle and setting the property.
+
The DEFAULT_THROTTLE_RATES['anon'] setting.
+
+
AnonRateThrottle is suitable if you want to restrict the rate of requests from unknown sources.
The UserRateThrottle will throttle users to a given rate of requests across the API. The user id is used to generate a unique key to throttle against. Unauthenticated requests will fall back to using the IP address of the incoming request to generate a unique key to throttle against.
+
The allowed request rate is determined from one of the following (in order of preference).
+
+
The rate property on the class, which may be provided by overriding UserRateThrottle and setting the property.
+
The DEFAULT_THROTTLE_RATES['user'] setting.
+
+
An API may have multiple UserRateThrottles in place at the same time. To do so, override UserRateThrottle and set a unique "scope" for each class.
+
For example, multiple user throttle rates could be implemented by using the following classes...
The ScopedRateThrottle class can be used to restrict access to specific parts of the API. This throttle will only be applied if the view that is being accessed includes a .throttle_scope property. The unique throttle key will then be formed by concatenating the "scope" of the request with the unique user id or IP address.
+
The allowed request rate is determined by the DEFAULT_THROTTLE_RATES setting using a key from the request "scope".
User requests to either ContactListView or ContactDetailView would be restricted to a total of 1000 requests per-day. User requests to UploadView would be restricted to 20 requests per day.
To create a custom throttle, override BaseThrottle and implement .allow_request(self, request, view). The method should return True if the request should be allowed, and False otherwise.
+
Optionally you may also override the .wait() method. If implemented, .wait() should return a recommended number of seconds to wait before attempting the next request, or None. The .wait() method will only be called if .allow_request() has previously returned False.
+
If the .wait() method is implemented and the request is throttled, then a Retry-After header will be included in the response.
Most of the time you're dealing with validation in REST framework you'll simply be relying on the default field validation, or writing explicit validation methods on serializer or field classes.
+
However, sometimes you'll want to place your validation logic into reusable components, so that it can easily be reused throughout your codebase. This can be achieved by using validator functions and validator classes.
Validation in Django REST framework serializers is handled a little differently to how validation works in Django's ModelForm class.
+
With ModelForm the validation is performed partially on the form, and partially on the model instance. With REST framework the validation is performed entirely on the serializer class. This is advantageous for the following reasons:
+
+
It introduces a proper separation of concerns, making your code behavior more obvious.
+
It is easy to switch between using shortcut ModelSerializer classes and using explicit Serializer classes. Any validation behavior being used for ModelSerializer is simple to replicate.
+
Printing the repr of a serializer instance will show you exactly what validation rules it applies. There's no extra hidden validation behavior being called on the model instance.
+
+
When you're using ModelSerializer all of this is handled automatically for you. If you want to drop down to using Serializer classes instead, then you need to define the validation rules explicitly.
The interesting bit here is the reference field. We can see that the uniqueness constraint is being explicitly enforced by a validator on the serializer field.
+
Because of this more explicit style REST framework includes a few validator classes that are not available in core Django. These classes are detailed below.
This validator can be used to enforce the unique=True constraint on model fields.
+It takes a single required argument, and an optional messages argument:
+
+
querysetrequired - This is the queryset against which uniqueness should be enforced.
+
message - The error message that should be used when validation fails.
+
lookup - The lookup used to find an existing instance with the value being validated. Defaults to 'exact'.
+
+
This validator should be applied to serializer fields, like so:
This validator can be used to enforce unique_together constraints on model instances.
+It has two required arguments, and a single optional messages argument:
+
+
querysetrequired - This is the queryset against which uniqueness should be enforced.
+
fieldsrequired - A list or tuple of field names which should make a unique set. These must exist as fields on the serializer class.
+
message - The error message that should be used when validation fails.
+
+
The validator should be applied to serializer classes, like so:
+
from rest_framework.validators import UniqueTogetherValidator
+
+class ExampleSerializer(serializers.Serializer):
+ # ...
+ class Meta:
+ # ToDo items belong to a parent list, and have an ordering defined
+ # by the 'position' field. No two items in a given list may share
+ # the same position.
+ validators = [
+ UniqueTogetherValidator(
+ queryset=ToDoItem.objects.all(),
+ fields=['list', 'position']
+ )
+ ]
+
+
+
Note: The UniqueTogetherValidator class always imposes an implicit constraint that all the fields it applies to are always treated as required. Fields with default values are an exception to this as they always supply a value even when omitted from user input.
These validators can be used to enforce the unique_for_date, unique_for_month and unique_for_year constraints on model instances. They take the following arguments:
+
+
querysetrequired - This is the queryset against which uniqueness should be enforced.
+
fieldrequired - A field name against which uniqueness in the given date range will be validated. This must exist as a field on the serializer class.
+
date_fieldrequired - A field name which will be used to determine date range for the uniqueness constrain. This must exist as a field on the serializer class.
+
message - The error message that should be used when validation fails.
+
+
The validator should be applied to serializer classes, like so:
+
from rest_framework.validators import UniqueForYearValidator
+
+class ExampleSerializer(serializers.Serializer):
+ # ...
+ class Meta:
+ # Blog posts should have a slug that is unique for the current year.
+ validators = [
+ UniqueForYearValidator(
+ queryset=BlogPostItem.objects.all(),
+ field='slug',
+ date_field='published'
+ )
+ ]
+
+
The date field that is used for the validation is always required to be present on the serializer class. You can't simply rely on a model class default=..., because the value being used for the default wouldn't be generated until after the validation has run.
+
There are a couple of styles you may want to use for this depending on how you want your API to behave. If you're using ModelSerializer you'll probably simply rely on the defaults that REST framework generates for you, but if you are using Serializer or simply want more explicit control, use on of the styles demonstrated below.
If you want the date field to be writable the only thing worth noting is that you should ensure that it is always available in the input data, either by setting a default argument, or by setting required=True.
+
published = serializers.DateTimeField(required=True)
+
If you want the date field to be entirely hidden from the user, then use HiddenField. This field type does not accept user input, but instead always returns its default value to the validated_data in the serializer.
+
published = serializers.HiddenField(default=timezone.now)
+
+
+
Note: The UniqueFor<Range>Validator classes impose an implicit constraint that the fields they are applied to are always treated as required. Fields with default values are an exception to this as they always supply a value even when omitted from user input.
Validators that are applied across multiple fields in the serializer can sometimes require a field input that should not be provided by the API client, but that is available as input to the validator.
+
Two patterns that you may want to use for this sort of validation include:
+
+
Using HiddenField. This field will be present in validated_data but will not be used in the serializer output representation.
+
Using a standard field with read_only=True, but that also includes a default=… argument. This field will be used in the serializer output representation, but cannot be set directly by the user.
+
+
REST framework includes a couple of defaults that may be useful in this context.
A default class that can be used to represent the current user. In order to use this, the 'request' must have been provided as part of the context dictionary when instantiating the serializer.
There are some ambiguous cases where you'll need to instead handle validation
+explicitly, rather than relying on the default serializer classes that
+ModelSerializer generates.
+
In these cases you may want to disable the automatically generated validators,
+by specifying an empty list for the serializer Meta.validators attribute.
By default "unique together" validation enforces that all fields be
+required=True. In some cases, you might want to explicit apply
+required=False to one of the fields, in which case the desired behaviour
+of the validation is ambiguous.
+
In this case you will typically need to exclude the validator from the
+serializer class, and instead write any validation logic explicitly, either
+in the .validate() method, or else in the view.
+
For example:
+
class BillingRecordSerializer(serializers.ModelSerializer):
+ def validate(self, attrs):
+ # Apply custom validation either here, or in the view.
+
+ class Meta:
+ fields = ['client', 'date', 'amount']
+ extra_kwargs = {'client': {'required': False}}
+ validators = [] # Remove a default "unique together" constraint.
+
When applying an update to an existing instance, uniqueness validators will
+exclude the current instance from the uniqueness check. The current instance
+is available in the context of the uniqueness check, because it exists as
+an attribute on the serializer, having initially been passed using
+instance=... when instantiating the serializer.
+
In the case of update operations on nested serializers there's no way of
+applying this exclusion, because the instance is not available.
+
Again, you'll probably want to explicitly remove the validator from the
+serializer class, and write the code the for the validation constraint
+explicitly, in a .validate() method, or in the view.
If you're not sure exactly what behavior a ModelSerializer class will
+generate it is usually a good idea to run manage.py shell, and print
+an instance of the serializer, so that you can inspect the fields and
+validators that it automatically generates for you.
Also keep in mind that with complex cases it can often be better to explicitly
+define your serializer classes, rather than relying on the default
+ModelSerializer behavior. This involves a little more code, but ensures
+that the resulting behavior is more transparent.
You can specify custom field-level validation by adding .validate_<field_name> methods
+to your Serializer subclass. This is documented in the
+Serializer docs
To write a class-based validator, use the __call__ method. Class-based validators are useful as they allow you to parameterize and reuse behavior.
+
class MultipleOf(object):
+ def __init__(self, base):
+ self.base = base
+
+ def __call__(self, value):
+ if value % self.base != 0:
+ message = 'This field must be a multiple of %d.' % self.base
+ raise serializers.ValidationError(message)
+
In some advanced cases you might want a validator to be passed the serializer
+field it is being used with as additional context. You can do so by setting
+a requires_context = True attribute on the validator. The __call__ method
+will then be called with the serializer_field
+or serializer as an additional argument.
API versioning allows you to alter behavior between different clients. REST framework provides for a number of different versioning schemes.
+
Versioning is determined by the incoming client request, and may either be based on the request URL, or based on the request headers.
+
There are a number of valid approaches to approaching versioning. Non-versioned systems can also be appropriate, particularly if you're engineering for very long-term systems with multiple clients outside of your control.
When API versioning is enabled, the request.version attribute will contain a string that corresponds to the version requested in the incoming client request.
+
By default, versioning is not enabled, and request.version will always return None.
How you vary the API behavior is up to you, but one example you might typically want is to switch to a different serialization style in a newer version. For example:
The reverse function included by REST framework ties in with the versioning scheme. You need to make sure to include the current request as a keyword argument, like so.
+
from rest_framework.reverse import reverse
+
+reverse('bookings-list', request=request)
+
+
The above function will apply any URL transformations appropriate to the request version. For example:
+
+
If NamespaceVersioning was being used, and the API version was 'v1', then the URL lookup used would be 'v1:bookings-list', which might resolve to a URL like http://example.org/v1/bookings/.
+
If QueryParameterVersioning was being used, and the API version was 1.0, then the returned URL might be something like http://example.org/bookings/?version=1.0
Unless it is explicitly set, the value for DEFAULT_VERSIONING_CLASS will be None. In this case the request.version attribute will always return None.
+
You can also set the versioning scheme on an individual view. Typically you won't need to do this, as it makes more sense to have a single versioning scheme used globally. If you do need to do so, use the versioning_class attribute.
+
class ProfileList(APIView):
+ versioning_class = versioning.QueryParameterVersioning
+
The following settings keys are also used to control versioning:
+
+
DEFAULT_VERSION. The value that should be used for request.version when no versioning information is present. Defaults to None.
+
ALLOWED_VERSIONS. If set, this value will restrict the set of versions that may be returned by the versioning scheme, and will raise an error if the provided version is not in this set. Note that the value used for the DEFAULT_VERSION setting is always considered to be part of the ALLOWED_VERSIONS set (unless it is None). Defaults to None.
+
VERSION_PARAM. The string that should be used for any versioning parameters, such as in the media type or URL query parameters. Defaults to 'version'.
+
+
You can also set your versioning class plus those three values on a per-view or a per-viewset basis by defining your own versioning scheme and using the default_version, allowed_versions and version_param class variables. For example, if you want to use URLPathVersioning:
This scheme requires the client to specify the version as part of the media type in the Accept header. The version is included as a media type parameter, that supplements the main media type.
+
Here's an example HTTP request using the accept header versioning style.
+
GET /bookings/ HTTP/1.1
+Host: example.com
+Accept: application/json; version=1.0
+
+
In the example request above request.version attribute would return the string '1.0'.
+
Versioning based on accept headers is generally considered as best practice, although other styles may be suitable depending on your client requirements.
Strictly speaking the json media type is not specified as including additional parameters. If you are building a well-specified public API you might consider using a vendor media type. To do so, configure your renderers to use a JSON based renderer with a custom media type:
+
class BookingsAPIRenderer(JSONRenderer):
+ media_type = 'application/vnd.megacorp.bookings+json'
+
+
Your client requests would now look like this:
+
GET /bookings/ HTTP/1.1
+Host: example.com
+Accept: application/vnd.megacorp.bookings+json; version=1.0
+
This scheme requires the client to specify the version as part of the URL path.
+
GET /v1/bookings/ HTTP/1.1
+Host: example.com
+Accept: application/json
+
+
Your URL conf must include a pattern that matches the version with a 'version' keyword argument, so that this information is available to the versioning scheme.
To the client, this scheme is the same as URLPathVersioning. The only difference is how it is configured in your Django application, as it uses URL namespacing, instead of URL keyword arguments.
+
GET /v1/something/ HTTP/1.1
+Host: example.com
+Accept: application/json
+
+
With this scheme the request.version attribute is determined based on the namespace that matches the incoming request path.
+
In the following example we're giving a set of views two different possible URL prefixes, each under a different namespace:
Both URLPathVersioning and NamespaceVersioning are reasonable if you just need a simple versioning scheme. The URLPathVersioning approach might be better suitable for small ad-hoc projects, and the NamespaceVersioning is probably easier to manage for larger projects.
The hostname versioning scheme requires the client to specify the requested version as part of the hostname in the URL.
+
For example the following is an HTTP request to the http://v1.example.com/bookings/ URL:
+
GET /bookings/ HTTP/1.1
+Host: v1.example.com
+Accept: application/json
+
+
By default this implementation expects the hostname to match this simple regular expression:
+
^([a-zA-Z0-9]+)\.[a-zA-Z0-9]+\.[a-zA-Z0-9]+$
+
+
Note that the first group is enclosed in brackets, indicating that this is the matched portion of the hostname.
+
The HostNameVersioning scheme can be awkward to use in debug mode as you will typically be accessing a raw IP address such as 127.0.0.1. There are various online tutorials on how to access localhost with a custom subdomain which you may find helpful in this case.
+
Hostname based versioning can be particularly useful if you have requirements to route incoming requests to different servers based on the version, as you can configure different DNS records for different API versions.
If your versioning scheme is based on the request URL, you will also want to alter how versioned URLs are determined. In order to do so you should override the .reverse() method on the class. See the source code for examples.
REST framework provides an APIView class, which subclasses Django's View class.
+
APIView classes are different from regular View classes in the following ways:
+
+
Requests passed to the handler methods will be REST framework's Request instances, not Django's HttpRequest instances.
+
Handler methods may return REST framework's Response, instead of Django's HttpResponse. The view will manage content negotiation and setting the correct renderer on the response.
+
Any APIException exceptions will be caught and mediated into appropriate responses.
+
Incoming requests will be authenticated and appropriate permission and/or throttle checks will be run before dispatching the request to the handler method.
+
+
Using the APIView class is pretty much the same as using a regular View class, as usual, the incoming request is dispatched to an appropriate handler method such as .get() or .post(). Additionally, a number of attributes may be set on the class that control various aspects of the API policy.
+
For example:
+
from rest_framework.views import APIView
+from rest_framework.response import Response
+from rest_framework import authentication, permissions
+from django.contrib.auth.models import User
+
+class ListUsers(APIView):
+ """
+ View to list all users in the system.
+
+ * Requires token authentication.
+ * Only admin users are able to access this view.
+ """
+ authentication_classes = [authentication.TokenAuthentication]
+ permission_classes = [permissions.IsAdminUser]
+
+ def get(self, request, format=None):
+ """
+ Return a list of all users.
+ """
+ usernames = [user.username for user in User.objects.all()]
+ return Response(usernames)
+
+
+
Note: The full methods, attributes on, and relations between Django REST Framework's APIView, GenericAPIView, various Mixins, and Viewsets can be initially complex. In addition to the documentation here, the Classy Django REST Framework resource provides a browsable reference, with full methods and attributes, for each of Django REST Framework's class-based views.
The following methods are used by REST framework to instantiate the various pluggable API policies. You won't typically need to override these methods.
The following methods are called directly by the view's .dispatch() method.
+These perform any actions that need to occur before or after calling the handler methods such as .get(), .post(), put(), patch() and .delete().
Performs any actions that need to occur before the handler method gets called.
+This method is used to enforce permissions and throttling, and perform content negotiation.
Any exception thrown by the handler method will be passed to this method, which either returns a Response instance, or re-raises the exception.
+
The default implementation handles any subclass of rest_framework.exceptions.APIException, as well as Django's Http404 and PermissionDenied exceptions, and returns an appropriate error response.
+
If you need to customize the error responses your API returns you should subclass this method.
Ensures that any Response object returned from the handler method will be rendered into the correct content type, as determined by the content negotiation.
REST framework also allows you to work with regular function based views. It provides a set of simple decorators that wrap your function based views to ensure they receive an instance of Request (rather than the usual Django HttpRequest) and allows them to return a Response (instead of a Django HttpResponse), and allow you to configure how the request is processed.
The core of this functionality is the api_view decorator, which takes a list of HTTP methods that your view should respond to. For example, this is how you would write a very simple view that just manually returns some data:
This view will use the default renderers, parsers, authentication classes etc specified in the settings.
+
By default only GET methods will be accepted. Other methods will respond with "405 Method Not Allowed". To alter this behaviour, specify which methods the view allows, like so:
To override the default settings, REST framework provides a set of additional decorators which can be added to your views. These must come after (below) the @api_view decorator. For example, to create a view that uses a throttle to ensure it can only be called once per day by a particular user, use the @throttle_classes decorator, passing a list of throttle classes:
+
from rest_framework.decorators import api_view, throttle_classes
+from rest_framework.throttling import UserRateThrottle
+
+class OncePerDayUserThrottle(UserRateThrottle):
+ rate = '1/day'
+
+@api_view(['GET'])
+@throttle_classes([OncePerDayUserThrottle])
+def view(request):
+ return Response({"message": "Hello for today! See you tomorrow!"})
+
+
These decorators correspond to the attributes set on APIView subclasses, described above.
+
The available decorators are:
+
+
@renderer_classes(...)
+
@parser_classes(...)
+
@authentication_classes(...)
+
@throttle_classes(...)
+
@permission_classes(...)
+
+
Each of these decorators takes a single argument which must be a list or tuple of classes.
To override the default schema generation for function based views you may use
+the @schema decorator. This must come after (below) the @api_view
+decorator. For example:
+
from rest_framework.decorators import api_view, schema
+from rest_framework.schemas import AutoSchema
+
+class CustomAutoSchema(AutoSchema):
+ def get_link(self, path, method, base_url):
+ # override view introspection here...
+
+@api_view(['GET'])
+@schema(CustomAutoSchema())
+def view(request):
+ return Response({"message": "Hello for today! See you tomorrow!"})
+
+
This decorator takes a single AutoSchema instance, an AutoSchema subclass
+instance or ManualSchema instance as described in the Schemas documentation.
+You may pass None in order to exclude the view from schema generation.
+
@api_view(['GET'])
+@schema(None)
+def view(request):
+ return Response({"message": "Will not appear in schema!"})
+
After routing has determined which controller to use for a request, your controller is responsible for making sense of the request and producing the appropriate output.
Django REST framework allows you to combine the logic for a set of related views in a single class, called a ViewSet. In other frameworks you may also find conceptually similar implementations named something like 'Resources' or 'Controllers'.
+
A ViewSet class is simply a type of class-based View, that does not provide any method handlers such as .get() or .post(), and instead provides actions such as .list() and .create().
+
The method handlers for a ViewSet are only bound to the corresponding actions at the point of finalizing the view, using the .as_view() method.
+
Typically, rather than explicitly registering the views in a viewset in the urlconf, you'll register the viewset with a router class, that automatically determines the urlconf for you.
Rather than writing your own viewsets, you'll often want to use the existing base classes that provide a default set of behavior. For example:
+
class UserViewSet(viewsets.ModelViewSet):
+ """
+ A viewset for viewing and editing user instances.
+ """
+ serializer_class = UserSerializer
+ queryset = User.objects.all()
+
+
There are two main advantages of using a ViewSet class over using a View class.
+
+
Repeated logic can be combined into a single class. In the above example, we only need to specify the queryset once, and it'll be used across multiple views.
+
By using routers, we no longer need to deal with wiring up the URL conf ourselves.
+
+
Both of these come with a trade-off. Using regular views and URL confs is more explicit and gives you more control. ViewSets are helpful if you want to get up and running quickly, or when you have a large API and you want to enforce a consistent URL configuration throughout.
The default routers included with REST framework will provide routes for a standard set of create/retrieve/update/destroy style actions, as shown below:
+
class UserViewSet(viewsets.ViewSet):
+ """
+ Example empty viewset demonstrating the standard
+ actions that will be handled by a router class.
+
+ If you're using format suffixes, make sure to also include
+ the `format=None` keyword argument for each action.
+ """
+
+ def list(self, request):
+ pass
+
+ def create(self, request):
+ pass
+
+ def retrieve(self, request, pk=None):
+ pass
+
+ def update(self, request, pk=None):
+ pass
+
+ def partial_update(self, request, pk=None):
+ pass
+
+ def destroy(self, request, pk=None):
+ pass
+
During dispatch, the following attributes are available on the ViewSet.
+
+
basename - the base to use for the URL names that are created.
+
action - the name of the current action (e.g., list, create).
+
detail - boolean indicating if the current action is configured for a list or detail view.
+
suffix - the display suffix for the viewset type - mirrors the detail attribute.
+
name - the display name for the viewset. This argument is mutually exclusive to suffix.
+
description - the display description for the individual view of a viewset.
+
+
You may inspect these attributes to adjust behaviour based on the current action. For example, you could restrict permissions to everything except the list action similar to this:
+
def get_permissions(self):
+ """
+ Instantiates and returns the list of permissions that this view requires.
+ """
+ if self.action == 'list':
+ permission_classes = [IsAuthenticated]
+ else:
+ permission_classes = [IsAdmin]
+ return [permission() for permission in permission_classes]
+
If you have ad-hoc methods that should be routable, you can mark them as such with the @action decorator. Like regular actions, extra actions may be intended for either a single object, or an entire collection. To indicate this, set the detail argument to True or False. The router will configure its URL patterns accordingly. e.g., the DefaultRouter will configure detail actions to contain pk in their URL patterns.
Extra actions can map additional HTTP methods to separate ViewSet methods. For example, the above password set/unset methods could be consolidated into a single route. Note that additional mappings do not accept arguments.
If you need to get the URL of an action, use the .reverse_action() method. This is a convenience wrapper for reverse(), automatically passing the view's request object and prepending the url_name with the .basename attribute.
+
Note that the basename is provided by the router during ViewSet registration. If you are not using a router, then you must provide the basename argument to the .as_view() method.
The url_name argument for .reverse_action() should match the same argument to the @action decorator. Additionally, this method can be used to reverse the default actions, such as list and create.
The ViewSet class inherits from APIView. You can use any of the standard attributes such as permission_classes, authentication_classes in order to control the API policy on the viewset.
+
The ViewSet class does not provide any implementations of actions. In order to use a ViewSet class you'll override the class and define the action implementations explicitly.
The GenericViewSet class inherits from GenericAPIView, and provides the default set of get_object, get_queryset methods and other generic view base behavior, but does not include any actions by default.
+
In order to use a GenericViewSet class you'll override the class and either mixin the required mixin classes, or define the action implementations explicitly.
The ModelViewSet class inherits from GenericAPIView and includes implementations for various actions, by mixing in the behavior of the various mixin classes.
+
The actions provided by the ModelViewSet class are .list(), .retrieve(), .create(), .update(), .partial_update(), and .destroy().
Because ModelViewSet extends GenericAPIView, you'll normally need to provide at least the queryset and serializer_class attributes. For example:
+
class AccountViewSet(viewsets.ModelViewSet):
+ """
+ A simple ViewSet for viewing and editing accounts.
+ """
+ queryset = Account.objects.all()
+ serializer_class = AccountSerializer
+ permission_classes = [IsAccountAdminOrReadOnly]
+
+
Note that you can use any of the standard attributes or method overrides provided by GenericAPIView. For example, to use a ViewSet that dynamically determines the queryset it should operate on, you might do something like this:
+
class AccountViewSet(viewsets.ModelViewSet):
+ """
+ A simple ViewSet for viewing and editing the accounts
+ associated with the user.
+ """
+ serializer_class = AccountSerializer
+ permission_classes = [IsAccountAdminOrReadOnly]
+
+ def get_queryset(self):
+ return self.request.user.accounts.all()
+
+
Note however that upon removal of the queryset property from your ViewSet, any associated router will be unable to derive the basename of your Model automatically, and so you will have to specify the basename kwarg as part of your router registration.
+
Also note that although this class provides the complete set of create/list/retrieve/update/destroy actions by default, you can restrict the available operations by using the standard permission classes.
The ReadOnlyModelViewSet class also inherits from GenericAPIView. As with ModelViewSet it also includes implementations for various actions, but unlike ModelViewSet only provides the 'read-only' actions, .list() and .retrieve().
You may need to provide custom ViewSet classes that do not have the full set of ModelViewSet actions, or that customize the behavior in some other way.
To create a base viewset class that provides create, list and retrieve operations, inherit from GenericViewSet, and mixin the required actions:
+
from rest_framework import mixins
+
+class CreateListRetrieveViewSet(mixins.CreateModelMixin,
+ mixins.ListModelMixin,
+ mixins.RetrieveModelMixin,
+ viewsets.GenericViewSet):
+ """
+ A viewset that provides `retrieve`, `create`, and `list` actions.
+
+ To use it, override the class and set the `.queryset` and
+ `.serializer_class` attributes.
+ """
+ pass
+
+
By creating your own base ViewSet classes, you can provide common behavior that can be reused in multiple viewsets across your API.
The 3.0 release of Django REST framework is the result of almost four years of iteration and refinement. It comprehensively addresses some of the previous remaining design issues in serializers, fields and the generic views.
+
This release is incremental in nature. There are some breaking API changes, and upgrading will require you to read the release notes carefully, but the migration path should otherwise be relatively straightforward.
+
The difference in quality of the REST framework API and implementation should make writing, maintaining and debugging your application far easier.
+
3.0 is the first of three releases that have been funded by our recent Kickstarter campaign.
+
As ever, a huge thank you to our many wonderful sponsors. If you're looking for a Django gig, and want to work with smart community-minded folks, you should probably check out that list and see who's hiring.
Printable representations on serializers that allow you to inspect exactly what fields are present on the instance.
+
Simple model serializers that are vastly easier to understand and debug, and that make it easy to switch between the implicit ModelSerializer class and the explicit Serializer class.
+
A new BaseSerializer class, making it easier to write serializers for alternative storage backends, or to completely customize your serialization and validation logic.
+
A cleaner fields API including new classes such as ListField and MultipleChoiceField.
Support for overriding how validation errors are handled by your API.
+
A metadata API that allows you to customize how OPTIONS requests are handled by your API.
+
A more compact JSON output with unicode style encoding turned on by default.
+
Templated based HTML form rendering for serializers. This will be finalized as public API in the upcoming 3.1 release.
+
+
Significant new functionality continues to be planned for the 3.1 and 3.2 releases. These releases will correspond to the two Kickstarter stretch goals - "Feature improvements" and "Admin interface". Further 3.x releases will present simple upgrades, without the same level of fundamental API changes necessary for the 3.0 release.
The usage of request.DATA and request.FILES is now pending deprecation in favor of a single request.data attribute that contains all the parsed data.
+
Having separate attributes is reasonable for web applications that only ever parse url-encoded or multipart requests, but makes less sense for the general-purpose request parsing that REST framework supports.
+
You may now pass all the request data to a serializer class in a single argument:
+
# Do this...
+ExampleSerializer(data=request.data)
+
+
Instead of passing the files argument separately:
+
# Don't do this...
+ExampleSerializer(data=request.DATA, files=request.FILES)
+
+
The usage of request.QUERY_PARAMS is now pending deprecation in favor of the lowercased request.query_params.
Previously the serializers used a two-step object creation, as follows:
+
+
Validating the data would create an object instance. This instance would be available as serializer.object.
+
Calling serializer.save() would then save the object instance to the database.
+
+
This style is in-line with how the ModelForm class works in Django, but is problematic for a number of reasons:
+
+
Some data, such as many-to-many relationships, cannot be added to the object instance until after it has been saved. This type of data needed to be hidden in some undocumented state on the object instance, or kept as state on the serializer instance so that it could be used when .save() is called.
+
Instantiating model instances directly means that you cannot use model manager classes for instance creation, e.g. ExampleModel.objects.create(...). Manager classes are an excellent layer at which to enforce business logic and application-level data constraints.
+
The two step process makes it unclear where to put deserialization logic. For example, should extra attributes such as the current user get added to the instance during object creation or during object save?
+
+
We now use single-step object creation, like so:
+
+
Validating the data makes the cleaned data available as serializer.validated_data.
+
Calling serializer.save() then saves and returns the new object instance.
+
+
The resulting API changes are further detailed below.
The .restore_object() method is now removed, and we instead have two separate methods, .create() and .update(). These methods work slightly different to the previous .restore_object().
+
When using the .create() and .update() methods you should both create and save the object instance. This is in contrast to the previous .restore_object() behavior that would instantiate the object but not save it.
+
These methods also replace the optional .save_object() method, which no longer exists.
+
The following example from the tutorial previously used restore_object() to handle both creating and updating object instances.
You must now use the .validated_data attribute if you need to inspect the data before saving, rather than using the .object attribute, which no longer exists.
+
For example the following code is no longer valid:
+
if serializer.is_valid():
+ name = serializer.object.name # Inspect validated field data.
+ logging.info('Creating ticket "%s"' % name)
+ serializer.object.user = request.user # Include the user when saving.
+ serializer.save()
+
+
Instead of using .object to inspect a partially constructed instance, you would now use .validated_data to inspect the cleaned incoming values. Also you can't set extra attributes on the instance directly, but instead pass them to the .save() method as keyword arguments.
+
The corresponding code would now look like this:
+
if serializer.is_valid():
+ name = serializer.validated_data['name'] # Inspect validated field data.
+ logging.info('Creating ticket "%s"' % name)
+ serializer.save(user=request.user) # Include the user when saving.
+
The .is_valid() method now takes an optional boolean flag, raise_exception.
+
Calling .is_valid(raise_exception=True) will cause a ValidationError to be raised if the serializer data contains validation errors. This error will be handled by REST framework's default exception handler, allowing you to remove error response handling from your view code.
+
The handling and formatting of error responses may be altered globally by using the EXCEPTION_HANDLER settings key.
+
This change also means it's now possible to alter the style of error responses used by the built-in generic views, without having to include mixin classes or other overrides.
Previously serializers.ValidationError error was simply a synonym for django.core.exceptions.ValidationError. This has now been altered so that it inherits from the standard APIException base class.
+
The reason behind this is that Django's ValidationError class is intended for use with HTML forms and its API makes using it slightly awkward with nested validation errors that can occur in serializers.
+
For most users this change shouldn't require any updates to your codebase, but it is worth ensuring that whenever raising validation errors you should prefer using the serializers.ValidationError exception class, and not Django's built-in exception.
+
We strongly recommend that you use the namespaced import style of import serializers and not from serializers import ValidationError in order to avoid any potential confusion.
The validate_<field_name> method hooks that can be attached to serializer classes change their signature slightly and return type. Previously these would take a dictionary of all incoming data, and a key representing the field name, and would return a dictionary including the validated data for that field:
+
def validate_score(self, attrs, source):
+ if attrs['score'] % 10 != 0:
+ raise serializers.ValidationError('This field should be a multiple of ten.')
+ return attrs
+
+
This is now simplified slightly, and the method hooks simply take the value to be validated, and return the validated value.
+
def validate_score(self, value):
+ if value % 10 != 0:
+ raise serializers.ValidationError('This field should be a multiple of ten.')
+ return value
+
+
Any ad-hoc validation that applies to more than one field should go in the .validate(self, attrs) method as usual.
+
Because .validate_<field_name> would previously accept the complete dictionary of attributes, it could be used to validate a field depending on the input in another field. Now if you need to do this you should use .validate() instead.
+
You can either return non_field_errors from the validate method by raising a simple ValidationError
+
def validate(self, attrs):
+ # serializer.errors == {'non_field_errors': ['A non field error']}
+ raise serializers.ValidationError('A non field error')
+
+
Alternatively if you want the errors to be against a specific field, use a dictionary of when instantiating the ValidationError, like so:
+
def validate(self, attrs):
+ # serializer.errors == {'my_field': ['A field error']}
+ raise serializers.ValidationError({'my_field': 'A field error'})
+
+
This ensures you can still write validation that compares all the input fields, but that marks the error against a particular field.
The under-used transform_<field_name> on serializer classes is no longer provided. Instead you should just override to_representation() if you need to apply any modifications to the representation style.
+
For example:
+
def to_representation(self, instance):
+ ret = super(UserSerializer, self).to_representation(instance)
+ ret['username'] = ret['username'].lower()
+ return ret
+
+
Dropping the extra point of API means there's now only one right way to do things. This helps with repetition and reinforcement of the core API, rather than having multiple differing approaches.
+
If you absolutely need to preserve transform_<field_name> behavior, for example, in order to provide a simpler 2.x to 3.0 upgrade, you can use a mixin, or serializer base class that add the behavior back in. For example:
+
class BaseModelSerializer(ModelSerializer):
+ """
+ A custom ModelSerializer class that preserves 2.x style `transform_<field_name>` behavior.
+ """
+ def to_representation(self, instance):
+ ret = super(BaseModelSerializer, self).to_representation(instance)
+ for key, value in ret.items():
+ method = getattr(self, 'transform_' + key, None)
+ if method is not None:
+ ret[key] = method(value)
+ return ret
+
This change also means that we no longer use the .full_clean() method on model instances, but instead perform all validation explicitly on the serializer. This gives a cleaner separation, and ensures that there's no automatic validation behavior on ModelSerializer classes that can't also be easily replicated on regular Serializer classes.
+
For the most part this change should be transparent. Field validation and uniqueness checks will still be run as normal, but the implementation is a little different.
+
The one difference that you do need to note is that the .clean() method will not be called as part of serializer validation, as it would be if using a ModelForm. Use the serializer .validate() method to perform a final validation step on incoming data where required.
+
There may be some cases where you really do need to keep validation logic in the model .clean() method, and cannot instead separate it into the serializer .validate(). You can do so by explicitly instantiating a model instance in the .validate() method.
Again, you really should look at properly separating the validation logic out of the model method if possible, but the above might be useful in some backwards compatibility cases, or for an easy migration path.
REST framework 2.x attempted to automatically support writable nested serialization, but the behavior was complex and non-obvious. Attempting to automatically handle these case is problematic:
+
+
There can be complex dependencies involved in order of saving multiple related model instances.
+
It's unclear what behavior the user should expect when related models are passed None data.
+
It's unclear how the user should expect to-many relationships to handle updates, creations and deletions of multiple records.
+
+
Using the depth option on ModelSerializer will now create read-only nested serializers by default.
+
If you try to use a writable nested serializer without writing a custom create() and/or update() method you'll see an assertion error when you attempt to save the serializer. For example:
+
>>> class ProfileSerializer(serializers.ModelSerializer):
+>>> class Meta:
+>>> model = Profile
+>>> fields = ['address', 'phone']
+>>>
+>>> class UserSerializer(serializers.ModelSerializer):
+>>> profile = ProfileSerializer()
+>>> class Meta:
+>>> model = User
+>>> fields = ['username', 'email', 'profile']
+>>>
+>>> data = {
+>>> 'username': 'lizzy',
+>>> 'email': 'lizzy@example.com',
+>>> 'profile': {'address': '123 Acacia Avenue', 'phone': '01273 100200'}
+>>> }
+>>>
+>>> serializer = UserSerializer(data=data)
+>>> serializer.save()
+AssertionError: The `.create()` method does not support nested writable fields by default. Write an explicit `.create()` method for serializer `UserSerializer`, or set `read_only=True` on nested serializer fields.
+
+
To use writable nested serialization you'll want to declare a nested field on the serializer class, and write the create() and/or update() methods explicitly.
+
class UserSerializer(serializers.ModelSerializer):
+ profile = ProfileSerializer()
+
+ class Meta:
+ model = User
+ fields = ['username', 'email', 'profile']
+
+ def create(self, validated_data):
+ profile_data = validated_data.pop('profile')
+ user = User.objects.create(**validated_data)
+ Profile.objects.create(user=user, **profile_data)
+ return user
+
+
The single-step object creation makes this far simpler and more obvious than the previous .restore_object() behavior.
The view_name and lookup_field options have been moved to PendingDeprecation. They are no longer required, as you can use the extra_kwargs argument instead:
+
class MySerializer(serializer.HyperlinkedModelSerializer):
+ class Meta:
+ model = MyModel
+ fields = ['url', 'email', 'notes', 'is_admin']
+ extra_kwargs = {
+ 'url': {'lookup_field': 'uuid'}
+ }
+
+
Alternatively, specify the field explicitly on the serializer class:
+
class MySerializer(serializer.HyperlinkedModelSerializer):
+ url = serializers.HyperlinkedIdentityField(
+ view_name='mymodel-detail',
+ lookup_field='uuid'
+ )
+
+ class Meta:
+ model = MyModel
+ fields = ['url', 'email', 'notes', 'is_admin']
+
With ModelSerializer you can now specify field names in the fields option that refer to model methods or properties. For example, suppose you have the following model:
The ListSerializer class has now been added, and allows you to create base serializer classes for only accepting multiple inputs.
+
class MultipleUserSerializer(ListSerializer):
+ child = UserSerializer()
+
+
You can also still use the many=True argument to serializer classes. It's worth noting that many=True argument transparently creates a ListSerializer instance, allowing the validation logic for list and non-list data to be cleanly separated in the REST framework codebase.
+
You will typically want to continue to use the existing many=True flag rather than declaring ListSerializer classes explicitly, but declaring the classes explicitly can be useful if you need to write custom create or update methods for bulk updates, or provide for other custom behavior.
+
See also the new ListField class, which validates input in the same way, but does not include the serializer interfaces of .is_valid(), .data, .save() and so on.
REST framework now includes a simple BaseSerializer class that can be used to easily support alternative serialization and deserialization styles.
+
This class implements the same basic API as the Serializer class:
+
+
.data - Returns the outgoing primitive representation.
+
.is_valid() - Deserializes and validates incoming data.
+
.validated_data - Returns the validated incoming data.
+
.errors - Returns an errors during validation.
+
.save() - Persists the validated data into an object instance.
+
+
There are four methods that can be overridden, depending on what functionality you want the serializer class to support:
+
+
.to_representation() - Override this to support serialization, for read operations.
+
.to_internal_value() - Override this to support deserialization, for write operations.
+
.create() and .update() - Override either or both of these to support saving instances.
+
+
Because this class provides the same interface as the Serializer class, you can use it with the existing generic class-based views exactly as you would for a regular Serializer or ModelSerializer.
+
The only difference you'll notice when doing so is the BaseSerializer classes will not generate HTML forms in the browsable API. This is because the data they return does not include all the field information that would allow each field to be rendered into a suitable HTML input.
To implement a read-only serializer using the BaseSerializer class, we just need to override the .to_representation() method. Let's take a look at an example using a simple Django model:
+
class HighScore(models.Model):
+ created = models.DateTimeField(auto_now_add=True)
+ player_name = models.CharField(max_length=10)
+ score = models.IntegerField()
+
+
It's simple to create a read-only serializer for converting HighScore instances into primitive data types.
To create a read-write serializer we first need to implement a .to_internal_value() method. This method returns the validated values that will be used to construct the object instance, and may raise a ValidationError if the supplied data is in an incorrect format.
+
Once you've implemented .to_internal_value(), the basic validation API will be available on the serializer, and you will be able to use .is_valid(), .validated_data and .errors.
+
If you want to also support .save() you'll need to also implement either or both of the .create() and .update() methods.
+
Here's a complete example of our previous HighScoreSerializer, that's been updated to support both read and write operations.
+
class HighScoreSerializer(serializers.BaseSerializer):
+ def to_internal_value(self, data):
+ score = data.get('score')
+ player_name = data.get('player_name')
+
+ # Perform the data validation.
+ if not score:
+ raise ValidationError({
+ 'score': 'This field is required.'
+ })
+ if not player_name:
+ raise ValidationError({
+ 'player_name': 'This field is required.'
+ })
+ if len(player_name) > 10:
+ raise ValidationError({
+ 'player_name': 'May not be more than 10 characters.'
+ })
+
+ # Return the validated values. This will be available as
+ # the `.validated_data` property.
+ return {
+ 'score': int(score),
+ 'player_name': player_name
+ }
+
+ def to_representation(self, obj):
+ return {
+ 'score': obj.score,
+ 'player_name': obj.player_name
+ }
+
+ def create(self, validated_data):
+ return HighScore.objects.create(**validated_data)
+
The BaseSerializer class is also useful if you want to implement new generic serializer classes for dealing with particular serialization styles, or for integrating with alternative storage backends.
+
The following class is an example of a generic serializer that can handle coercing arbitrary objects into primitive representations.
+
class ObjectSerializer(serializers.BaseSerializer):
+ """
+ A read-only serializer that coerces arbitrary complex objects
+ into primitive representations.
+ """
+ def to_representation(self, obj):
+ for attribute_name in dir(obj):
+ attribute = getattr(obj, attribute_name)
+ if attribute_name.startswith('_'):
+ # Ignore private attributes.
+ pass
+ elif hasattr(attribute, '__call__'):
+ # Ignore methods and other callables.
+ pass
+ elif isinstance(attribute, (str, int, bool, float, type(None))):
+ # Primitive types can be passed through unmodified.
+ output[attribute_name] = attribute
+ elif isinstance(attribute, list):
+ # Recursively deal with items in lists.
+ output[attribute_name] = [
+ self.to_representation(item) for item in attribute
+ ]
+ elif isinstance(attribute, dict):
+ # Recursively deal with items in dictionaries.
+ output[attribute_name] = {
+ str(key): self.to_representation(value)
+ for key, value in attribute.items()
+ }
+ else:
+ # Force anything else to its string representation.
+ output[attribute_name] = str(attribute)
+
REST framework now has more explicit and clear control over validating empty values for fields.
+
Previously the meaning of the required=False keyword argument was underspecified. In practice its use meant that a field could either be not included in the input, or it could be included, but be None or the empty string.
+
We now have a better separation, with separate required, allow_null and allow_blank arguments.
+
The following set of arguments are used to control validation of empty values:
+
+
required=False: The value does not need to be present in the input, and will not be passed to .create() or .update() if it is not seen.
+
default=<value>: The value does not need to be present in the input, and a default value will be passed to .create() or .update() if it is not seen.
+
allow_null=True: None is a valid input.
+
allow_blank=True: '' is valid input. For CharField and subclasses only.
+
+
Typically you'll want to use required=False if the corresponding model field has a default value, and additionally set either allow_null=True or allow_blank=True if required.
+
The default argument is also available and always implies that the field is not required to be in the input. It is unnecessary to use the required argument when a default is specified, and doing so will result in an error.
The previous field implementations did not forcibly coerce returned values into the correct type in many cases. For example, an IntegerField would return a string output if the attribute value was a string. We now more strictly coerce to the correct return type, leading to more constrained and expected behavior.
The .validate() method is now removed from field classes. This method was in any case undocumented and not public API. You should instead simply override to_internal_value().
+
class UppercaseCharField(serializers.CharField):
+ def to_internal_value(self, data):
+ value = super(UppercaseCharField, self).to_internal_value(data)
+ if value != value.upper():
+ raise serializers.ValidationError('The input should be uppercase only.')
+ return value
+
+
Previously validation errors could be raised in either .to_native() or .validate(), making it non-obvious which should be used. Providing only a single point of API ensures more repetition and reinforcement of the core API.
The ListField class has now been added. This field validates list input. It takes a child keyword argument which is used to specify the field used to validate each item in the list. For example:
You can also use a declarative style to create new subclasses of ListField, like this:
+
class ScoresField(ListField):
+ child = IntegerField(min_value=0, max_value=100)
+
+
We can now use the ScoresField class inside another serializer:
+
scores = ScoresField()
+
+
See also the new ListSerializer class, which validates input in the same way, but also includes the serializer interfaces of .is_valid(), .data, .save() and so on.
The ChoiceField class may now accept a list of choices in addition to the existing style of using a list of pairs of (name, display_value). The following is now valid:
+
color = ChoiceField(choices=['red', 'green', 'blue'])
+
The MultipleChoiceField class has been added. This field acts like ChoiceField, but returns a set, which may include none, one or many of the valid choices.
The from_native(self, value) and to_native(self, data) method names have been replaced with the more obviously named to_internal_value(self, data) and to_representation(self, value).
+
The field_from_native() and field_to_native() methods are removed. Previously you could use these methods if you wanted to customise the behaviour in a way that did not simply lookup the field value from the object. For example...
+
def field_to_native(self, obj, field_name):
+ """A custom read-only field that returns the class name."""
+ return obj.__class__.__name__
+
+
Now if you need to access the entire object you'll instead need to override one or both of the following:
+
+
Use get_attribute to modify the attribute value passed to to_representation().
+
Use get_value to modify the data value passed to_internal_value().
+
+
For example:
+
def get_attribute(self, obj):
+ # Pass the entire object through to `to_representation()`,
+ # instead of the standard attribute lookup.
+ return obj
+
+def to_representation(self, value):
+ return value.__class__.__name__
+
Previously relational fields that were explicitly declared on a serializer class could omit the queryset argument if (and only if) they were declared on a ModelSerializer.
+
This code would be valid in 2.4.3:
+
class AccountSerializer(serializers.ModelSerializer):
+ organizations = serializers.SlugRelatedField(slug_field='name')
+
+ class Meta:
+ model = Account
+
The queryset argument is now always required for writable relational fields.
+This removes some magic and makes it easier and more obvious to move between implicit ModelSerializer classes and explicit Serializer classes.
+
class AccountSerializer(serializers.ModelSerializer):
+ organizations = serializers.SlugRelatedField(
+ slug_field='name',
+ queryset=Organization.objects.all()
+ )
+
+ class Meta:
+ model = Account
+
+
The queryset argument is only ever required for writable fields, and is not required or valid for fields with read_only=True.
The argument to SerializerMethodField is now optional, and defaults to get_<field_name>. For example the following is valid:
+
class AccountSerializer(serializers.Serializer):
+ # `method_name='get_billing_details'` by default.
+ billing_details = serializers.SerializerMethodField()
+
+ def get_billing_details(self, account):
+ return calculate_billing(account)
+
+
In order to ensure a consistent code style an assertion error will be raised if you include a redundant method name argument that matches the default method name. For example, the following code will raise an error:
I've see several codebases that unnecessarily include the source argument, setting it to the same value as the field name. This usage is redundant and confusing, making it less obvious that source is usually not required.
REST framework now provides new validators that allow you to ensure field uniqueness, while still using a completely explicit Serializer class instead of using ModelSerializer.
+
The UniqueValidator should be applied to a serializer field, and takes a single queryset argument.
+
from rest_framework import serializers
+from rest_framework.validators import UniqueValidator
+
+class OrganizationSerializer(serializers.Serializer):
+ url = serializers.HyperlinkedIdentityField(view_name='organization_detail')
+ created = serializers.DateTimeField(read_only=True)
+ name = serializers.CharField(
+ max_length=100,
+ validators=UniqueValidator(queryset=Organization.objects.all())
+ )
+
+
The UniqueTogetherValidator should be applied to a serializer, and takes a queryset argument and a fields argument which should be a list or tuple of field names.
+
class RaceResultSerializer(serializers.Serializer):
+ category = serializers.ChoiceField(['5k', '10k'])
+ position = serializers.IntegerField()
+ name = serializers.CharField(max_length=100)
+
+ class Meta:
+ validators = [UniqueTogetherValidator(
+ queryset=RaceResult.objects.all(),
+ fields=['category', 'position']
+ )]
+
REST framework also now includes explicit validator classes for validating the unique_for_date, unique_for_month, and unique_for_year model field constraints. These are used internally instead of calling into Model.full_clean().
+
These classes are documented in the Validators section of the documentation.
The pre_save and post_save hooks no longer exist, but are replaced with perform_create(self, serializer) and perform_update(self, serializer).
+
These methods should save the object instance by calling serializer.save(), adding in any additional arguments as required. They may also perform any custom pre-save or post-save behavior.
+
For example:
+
def perform_create(self, serializer):
+ # Include the owner attribute directly, rather than from request data.
+ instance = serializer.save(owner=self.request.user)
+ # Perform a custom post-save action.
+ send_email(instance.to_email, instance.message)
+
+
The pre_delete and post_delete hooks no longer exist, and are replaced with .perform_destroy(self, instance), which should delete the instance and perform any custom actions.
The .object and .object_list attributes are no longer set on the view instance. Treating views as mutable object instances that store state during the processing of the view tends to be poor design, and can lead to obscure flow logic.
+
I would personally recommend that developers treat view instances as immutable objects in their application code.
Allowing PUT as create operations is problematic, as it necessarily exposes information about the existence or non-existence of objects. It's also not obvious that transparently allowing re-creating of previously deleted instances is necessarily a better default behavior than simply returning 404 responses.
+
Both styles "PUT as 404" and "PUT as create" can be valid in different circumstances, but we've now opted for the 404 behavior as the default, due to it being simpler and more obvious.
The generic views now raise ValidationFailed exception for invalid data. This exception is then dealt with by the exception handler, rather than the view returning a 400 Bad Request response directly.
+
This change means that you can now easily customize the style of error responses across your entire API, without having to modify any of the generic views.
Behavior for dealing with OPTIONS requests was previously built directly into the class-based views. This has now been properly separated out into a Metadata API that allows the same pluggable style as other API policies in REST framework.
+
This makes it far easier to use a different style for OPTIONS responses throughout your API, and makes it possible to create third-party metadata policies.
REST framework 3.0 includes templated HTML form rendering for serializers.
+
This API should not yet be considered finalized, and will only be promoted to public API for the 3.1 release.
+
Significant changes that you do need to be aware of include:
+
+
Nested HTML forms are now supported, for example, a UserSerializer with a nested ProfileSerializer will now render a nested fieldset when used in the browsable API.
+
Nested lists of HTML forms are not yet supported, but are planned for 3.1.
+
Because we now use templated HTML form generation, the widget option is no longer available for serializer fields. You can instead control the template that is used for a given field, by using the style dictionary.
The style keyword argument can be used to pass through additional information from a serializer field, to the renderer class. In particular, the HTMLFormRenderer uses the base_template key to determine which template to render the field with.
+
For example, to use a textarea control instead of the default input control, you would use the following…
Unicode JSON is now the default. The UnicodeJSONRenderer class no longer exists, and the UNICODE_JSON setting has been added. To revert this behavior use the new setting:
The FileField and ImageField classes are now represented as URLs by default. You should ensure you set Django's standard MEDIA_URL setting appropriately, and ensure your application serves the uploaded files.
+
You can revert this behavior, and display filenames in the representation by using the UPLOADED_FILES_USE_URL settings key:
Also note that you should pass the request object to the serializer as context when instantiating it, so that a fully qualified URL can be returned. Returned URLs will then be of the form https://example.com/url_path/filename.txt. For example:
The custom X-Throttle-Wait-Second header has now been dropped in favor of the standard Retry-After header. You can revert this behavior if needed by writing a custom exception handler for your application.
Date and Time objects are now coerced to strings by default in the serializer output. Previously they were returned as Date, Time and DateTime objects, and later coerced to strings by the renderer.
+
You can modify this behavior globally by settings the existing DATE_FORMAT, DATETIME_FORMAT and TIME_FORMAT settings keys. Setting these values to None instead of their default value of 'iso-8601' will result in native objects being returned in serializer data.
Decimals are now coerced to strings by default in the serializer output. Previously they were returned as Decimal objects, and later coerced to strings by the renderer.
+
You can modify this behavior globally by using the COERCE_DECIMAL_TO_STRING settings key.
Or modify it on an individual serializer field, using the coerce_to_string keyword argument.
+
# Return `Decimal` instances in `serializer.data`, not strings.
+amount = serializers.DecimalField(
+ max_digits=10,
+ decimal_places=2,
+ coerce_to_string=False
+)
+
+
The default JSON renderer will return float objects for un-coerced Decimal instances. This allows you to easily switch between string or float representations for decimals depending on your API design needs.
The serializer ChoiceField does not currently display nested choices, as was the case in 2.4. This will be address as part of 3.1.
+
Due to the new templated form rendering, the 'widget' option is no longer valid. This means there's no easy way of using third party "autocomplete" widgets for rendering select inputs that contain a large number of choices. You'll either need to use a regular select or a plain text input. We may consider addressing this in 3.1 or 3.2 if there's sufficient demand.
+
Some of the default validation error messages were rewritten and might no longer be pre-translated. You can still create language files with Django if you wish to localize them.
+
APIException subclasses could previously take any arbitrary type in the detail argument. These exceptions now use translatable text strings, and as a result call force_text on the detail argument, which must be a string. If you need complex arguments to an APIException class, you should subclass it and override the __init__() method. Typically you'll instead want to use a custom exception handler to provide for non-standard error responses.
Note that as a result of this work a number of settings keys and generic view attributes are now moved to pending deprecation. Controlling pagination styles is now largely handled by overriding a pagination class and modifying its configuration attributes.
+
+
The PAGINATE_BY settings key will continue to work but is now pending deprecation. The more obviously named PAGE_SIZE settings key should now be used instead.
+
The PAGINATE_BY_PARAM, MAX_PAGINATE_BY settings keys will continue to work but are now pending deprecation, in favor of setting configuration attributes on the configured pagination class.
+
The paginate_by, page_query_param, paginate_by_param and max_paginate_by generic view attributes will continue to work but are now pending deprecation, in favor of setting configuration attributes on the configured pagination class.
+
The pagination_serializer_class view attribute and DEFAULT_PAGINATION_SERIALIZER_CLASS settings key are no longer valid. The pagination API does not use serializers to determine the output format, and you'll need to instead override the get_paginated_response method on a pagination class in order to specify how the output format is controlled.
Until now, there has only been a single built-in pagination style in REST framework. We now have page, limit/offset and cursor based schemes included by default.
+
The cursor based pagination scheme is particularly smart, and is a better approach for clients iterating through large or frequently changing result sets. The scheme supports paging against non-unique indexes, by using both cursor and limit/offset information. It also allows for both forward and reverse cursor pagination. Much credit goes to David Cramer for this blog post on the subject.
Paginated results now include controls that render directly in the browsable API. If you're using the page or limit/offset style, then you'll see a page based control displayed in the browsable API:
+
+
The cursor based pagination renders a more simple style of control:
The pagination API was previously only able to alter the pagination style in the body of the response. The API now supports being able to write pagination information in response headers, making it possible to use pagination schemes that use the Link or Content-Range headers.
REST framework now includes a built-in set of translations, and supports internationalized error responses. This allows you to either change the default language, or to allow clients to specify the language via the Accept-Language header.
+
You can change the default language by using the standard Django LANGUAGE_CODE setting:
+
LANGUAGE_CODE = "es-es"
+
+
You can turn on per-request language requests by adding LocalMiddleware to your MIDDLEWARE_CLASSES setting:
When per-request internationalization is enabled, client requests will respect the Accept-Language header where possible. For example, let's make a request for an unsupported media type:
+
Request
+
GET /api/users HTTP/1.1
+Accept: application/xml
+Accept-Language: es-es
+Host: example.org
+
+
Response
+
HTTP/1.0 406 NOT ACCEPTABLE
+
+{
+ "detail": "No se ha podido satisfacer la solicitud de cabecera de Accept."
+}
+
+
Note that the structure of the error responses is still the same. We still have a detail key in the response. If needed you can modify this behavior too, by using a custom exception handler.
+
We include built-in translations both for standard exception cases, and for serializer validation errors.
Django 1.8's new ArrayField, HStoreField and UUIDField are now all fully supported.
+
This work also means that we now have both serializers.DictField(), and serializers.ListField() types, allowing you to express and validate a wider set of representations.
+
If you're building a new 1.8 project, then you should probably consider using UUIDField as the primary keys for all your models. This style will work automatically with hyperlinked serializers, returning URLs in the following style:
The serializer redesign in 3.0 did not include any public API for modifying how ModelSerializer classes automatically generate a set of fields from a given mode class. We've now re-introduced an API for this, allowing you to create new ModelSerializer base classes that behave differently, such as using a different default style for relationships.
We've now moved a number of packages out of the core of REST framework, and into separately installable packages. If you're currently using these you don't need to worry, you simply need to pip install the new packages, and change any import paths.
+
We're making this change in order to help distribute the maintenance workload, and keep better focus of the core essentials of the framework.
+
The change also means we can be more flexible with which external packages we recommend. For example, the excellently maintained Django OAuth toolkit has now been promoted as our recommended option for integrating OAuth support.
+
The following packages are now moved out of core and should be separately installed:
It's worth reiterating that this change in policy shouldn't mean any work in your codebase other than adding a new requirement and modifying some import paths. For example to install XML rendering, you would now do:
The request.DATA, request.FILES and request.QUERY_PARAMS attributes move from pending deprecation, to deprecated. Use request.data and request.query_params instead, as discussed in the 3.0 release notes.
+
The ModelSerializer Meta options for write_only_fields, view_name and lookup_field are also moved from pending deprecation, to deprecated. Use extra_kwargs instead, as discussed in the 3.0 release notes.
+
All these attributes and options will still work in 3.1, but their usage will raise a warning. They will be fully removed in 3.2.
The next focus will be on HTML renderings of API output and will include:
+
+
HTML form rendering of serializers.
+
Filtering controls built-in to the browsable API.
+
An alternative admin-style interface.
+
+
This will either be made as a single 3.2 release, or split across two separate releases, with the HTML forms and filter controls coming in 3.2, and the admin-style interface coming in a 3.3 release.
If you're currently using the CoreAPI schemas, you'll need to make sure to
+update your REST framework settings to include DEFAULT_SCHEMA_CLASS explicitly.
You'll still be able to keep using CoreAPI schemas, API docs, and client for the
+foreseeable future. We'll aim to ensure that the CoreAPI schema generator remains
+available as a third party package, even once it has eventually been removed
+from REST framework, scheduled for version 3.12.
You can generate a static OpenAPI schema, using the generateschema management
+command.
+
Alternately, to have the project serve an API schema, use the get_schema_view()
+shortcut.
+
In your urls.py:
+
from rest_framework.schemas import get_schema_view
+
+urlpatterns = [
+ # ...
+ # Use the `get_schema_view()` helper to add a `SchemaView` to project URLs.
+ # * `title` and `description` parameters are passed to `SchemaGenerator`.
+ # * Provide view name for use with `reverse()`.
+ path('openapi', get_schema_view(
+ title="Your Project",
+ description="API for all things …"
+ ), name='openapi-schema'),
+ # ...
+]
+
For customizations that you want to apply across the entire API, you can subclass rest_framework.schemas.openapi.SchemaGenerator and provide it as an argument
+to the generateschema command or get_schema_view() helper function.
+
For specific per-view customizations, you can subclass AutoSchema,
+making sure to set schema = <YourCustomClass> on the view.
Given that our OpenAPI schema generation is a new feature, it's likely that there
+will still be some iterative improvements for us to make. There will be two
+main cases here:
+
+
Expanding the supported range of OpenAPI schemas that are generated by default.
+
Improving the ability for developers to customize the output.
+
+
We'll aim to bring the first type of change quickly in point releases. For the
+second kind we'd like to adopt a slower approach, to make sure we keep the API
+simple, and as widely applicable as possible, before we bring in API changes.
+
It's also possible that we'll end up implementing API documentation and API client
+tooling that are driven by the OpenAPI schema. The apistar project has a
+significant amount of work towards this. However, if we do so, we'll plan
+on keeping any tooling outside of the core framework.
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.
+
Every single sign-up helps us make REST framework long-term financially sustainable.
The OpenAPI schema generation continues to mature. Some highlights in 3.11
+include:
+
+
Automatic mapping of Django REST Framework renderers and parsers into OpenAPI
+ request and response media-types.
+
Improved mapping JSON schema mapping types, for example in HStoreFields, and
+ with large integer values.
+
Porting of the old CoreAPI parsing of docstrings to form OpenAPI operation
+ descriptions.
+
+
In this example view operation descriptions for the get and post methods will
+be extracted from the class docstring:
+
class DocStringExampleListView(APIView):
+"""
+get: A description of my GET operation.
+post: A description of my POST operation.
+"""
+ permission_classes = [permissions.IsAuthenticatedOrReadOnly]
+
+ def get(self, request, *args, **kwargs):
+ ...
+
+ def post(self, request, *args, **kwargs):
+ ...
+
In some circumstances a Validator class or a Default class may need to access the serializer field with which it is called, or the .context with which the serializer was instantiated. In particular:
+
+
Uniqueness validators need to be able to determine the name of the field to which they are applied, in order to run an appropriate database query.
+
The CurrentUserDefault needs to be able to determine the context with which the serializer was instantiated, in order to return the current user instance.
+
+
Previous our approach to this was that implementations could include a set_context method, which would be called prior to validation. However this approach had issues with potential race conditions. We have now move this approach into a pending deprecation state. It will continue to function, but will be escalated to a deprecated state in 3.12, and removed entirely in 3.13.
+
Instead, validators or defaults which require the serializer context, should include a requires_context = True attribute on the class.
+
The __call__ method should then include an additional serializer_field argument.
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.
+
Every single sign-up helps us make REST framework long-term financially sustainable.
The 3.2 release is the first version to include an admin interface for the browsable API.
+
+
This interface is intended to act as a more user-friendly interface to the API. It can be used either as a replacement to the existing BrowsableAPIRenderer, or used together with it, allowing you to switch between the two styles as required.
+
We've also fixed a huge number of issues, and made numerous cleanups and improvements.
+
Over the course of the 3.1.x series we've resolved nearly 600 tickets on our GitHub issue tracker. This means we're currently running at a rate of closing around 100 issues or pull requests per month.
+
None of this would have been possible without the support of our wonderful Kickstarter backers. If you're looking for a job in Django development we'd strongly recommend taking a look through our sponsors and finding out who's hiring.
There are some limitations to the AdminRenderer, in particular it is not yet able to handle list or dictionary inputs, as we do not have any HTML form fields that support those.
+
Also note that this is an initial release and we do not yet have a public API for modifying the behavior or documentation on overriding the templates.
+
The idea is to get this released to users early, so we can start getting feedback and release a more fully featured version in 3.3.
There are no new deprecations in 3.2, although a number of existing deprecations have now escalated in line with our deprecation policy.
+
+
request.DATA was put on the deprecation path in 3.0. It has now been removed and its usage will result in an error. Use the more pythonic style of request.data instead.
+
request.QUERY_PARAMS was put on the deprecation path in 3.0. It has now been removed and its usage will result in an error. Use the more pythonic style of request.query_params instead.
+
The following ModelSerializer.Meta options have now been removed: write_only_fields, view_name, lookup_field. Use the more general extra_kwargs option instead.
+
+
The following pagination view attributes and settings have been moved into attributes on the pagination class since 3.1. Their usage was formerly in 'pending deprecation', and has now escalated to 'deprecated'. They will continue to function but will raise errors.
+
+
view.paginate_by - Use paginator.page_size instead.
+
view.page_query_param - Use paginator.page_query_param instead.
+
view.paginate_by_param - Use paginator.page_size_query_param instead.
+
view.max_paginate_by - Use paginator.max_page_size instead.
+
settings.PAGINATE_BY - Use paginator.page_size instead.
+
settings.PAGINATE_BY_PARAM - Use paginator.page_size_query_param instead.
+
settings.MAX_PAGINATE_BY - Use paginator.max_page_size instead.
We've now added an allow_empty argument, which can be used with ListSerializer, or with many=True relationships. This is True by default, but can be set to False if you want to disallow empty lists as valid input.
+
As a follow-up to this we are now able to properly mirror the behavior of Django's ModelForm with respect to how many-to-many fields are validated.
+
Previously a many-to-many field on a model would map to a serializer field that would allow either empty or non-empty list inputs. Now, a many-to-many field will map to a serializer field that requires at least one input, unless the model field has blank=True set.
The upshot is this: If you have many to many fields in your models, then make sure you've included the argument blank=True if you want to allow empty inputs in the equivalent ModelSerializer fields.
When using allow_null with ListField or a nested many=True serializer the previous behavior was to allow null values as items in the list. The behavior is now to allow null values instead of the list.
+
For example, take the following field:
+
NestedSerializer(many=True, allow_null=True)
+
+
Previously the validation behavior would be:
+
+
[{…}, null, {…}] is valid.
+
null is invalid.
+
+
Our validation behavior as of 3.2.0 is now:
+
+
[{…}, null, {…}] is invalid.
+
null is valid.
+
+
If you want to allow null child items, you'll need to instead specify allow_null on the child class, using an explicit ListField instead of many=True. For example:
The 3.3 release marks the final work in the Kickstarter funded series. We'd like to offer a final resounding thank you to all our wonderful sponsors and supporters.
+
The amount of work that has been achieved as a direct result of the funding is immense. We've added a huge amounts of new functionality, resolved nearly 2,000 tickets, and redesigned & refined large parts of the project.
+
In order to continue driving REST framework forward, we'll shortly be announcing a new set of funding plans. Follow @_tomchristie to keep up to date with these announcements, and be among the first set of sign ups.
+
We strongly believe that collaboratively funded software development yields outstanding results for a relatively low investment-per-head. If you or your company use REST framework commercially, then we would strongly urge you to participate in this latest funding drive, and help us continue to build an increasingly polished & professional product.
The AJAX based support for the browsable API means that there are a number of internal cleanups in the request class. For the vast majority of developers this should largely remain transparent:
+
+
To support form based PUT and DELETE, or to support form content types such as JSON, you should now use the AJAX forms javascript library. This replaces the previous 'method and content type overloading' that required significant internal complexity to the request class.
+
The accept query parameter is no longer supported by the default content negotiation class. If you require it then you'll need to use a custom content negotiation class.
+
The custom HTTP_X_HTTP_METHOD_OVERRIDE header is no longer supported by default. If you require it then you'll need to use custom middleware.
+
+
The following pagination view attributes and settings have been moved into attributes on the pagination class since 3.1. Their usage was formerly deprecated, and has now been removed entirely, in line with the deprecation policy.
+
+
view.paginate_by - Use paginator.page_size instead.
+
view.page_query_param - Use paginator.page_query_param instead.
+
view.paginate_by_param - Use paginator.page_size_query_param instead.
+
view.max_paginate_by - Use paginator.max_page_size instead.
+
settings.PAGINATE_BY - Use paginator.page_size instead.
+
settings.PAGINATE_BY_PARAM - Use paginator.page_size_query_param instead.
+
settings.MAX_PAGINATE_BY - Use paginator.max_page_size instead.
+
+
The ModelSerializer and HyperlinkedModelSerializer classes should now include either a fields or exclude option, although the fields = '__all__' shortcut may be used. Failing to include either of these two options is currently pending deprecation, and will be removed entirely in the 3.5 release. This behavior brings ModelSerializer more closely in line with Django's ModelForm behavior.
The 3.4 release is the first in a planned series that will be addressing schema
+generation, hypermedia support, API clients, and finally realtime support.
The 3.4 release has been made possible a recent Mozilla grant, and by our
+collaborative funding model. If you use REST framework commercially, and would
+like to see this work continue, 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.
+Right now we're over 60% of the way towards achieving that.
+Every single sign-up makes a significant impact.
REST framework 3.4 brings built-in support for generating API schemas.
+
We provide this support by using Core API, a Document Object Model
+for describing APIs.
+
Because Core API represents the API schema in an format-independent
+manner, we're able to render the Core API Document object into many different
+schema formats, by allowing the renderer class to determine how the internal
+representation maps onto the external schema format.
+
This approach should also open the door to a range of auto-generated API
+documentation options in the future, by rendering the Document object into
+HTML documentation pages.
+
Alongside the built-in schema support, we're also now providing the following:
These API clients are dynamically driven, and able to interact with any API
+that exposes a supported schema format.
+
Dynamically driven clients allow you to interact with an API at an application
+layer interface, rather than a network layer interface, while still providing
+the benefits of RESTful Web API design.
+
We're expecting to expand the range of languages that we provide client libraries
+for over the coming months.
+
Further work on maturing the API schema support is also planned, including
+documentation on supporting file upload and download, and improved support for
+documentation generation and parameter annotation.
It is also worth noting that Marc Gibbons is currently working towards a 2.0 release of
+the popular Django REST Swagger package, which will tie in with our new built-in support.
The following change in 3.3.0 is now escalated from "pending deprecation" to
+"deprecated". Its usage will continue to function but will raise warnings:
+
ModelSerializer and HyperlinkedModelSerializer should include either a fields
+option, or an exclude option. The fields = '__all__' shortcut may be used
+to explicitly include all fields.
Using the default JSON renderer and directly returning a datetime or time
+instance will now render with microsecond precision (6 digits), rather than
+millisecond precision (3 digits). This makes the output format consistent with the
+default string output of serializers.DateTimeField and serializers.TimeField.
+
This change does not affect the default behavior when using serializers,
+which is to serialize datetime and time instances into strings with
+microsecond precision.
+
The serializer behavior can be modified if needed, using the DATETIME_FORMAT
+and TIME_FORMAT settings.
+
The renderer behavior can be modified by setting a custom encoder_class
+attribute on a JSONRenderer subclass.
Making an OPTIONS request to views that have a serializer choice field
+will result in a list of the available choices being returned in the response.
+
In cases where there is a relational field, the previous behavior would be
+to return a list of available instances to choose from for that relational field.
+
In order to minimise exposed information the behavior now is to not return
+choices information for relational fields.
Many thanks to all our contributors who've been involved in the release, either through raising issues, giving feedback, improving the documentation, or suggesting and implementing code changes.
The 3.5 release is the second in a planned series that is addressing schema
+generation, hypermedia support, API client libraries, and finally realtime support.
The 3.5 release would not have been possible without our collaborative funding model.
+If you use REST framework commercially and would like to see this work continue,
+we strongly encourage you to invest in its continued development by
+signing up for a paid plan.
There have been a large number of fixes to the schema generation. These should
+resolve issues for anyone using the latest version of the django-rest-swagger
+package.
+
Some of these changes do affect the resulting schema structure,
+so if you're already using schema generation you should make sure to review
+the deprecation notes, particularly if you're currently using
+a dynamic client library to interact with your API.
+
Finally, we're also now exposing the schema generation as a
+publicly documented API, allowing you to more easily
+override the behaviour.
Rather than sending any HTTP requests to the network, this interface will
+coerce all outgoing requests into WSGI, and call into your application directly.
You can also now test your project by interacting with it using the coreapi
+client library.
+
# Fetch the API schema
+client = CoreAPIClient()
+schema = client.get('http://testserver/schema/')
+
+# Create a new organisation
+params = {'name': 'MegaCorp', 'status': 'active'}
+client.action(schema, ['organisations', 'create'], params)
+
+# Ensure that the organisation exists in the listing
+data = client.action(schema, ['organisations', 'list'])
+assert(len(data) == 1)
+assert(data == [{'name': 'MegaCorp', 'status': 'active'}])
+
+
Again, this will call directly into the application using the WSGI interface,
+rather than making actual network calls.
+
This is a good option if you are planning for clients to mainly interact with
+your API using the coreapi client library, or some other auto-generated client.
One interesting aspect of both the requests client and the coreapi client
+is that they allow you to write tests in such a way that they can also be made
+to run against a live service.
+
By switching the WSGI based client instances to actual instances of requests.Session
+or coreapi.Client you can have the test cases make actual network calls.
+
Being able to write test cases that can exercise your staging or production
+environment is a powerful tool. However in order to do this, you'll need to pay
+close attention to how you handle setup and teardown to ensure a strict isolation
+of test data from other live or staging data.
Further work on the encoding and documentation generation is planned, in order to
+make features such as the 'Try it now' support available at a later date.
+
This work also now means that you can use the Core API client libraries to interact
+with APIs that expose a RAML specification. The RAML codec gives some examples of
+interacting with the Spotify API in this way.
Exceptions raised by REST framework now include short code identifiers.
+When used together with our customizable error handling, this now allows you to
+modify the style of API error messages.
+
As an example, this allows for the following style of error responses:
+
{
+ "message": "You do not have permission to perform this action.",
+ "code": "permission_denied"
+}
+
+
This is particularly useful with validation errors, which use appropriate
+codes to identify differing kinds of failure...
+
{
+ "name": {"message": "This field is required.", "code": "required"},
+ "age": {"message": "A valid integer is required.", "code": "invalid"}
+}
+
The 'pk' identifier in schema paths is now mapped onto the actually model field
+name by default. This will typically be 'id'.
+
This gives a better external representation for schemas, with less implementation
+detail being exposed. It also reflects the behaviour of using a ModelSerializer
+class with fields = '__all__'.
+
You can revert to the previous behaviour by setting 'SCHEMA_COERCE_PATH_PK': False
+in the REST framework settings.
The media type for CoreJSON is now application/json+coreapi, rather than
+the previous application/vnd.json+coreapi. This brings it more into line with
+other custom media types, such as those used by Swagger and RAML.
+
The clients currently accept either media type. The old style-media type will
+be deprecated at a later date.
ModelSerializer and HyperlinkedModelSerializer must include either a fields
+option, or an exclude option. The fields = '__all__' shortcut may be used to
+explicitly include all fields.
+
Failing to set either fields or exclude raised a pending deprecation warning
+in version 3.3 and raised a deprecation warning in 3.4. Its usage is now mandatory.
If you use REST framework commercially and would like to see this work continue,
+we strongly encourage you to invest in its continued development by
+signing up for a paid plan.
REST framework's new API documentation supports a number of features:
+
+
Live API interaction.
+
Support for various authentication schemes.
+
Code snippets for the Python, JavaScript, and Command Line clients.
+
+
The coreapi library is required as a dependency for the API docs. Make sure
+to install the latest version (2.3.0 or above). The pygments and markdown
+libraries are optional but recommended.
+
To install the API documentation, you'll need to include it in your projects URLconf:
Once installed you should see something a little like this:
+
+
We'll likely be making further refinements to the API documentation over the
+coming weeks. Keep in mind that this is a new feature, and please do give
+us feedback if you run into any issues or limitations.
+
For more information on documenting your API endpoints see the "Documenting your API" section.
The JavaScript client library allows you to load an API schema, and then interact
+with that API at an application layer interface, rather than constructing fetch
+requests explicitly.
The JavaScript client library supports various authentication schemes, and can be
+used by your project itself, or as an external client interacting with your API.
+
The client is not limited to usage with REST framework APIs, although it does
+currently only support loading CoreJSON API schemas. Support for Swagger and
+other API schemas is planned.
Previous authentication support in the Python client library was limited to
+allowing users to provide explicit header values.
+
We now have better support for handling the details of authentication, with
+the introduction of the BasicAuthentication, TokenAuthentication, and
+SessionAuthentication schemes.
+
You can include the authentication scheme when instantiating a new client.
The 3.5 "pending deprecation" of router arguments for generating a schema view, such as schema_title, schema_url and schema_renderers, have now been escalated to a
+"deprecated" warning.
+
Instead of using DefaultRouter(schema_title='Example API'), you should use the get_schema_view() function, and include the view explicitly in your URL conf.
There are likely to be a number of refinements to the API documentation and
+JavaScript client library over the coming weeks, which could include some of the following:
+
+
Support for private API docs, requiring login.
+
File upload and download support in the JavaScript client & API docs.
+
Comprehensive documentation for the JavaScript client library.
+
Automatically including authentication details in the API doc code snippets.
+
Adding authentication support in the command line client.
+
Support for loading Swagger and other schemas in the JavaScript client.
+
Improved support for documenting parameter schemas and response schemas.
+
Refining the API documentation interaction modal.
+
+
Once work on those refinements is complete, we'll be starting feature work
+on realtime support, for the 3.7 release.
If you use REST framework commercially and would like to see this work continue, we strongly encourage you to invest in its continued development by
+signing up for a paid plan.
The schema generation introduced in 3.5 and the related API docs generation in 3.6 are both hugely powerful features, however they've been somewhat limited in cases where the view introspection isn't able to correctly identify the schema for a particular view.
+
In order to try to address this we're now adding the ability for per-view customization of the API schema. The interface that we're adding for this allows either basic manual overrides over which fields should be included on a view, or for more complex programmatic overriding of the schema generation. We believe this release comprehensively addresses some of the existing shortcomings of the schema features.
+
Let's take a quick look at using the new functionality...
+
The APIView class has a schema attribute, that is used to control how the Schema for that particular view is generated. The default behaviour is to use the AutoSchema class.
+
from rest_framework.views import APIView
+from rest_framework.schemas import AutoSchema
+
+class CustomView(APIView):
+ schema = AutoSchema() # Included for demonstration only. This is the default behavior.
+
+
We can remove a view from the API schema and docs, like so:
+
class CustomView(APIView):
+ schema = None
+
+
If we want to mostly use the default behavior, but additionally include some additional fields on a particular view, we can now do so easily...
There are a large number of minor fixes and improvements in this release. See the release notes page for a complete listing.
+
The number of open tickets against the project currently at its lowest number in quite some time, and we're continuing to focus on reducing these to a manageable amount.
Both APIView.exclude_from_schema and the exclude_from_schema argument to the @api_view decorator and now PendingDeprecation. They will be moved to deprecated in the 3.8 release, and removed entirely in 3.9.
+
For APIView you should instead set a schema = None attribute on the view class.
+
For function based views the @schema decorator can be used to exclude the view from the schema, by using @schema(None).
We're still planning to work on improving real-time support for REST framework by providing documentation on integrating with Django channels, as well adding support for more easily adding WebSocket support to existing HTTP endpoints.
+
This will likely be timed so that any REST framework development here ties in with similar work on API Star.
The 3.8 release is a maintenance focused release resolving a large number of previously outstanding issues and laying
+the foundations for future changes.
If you use REST framework commercially and would like to see this work continue, we strongly encourage you to invest in its continued development by
+signing up for a paid plan.
#5886read_only fields will now always be excluded from writable fields.
+
Previously read_only fields when combined with a default value would use the default for create and update
+operations. This was counter-intuitive in some circumstances and led to difficulties supporting dotted source
+attributes on nullable relations.
+
In order to maintain the old behaviour you may need to pass the value of read_only fields when calling save() in
+the view:
#5705list_route and detail_route have been merge into a single action decorator. This improves viewset action introspection, and will allow extra actions to be displayed in the Browsable API in future versions.
+
Both list_route and detail_route are now pending deprecation. They will be deprecated in 3.9 and removed entirely
+in 3.10.
+
The new action decorator takes a boolean detail argument.
+
+
Replace detail_route uses with @action(detail=True).
+
Replace list_route uses with @action(detail=False).
Both APIView.exclude_from_schema and the exclude_from_schema argument to the @api_view decorator are now deprecated. They will be removed entirely in 3.9.
+
For APIView you should instead set a schema = None attribute on the view class.
+
For function based views the @schema decorator can be used to exclude the view from the schema, by using @schema(None).
We're currently working towards moving to using OpenAPI as our default schema output. We'll also be revisiting our API documentation generation and client libraries.
+
We're doing some consolidation in order to make this happen. It's planned that 3.9 will drop the coreapi and coreschema libraries, and instead use apistar for the API documentation generation, schema generation, and API client libraries.
The 3.9 release gives access to extra actions in the Browsable API, introduces composable permissions and built-in OpenAPI schema support. (Formerly known as Swagger)
If you use REST framework commercially and would like to see this work continue, we strongly encourage you to invest in its continued development by
+signing up for a paid plan.
There's lots of different tooling that you can use for working with OpenAPI
+schemas. One option that we're working on is the API Star
+command line tool.
We're planning to iteratively work towards OpenAPI becoming the standard schema
+representation. This will mean that the coreapi dependency will gradually become
+removed, and we'll instead generate the schema directly, rather than building
+a CoreAPI Document object.
+
OpenAPI has clearly become the standard for specifying Web APIs, so there's not
+much value any more in our schema-agnostic document model. Making this change
+will mean that we'll more easily be able to take advantage of the full set of
+OpenAPI functionality.
+
This will also make a wider range of tooling available.
+
We'll focus on continuing to develop the API Star
+library and client tool into a recommended option for generating API docs,
+validating API schemas, and providing a dynamic client library.
+
There's also a huge amount of ongoing work on maturing the ASGI landscape,
+with the possibility that some of this work will eventually feed back into
+Django.
+
There will be further work on the Uvicorn
+web server, as well as lots of functionality planned for the Starlette
+web framework, which is building a foundational set of tooling for working with
+ASGI.
There are many ways you can contribute to Django REST framework. We'd like it to be a community-led project, so please get involved and help shape the future of the project.
The most important thing you can do to help push the REST framework project forward is to be actively involved wherever possible. Code contributions are often overvalued as being the primary way to get involved in a project, we don't believe that needs to be the case.
+
If you use REST framework, we'd love you to be vocal about your experiences with it - you might consider writing a blog post about using REST framework, or publishing a tutorial about building a project with a particular JavaScript framework. Experiences from beginners can be particularly helpful because you'll be in the best position to assess which bits of REST framework are more difficult to understand and work with.
+
Other really great ways you can help move the community forward include helping to answer questions on the discussion group, or setting up an email alert on StackOverflow so that you get notified of any new questions with the django-rest-framework tag.
+
When answering questions make sure to help future contributors find their way around by hyperlinking wherever possible to related threads and tickets, and include backlinks from those items if relevant.
Please keep the tone polite & professional. For some users a discussion on the REST framework mailing list or ticket tracker may be their first engagement with the open source community. First impressions count, so let's try to make everyone feel welcome.
+
Be mindful in the language you choose. As an example, in an environment that is heavily male-dominated, posts that start 'Hey guys,' can come across as unintentionally exclusive. It's just as easy, and more inclusive to use gender neutral language in those situations.
+
The Django code of conduct gives a fuller set of guidelines for participating in community forums.
It's really helpful if you can make sure to address issues on the correct channel. Usage questions should be directed to the discussion group. Feature requests, bug reports and other issues should be raised on the GitHub issue tracker.
+
Some tips on good issue reporting:
+
+
When describing issues try to phrase your ticket in terms of the behavior you think needs changing rather than the code you think need changing.
+
Search the issue list first for related items, and make sure you're running the latest version of REST framework before reporting an issue.
+
If reporting a bug, then try to include a pull request with a failing test case. This will help us quickly identify if there is a valid issue, and make sure that it gets fixed more quickly if there is one.
+
Feature requests will often be closed with a recommendation that they be implemented outside of the core REST framework library. Keeping new feature requests implemented as third party libraries allows us to keep down the maintenance overhead of REST framework, so that the focus can be on continued stability, bugfixes, and great documentation.
+
Closing an issue doesn't necessarily mean the end of a discussion. If you believe your issue has been closed incorrectly, explain why and we'll consider if it needs to be reopened.
Getting involved in triaging incoming issues is a good way to start contributing. Every single ticket that comes into the ticket tracker needs to be reviewed in order to determine what the next steps should be. Anyone can help out with this, you just need to be willing to
+
+
Read through the ticket - does it make sense, is it missing any context that would help explain it better?
+
Is the ticket reported in the correct place, would it be better suited as a discussion on the discussion group?
+
If the ticket is a bug report, can you reproduce it? Are you able to write a failing test case that demonstrates the issue and that can be submitted as a pull request?
+
If the ticket is a feature request, do you agree with it, and could the feature request instead be implemented as a third party package?
+
If a ticket hasn't had much activity and it addresses something you need, then comment on the ticket and try to find out what's needed to get it moving again.
Run the tests using a more concise output style, no coverage, no flake8.
+
./runtests.py --fast
+
+
Don't run the flake8 code linting.
+
./runtests.py --nolint
+
+
Only run the flake8 code linting, don't run the tests.
+
./runtests.py --lintonly
+
+
Run the tests for a given test case.
+
./runtests.py MyTestCase
+
+
Run the tests for a given test method.
+
./runtests.py MyTestCase.test_this_method
+
+
Shorter form to run the tests for a given test method.
+
./runtests.py test_this_method
+
+
Note: The test case and test method matching is fuzzy and will sometimes run other tests that contain a partial string match to the given command line input.
You can also use the excellent tox testing tool to run the tests against all supported versions of Python and Django. Install tox globally, and then simply run:
It's a good idea to make pull requests early on. A pull request represents the start of a discussion, and doesn't necessarily need to be the final, finished submission.
+
It's also always best to make a new branch before starting work on a pull request. This means that you'll be able to later switch back to working on another separate issue without interfering with an ongoing pull requests.
+
It's also useful to remember that if you have an outstanding pull request then pushing new commits to your GitHub repo will also automatically update the pull requests.
+
GitHub's documentation for working on pull requests is available here.
+
Always run the tests before submitting pull requests, and ideally run tox in order to check that your modifications are compatible on all supported versions of Python and Django.
+
Once you've made a pull request take a look at the Travis build status in the GitHub interface and make sure the tests are running as you'd expect.
Sometimes, in order to ensure your code works on various different versions of Django, Python or third party libraries, you'll need to run slightly different code depending on the environment. Any code that branches in this way should be isolated into the compat.py module, and should provide a single common interface that the rest of the codebase can use.
There are many great Markdown editors that make working with the documentation really easy. The Mou editor for Mac is one such editor that comes highly recommended.
Documentation should be in American English. The tone of the documentation is very important - try to stick to a simple, plain, objective and well-balanced style where possible.
+
Some other tips:
+
+
Keep paragraphs reasonably short.
+
Don't use abbreviations such as 'e.g.' but instead use the long form, such as 'For example'.
Linking in this style means you'll be able to click the hyperlink in your Markdown editor to open the referenced document. When the documentation is built, these links will be converted into regular links to HTML pages.
If you use REST framework commercially we strongly encourage you to invest in its continued development by signing up for a paid plan.
+
We believe that collaboratively funded software can offer outstanding returns on investment, by encouraging our users to collectively share the cost of development.
+
Signing up for a paid plan will:
+
+
Directly contribute to faster releases, more features, and higher quality software.
+
Allow more time to be invested in documentation, issue triage, and community support.
+
Safeguard the future development of REST framework.
+
+
REST framework continues to be open-source and permissively licensed, but we firmly believe it is in the commercial best-interest for users of the project to invest in its ongoing development.
The 3.4 and 3.5 releases, including schema generation for both Swagger and RAML, a Python client library, a Command Line client, and addressing of a large number of outstanding issues.
+
The 3.6 release, including JavaScript client library, and API documentation, complete with auto-generated code samples.
+
The 3.7 release, made possible due to our collaborative funding model, focuses on improvements to schema generation and the interactive API documentation.
Realtime API support, using WebSockets. This will consist of documentation and support for using REST framework together with Django Channels, plus integrating WebSocket support into the client libraries.
+
Better authentication defaults, possibly bringing JWT & CORs support into the core package.
+
Securing the community & operations manager position long-term.
+
Opening up and securing a part-time position to focus on ticket triage and resolution.
+
Paying for development time on building API client libraries in a range of programming languages. These would be integrated directly into the upcoming API documentation.
+
+
Sign up for a paid plan today, and help ensure that REST framework becomes a sustainable, full-time funded project.
As a developer, Django REST framework feels like an obvious and natural extension to all the great things that make up Django and it's community. Getting started is easy while providing simple abstractions which makes it flexible and customizable. Contributing and supporting Django REST framework helps ensure its future and one way or another it also helps Django, and the Python ecosystem.
+
— José Padilla, Django REST framework contributor
+
+
+
+
The number one feature of the Python programming language is its community. Such a community is only possible because of the Open Source nature of the language and all the culture that comes from it. Building great Open Source projects require great minds. Given that, we at Vinta are not only proud to sponsor the team behind DRF but we also recognize the ROI that comes from it.
+
— Filipe Ximenes, Vinta Software
+
+
+
+
It's really awesome that this project continues to endure. The code base is top notch and the maintainers are committed to the highest level of quality.
+DRF is one of the core reasons why Django is top choice among web frameworks today. In my opinion, it sets the standard for rest frameworks for the development community at large.
These subscriptions are recommended for companies and organizations using REST framework either publicly or privately.
+
In exchange for funding you'll also receive advertising space on our site, allowing you to promote your company or product to many tens of thousands of developers worldwide.
+
Our professional and premium plans also include priority support. At any time your engineers can escalate an issue or discussion group thread, and we'll ensure it gets a guaranteed response within the next working day.
+
+
+
+
+ {{ symbol }}
+ {{ rates.corporate1 }}
+ /month{% if vat %} +VAT{% endif %}
+
+
Basic
+
+
+ Support ongoing development
+
+
+ Funding page ad placement
+
+
+
+
+
+
+
+
+ {{ symbol }}
+ {{ rates.corporate2 }}
+ /month{% if vat %} +VAT{% endif %}
+
+
Professional
+
+
+ Support ongoing development
+
+
+ Sidebar ad placement
+
+
+ Priority support for your engineers
+
+
+
+
+
+
+
+
+ {{ symbol }}
+ {{ rates.corporate3 }}
+ /month{% if vat %} +VAT{% endif %}
+
+
Premium
+
+
+ Support ongoing development
+
+
+ Homepage ad placement
+
+
+ Sidebar ad placement
+
+
+ Priority support for your engineers
+
+
+
+
+
+
+
+
+
+
Billing is monthly and you can cancel at any time.
+
Once you've signed up, we will contact you via email and arrange your ad placements on the site.
In an effort to keep the project as transparent as possible, we are releasing monthly progress reports and regularly include financial reports and cost breakdowns.
Q: Can you issue monthly invoices?
+A: Yes, we are happy to issue monthly invoices. Please just email us and let us know who to issue the invoice to (name and address) and which email address to send it to each month.
+
Q: Does sponsorship include VAT?
+A: Sponsorship is VAT exempt.
+
Q: Do I have to sign up for a certain time period?
+A: No, we appreciate your support for any time period that is convenient for you. Also, you can cancel your sponsorship anytime.
+
Q: Can I pay yearly? Can I pay upfront fox X amount of months at a time?
+A: We are currently only set up to accept monthly payments. However, if you'd like to support Django REST framework and you can only do yearly/upfront payments, we are happy to work with you and figure out a convenient solution.
+
Q: Are you only looking for corporate sponsors?
+A: No, we value individual sponsors just as much as corporate sponsors and appreciate any kind of support.
Looking for a new Django REST Framework related role? On this site we provide a list of job resources that may be helpful. It's also worth checking out if any of our sponsors are hiring.
Know of any other great resources for Django REST Framework jobs that are missing in our list? Please submit a pull request or email us.
+
Wonder how else you can help? One of the best ways you can help Django REST Framework is to ask interviewers if their company is signed up for REST Framework sponsorship yet.
In order to continue to drive the project forward, I'm launching a Kickstarter campaign to help fund the development of a major new release - Django REST framework 3.
We've now blazed way past all our goals, with a staggering £30,000 (~$50,000), meaning I'll be in a position to work on the project significantly beyond what we'd originally planned for. I owe a huge debt of gratitude to all the wonderful companies and individuals who have been backing the project so generously, and making this possible.
Our platinum sponsors have each made a hugely substantial contribution to the future development of Django REST framework, and I simply can't thank them enough.
Our gold sponsors include companies large and small. Many thanks for their significant funding of the project and their commitment to sustainable open-source development.
The serious financial contribution that our silver sponsors have made is very much appreciated. I'd like to say a particular thank you to individuals who have chosen to privately support the project at this level.
The following individuals made a significant financial contribution to the development of Django REST framework 3, for which I can only offer a huge, warm and sincere thank you!
+
Individual backers: Jure Cuhalev, Kevin Brolly, Ferenc Szalai, Dougal Matthews, Stefan Foulis, Carlos Hernando, Alen Mujezinovic, Ross Crawford-d'Heureuse, George Kappel, Alasdair Nicol, John Carr, Steve Winton, Trey, Manuel Miranda, David Horn, Vince Mi, Daniel Sears, Jamie Matthews, Ryan Currah, Marty Kemka, Scott Nixon, Moshin Elahi, Kevin Campbell, Jose Antonio Leiva Izquierdo, Kevin Stone, Andrew Godwin, Tijs Teulings, Roger Boardman, Xavier Antoviaque, Darian Moody, Lujeni, Jon Dugan, Wiley Kestner, Daniel C. Silverstein, Daniel Hahler, Subodh Nijsure, Philipp Weidenhiller, Yusuke Muraoka, Danny Roa, Reto Aebersold, Kyle Getrost, Décébal Hormuz, James Dacosta, Matt Long, Mauro Rocco, Tyrel Souza, Ryan Campbell, Ville Jyrkkä, Charalampos Papaloizou, Nikolai Røed Kristiansen, Antoni Aloy López, Celia Oakley, Michał Krawczak, Ivan VenOsdel, Tim Watts, Martin Warne, Nicola Jordan, Ryan Kaskel.
There were also almost 300 further individuals choosing to help fund the project at other levels or choosing to give anonymously. Again, thank you, thank you, thank you!
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/community/mozilla-grant/index.html b/community/mozilla-grant/index.html
new file mode 100644
index 000000000..0ae0ec1c9
--- /dev/null
+++ b/community/mozilla-grant/index.html
@@ -0,0 +1,548 @@
+
+
+
+
+
+
+ Mozilla Grant - Django REST framework
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
We have recently been awarded a Mozilla grant, in order to fund the next major releases of REST framework. This work will focus on seamless client-side integration by introducing supporting client libraries that are able to dynamically interact with REST framework APIs. The framework will provide for either hypermedia or schema endpoints, which will expose the available interface for the client libraries to interact with.
+
Additionally, we will be building on the realtime support that Django Channels provides, supporting and documenting how to build realtime APIs with REST framework. Again, this will include supporting work in the associated client libraries, making it easier to build richly interactive applications.
+
The Core API project will provide the foundations for our client library support, and will allow us to support interaction using a wide range of schemas and hypermedia formats. It's worth noting that these client libraries won't be tightly coupled to solely REST framework APIs either, and will be able to interact with any API that exposes a supported schema or hypermedia format.
This work will include built-in schema and hypermedia support, allowing dynamic client libraries to interact with the API. I'll also be releasing both Python and Javascript client libraries, plus a command-line client, a new tutorial section, and further documentation.
+
+
Client library support in REST framework.
+
Schema & hypermedia support for REST framework APIs.
+
A test client, allowing you to write tests that emulate a client library interacting with your API.
+
New tutorial sections on using client libraries to interact with REST framework APIs.
In order to ensure that I can be fully focused on trying to secure a sustainable
+& well-funded open source business I will be leaving my current role at DabApps
+at the end of May 2016.
+
I have formed a UK limited company, Encode, which will
+act as the business entity behind REST framework. I will be issuing monthly reports
+from Encode on progress both towards the Mozilla grant, and for development time
+funded via the REST framework paid plans.
"No one can whistle a symphony; it takes a whole orchestra to play it"
+
— Halford E. Luccock
+
+
This document outlines our project management processes for REST framework.
+
The aim is to ensure that the project has a high
+"bus factor", and can continue to remain well supported for the foreseeable future. Suggestions for improvements to our process are welcome.
We have a quarterly maintenance cycle where new members may join the maintenance team. We currently cap the size of the team at 5 members, and may encourage folks to step out of the team for a cycle to allow new members to participate.
Each maintenance cycle is initiated by an issue being opened with the Process label.
+
+
To be considered for a maintainer role simply comment against the issue.
+
Existing members must explicitly opt-in to the next cycle by check-marking their name.
+
The final decision on the incoming team will be made by @tomchristie.
+
+
Members of the maintenance team will be added as collaborators to the repository.
+
The following template should be used for the description of the issue, and serves as the formal process for selecting the team.
+
This issue is for determining the maintenance team for the *** period.
+
+Please see the [Project management](https://www.django-rest-framework.org/topics/project-management/) section of our documentation for more details.
+
+---
+
+#### Renewing existing members.
+
+The following people are the current maintenance team. Please checkmark your name if you wish to continue to have write permission on the repository for the *** period.
+
+- [ ] @***
+- [ ] @***
+- [ ] @***
+- [ ] @***
+- [ ] @***
+
+---
+
+#### New members.
+
+If you wish to be considered for this or a future date, please comment against this or subsequent issues.
+
+To modify this process for future maintenance cycles make a pull request to the [project management](https://www.django-rest-framework.org/topics/project-management/) documentation.
+
It should be noted that participating actively in the REST framework project clearly does not require being part of the maintenance team. Almost every import part of issue triage and project improvement can be actively worked on regardless of your collaborator status on the repository.
The release manager is selected on every quarterly maintenance cycle.
+
+
The manager should be selected by @tomchristie.
+
The manager will then have the maintainer role added to PyPI package.
+
The previous manager will then have the maintainer role removed from the PyPI package.
+
+
Our PyPI releases will be handled by either the current release manager, or by @tomchristie. Every release should have an open issue tagged with the Release label and marked against the appropriate milestone.
+
The following template should be used for the description of the issue, and serves as a release checklist.
+
Release manager is @***.
+Pull request is #***.
+
+During development cycle:
+
+- [ ] Upload the new content to be translated to [transifex](https://www.django-rest-framework.org/topics/project-management/#translations).
+
+
+Checklist:
+
+- [ ] Create pull request for [release notes](https://github.com/encode/django-rest-framework/blob/master/docs/topics/release-notes.md) based on the [*.*.* milestone](https://github.com/encode/django-rest-framework/milestones/***).
+- [ ] Update supported versions:
+ - [ ] `setup.py` `python_requires` list
+ - [ ] `setup.py` Python & Django version trove classifiers
+ - [ ] `README` Python & Django versions
+ - [ ] `docs` Python & Django versions
+- [ ] Update the translations from [transifex](https://www.django-rest-framework.org/topics/project-management/#translations).
+- [ ] Ensure the pull request increments the version to `*.*.*` in [`restframework/__init__.py`](https://github.com/encode/django-rest-framework/blob/master/rest_framework/__init__.py).
+- [ ] Confirm with @tomchristie that release is finalized and ready to go.
+- [ ] Ensure that release date is included in pull request.
+- [ ] Merge the release pull request.
+- [ ] Push the package to PyPI with `./setup.py publish`.
+- [ ] Tag the release, with `git tag -a *.*.* -m 'version *.*.*'; git push --tags`.
+- [ ] Deploy the documentation with `mkdocs gh-deploy`.
+- [ ] Make a release announcement on the [discussion group](https://groups.google.com/forum/?fromgroups#!forum/django-rest-framework).
+- [ ] Make a release announcement on twitter.
+- [ ] Close the milestone on GitHub.
+
+To modify this process for future releases make a pull request to the [project management](https://www.django-rest-framework.org/topics/project-management/) documentation.
+
+
When pushing the release to PyPI ensure that your environment has been installed from our development requirement.txt, so that documentation and PyPI installs are consistently being built against a pinned set of packages.
The maintenance team are responsible for managing the translation packs include in REST framework. Translating the source strings into multiple languages is managed through the transifex service.
The official Transifex client is used to upload and download translations to Transifex. The client is installed using pip:
+
pip install transifex-client
+
+
To use it you'll need a login to Transifex which has a password, and you'll need to have administrative access to the Transifex project. You'll need to create a ~/.transifexrc file which contains your credentials.
When any user visible strings are changed, they should be uploaded to Transifex so that the translators can start to translate them. To do this, just run:
+
# 1. Update the source django.po file, which is the US English version.
+cd rest_framework
+django-admin makemessages -l en_US
+# 2. Push the source django.po file to Transifex.
+cd ..
+tx push -s
+
+
When pushing source files, Transifex will update the source strings of a resource to match those from the new source file.
+
Here's how differences between the old and new source files will be handled:
+
+
New strings will be added.
+
Modified strings will be added as well.
+
Strings which do not exist in the new source file will be removed from the database, along with their translations. If that source strings gets re-added later then Transifex Translation Memory will automatically include the translation string.
When a translator has finished translating their work needs to be downloaded from Transifex into the REST framework repository. To do this, run:
+
# 3. Pull the translated django.po files from Transifex.
+tx pull -a --minimum-perc 10
+cd rest_framework
+# 4. Compile the binary .mo files for all supported languages.
+django-admin compilemessages
+
All our test requirements are pinned to exact versions, in order to ensure that our test runs are reproducible. We maintain the requirements in the requirements directory. The requirements files are referenced from the tox.ini configuration file, ensuring we have a single source of truth for package versions used in testing.
+
Package upgrades should generally be treated as isolated pull requests. You can check if there are any packages available at a newer version, by using the pip list --outdated.
Minor version numbers (0.0.x) are used for changes that are API compatible. You should be able to upgrade between minor point releases without any other code changes.
+
Medium version numbers (0.x.0) may include API changes, in line with the deprecation policy. You should read the release notes carefully before upgrading between medium point releases.
+
Major version numbers (x.0.0) are reserved for substantial project milestones.
REST framework releases follow a formal deprecation policy, which is in line with Django's deprecation policy.
+
The timeline for deprecation of a feature present in version 1.0 would work as follows:
+
+
+
Version 1.1 would remain fully backwards compatible with 1.0, but would raise RemovedInDRF13Warning warnings, subclassing PendingDeprecationWarning, if you use the feature that are due to be deprecated. These warnings are silent by default, but can be explicitly enabled when you're ready to start migrating any required changes. For example if you start running your tests using python -Wd manage.py test, you'll be warned of any API changes you need to make.
+
+
+
Version 1.2 would escalate these warnings to subclass DeprecationWarning, which is loud by default.
+
+
+
Version 1.3 would remove the deprecated bits of API entirely.
+
+
+
Note that in line with Django's policy, any parts of the framework not mentioned in the documentation should generally be considered private API, and may be subject to change.
This is the last Django REST Framework release that will support Python 2.
+Be sure to upgrade to Python 3 before upgrading to Django REST Framework 3.10.
+
+
Adjusted the compat check for django-guardian to allow the last guardian
+ version (v1.4.9) compatible with Python 2. #6613
Deprecate the Router.registerbase_name argument in favor of basename. #5990
+
Deprecate the Router.get_default_base_name method in favor of Router.get_default_basename. #5990
+
Change CharField to disallow null bytes. #6073
+ To revert to the old behavior, subclass CharField and remove ProhibitNullCharactersValidator from the validators.
+ python
+ class NullableCharField(serializers.CharField):
+ def __init__(self, *args, **kwargs):
+ super().__init__(*args, **kwargs)
+ self.validators = [v for v in self.validators if not isinstance(v, ProhibitNullCharactersValidator)]
+
Add OpenAPIRenderer and generate_schema management command. #6229
+
Add OpenAPIRenderer by default, and add schema docs. #6233
Alternatively you may override save() or create() or update() on the serializer as appropriate.
+
+
+
Correct allow_null behaviour when required=False #5888
+
Without an explicit default, allow_null implies a default of null for outgoing serialization. Previously such
+fields were being skipped when read-only or otherwise not required.
+
Possible backwards compatibility break if you were relying on such fields being excluded from the outgoing
+representation. In order to restore the old behaviour you can override data to exclude the field when None.
+
For example:
+
@property
+def data(self):
+ """
+ Drop `maybe_none` field if None.
+ """
+ data = super().data
+ if 'maybe_none' in data and data['maybe_none'] is None:
+ del data['maybe_none']
+ return data
+
+
+
+
Refactor dynamic route generation and improve viewset action introspectibility. #5705
+
ViewSets have been provided with new attributes and methods that allow
+it to introspect its set of actions and the details of the current action.
+
+
Merged list_route and detail_route into a single action decorator.
+
Get all extra actions on a ViewSet with .get_extra_actions().
+
Extra actions now set the url_name and url_path on the decorated method.
+
url_name is now based on the function name, instead of the url_path,
+ as the path is not always suitable (e.g., capturing arguments in the path).
+
Enable action url reversing through .reverse_action() method (added in 3.7.4)
+
Example reverse call: self.reverse_action(self.custom_action.url_name)
+
Add detail initkwarg to indicate if the current action is operating on a
+ collection or a single instance.
+
+
Additional changes:
+
+
Deprecated list_route & detail_route in favor of action decorator with detail boolean.
+
Deprecated dynamic list/detail route variants in favor of DynamicRoute with detail boolean.
+
Refactored the router's dynamic route generation.
+
list_route and detail_route maintain the old behavior of url_name,
+ basing it on the url_path instead of the function name.
Schema: Extract method for manual_fields processing #5633
+
Allows for easier customisation of manual_fields processing, for example
+to provide per-method manual fields. AutoSchema adds get_manual_fields,
+as the intended override point, and a utility method update_fields, to
+handle by-name field replacement from a list, which, in general, you are not
+expected to override.
+
Note: AutoSchema.__init__ now ensures manual_fields is a list.
+Previously may have been stored internally as None.
+
+
+
Remove ulrparse compatibility shim; use six instead #5579
+
+
Drop compat wrapper for TimeDelta.total_seconds()#5577
Fix DjangoModelPermissions to ensure user authentication before calling the view's get_queryset() method. As a side effect, this changes the order of the HTTP method permissions and authentication checks, and 405 responses will only be returned when authenticated. If you want to replicate the old behavior, see the PR for details. #5376
+
Deprecated exclude_from_schema on APIView and api_view decorator. Set schema = None or @schema(None) as appropriate. #5422
+
+
Timezone-aware DateTimeFields now respect active or default timezone during serialization, instead of always using UTC. #5435
+
Resolves inconsistency whereby instances were serialized with supplied datetime for create but UTC for retrieve. #3732
+
Possible backwards compatibility break if you were relying on datetime strings being UTC. Have client interpret datetimes or set default or active timezone (docs) to UTC if needed.
+
+
+
Removed DjangoFilterBackend inline with deprecation policy. Use django_filters.rest_framework.FilterSet and/or django_filters.rest_framework.DjangoFilterBackend instead. #5273
+
+
Don't strip microseconds from time when encoding. Makes consistent with datetime.
+ BC Change: Previously only milliseconds were encoded. #5440
+
Added STRICT_JSON setting (default True) to raise exception for the extended float values (nan, inf, -inf) accepted by Python's json module.
+ BC Change: Previously these values would converted to corresponding strings. Set STRICT_JSON to False to restore the previous behaviour. #5265
+
Add support for page_size parameter in CursorPaginator class #5250
+
Make DEFAULT_PAGINATION_CLASSNone by default.
+ BC Change: If your were just setting PAGE_SIZE to enable pagination you will need to add DEFAULT_PAGINATION_CLASS.
+ The previous default was rest_framework.pagination.PageNumberPagination. There is a system check warning to catch this case. You may silence that if you are setting pagination class on a per-view basis. #5170
+
Catch APIException from get_serializer_fields in schema generation. #5443
+
Allow custom authentication and permission classes when using include_docs_urls#5448
+
Defer translated string evaluation on validators. #5452
+
Added default value for 'detail' param into 'ValidationError' exception #5342
+
Adjust schema get_filter_fields rules to match framework #5454
+
Updated test matrix to add Django 2.0 and drop Django 1.8 & 1.9
+ BC Change: This removes Django 1.8 and Django 1.9 from Django REST Framework supported versions. #5457
+
Fixed a deprecation warning in serializers.ModelField #5058
+
Added a more explicit error message when get_queryset returned None#5348
Remove deprecated schema code from DefaultRouter #5482
+
Refactor schema generation to allow per-view customisation.
+ BC Change: SchemaGenerator.get_serializer_fields has been refactored as AutoSchema.get_serializer_fields and drops the view argument [#5354][gh5354]
Remove version string from templates. Thanks to @blag for the report and fixes. (#3878, #3913, #3912)
+
Fixes vertical html layout for BooleanField. Thanks to Mikalai Radchuk for the fix. (#3910)
+
Silenced deprecation warnings on Django 1.8. Thanks to Simon Charette for the fix. (#3903)
+
Internationalization for authtoken. Thanks to Michael Nacharov for the fix. (#3887, #3968)
+
Fix Token model as abstract when the authtoken application isn't declared. Thanks to Adam Thomas for the report. (#3860, #3858)
+
Improve Markdown version compatibility. Thanks to Michael J. Schultz for the fix. (#3604, #3842)
+
QueryParameterVersioning does not use DEFAULT_VERSION setting. Thanks to Brad Montgomery for the fix. (#3833)
+
Add an explicit on_delete on the models. Thanks to Mads Jensen for the fix. (#3832)
+
Fix DateField.to_representation to work with Python 2 unicode. Thanks to Mikalai Radchuk for the fix. (#3819)
+
Fixed TimeField not handling string times. Thanks to Areski Belaid for the fix. (#3809)
+
Avoid updates of Meta.extra_kwargs. Thanks to Kevin Massey for the report and fix. (#3805, #3804)
+
Fix nested validation error being rendered incorrectly. Thanks to Craig de Stigter for the fix. (#3801)
+
Document how to avoid CSRF and missing button issues with django-crispy-forms. Thanks to Emmanuelle Delescolle, José Padilla and Luis San Pablo for the report, analysis and fix. (#3787, #3636, #3637)
+
Improve Rest Framework Settings file setup time. Thanks to Miles Hutson for the report and Mads Jensen for the fix. (#3786, #3815)
+
Improve authtoken compatibility with Django 1.9. Thanks to S. Andrew Sheppard for the fix. (#3785)
+
Fix Min/MaxValueValidator transfer from a model's DecimalField. Thanks to Kevin Brown for the fix. (#3774)
+
Improve HTML title in the Browsable API. Thanks to Mike Lissner for the report and fix. (#3769)
+
Fix AutoFilterSet to inherit from default_filter_set. Thanks to Tom Linford for the fix. (#3753)
+
Fix transifex config to handle the new Chinese language codes. Thanks to @nypisces for the report and fix. (#3739)
+
DateTimeField does not handle empty values correctly. Thanks to Mick Parker for the report and fix. (#3731, #3726)
+
Raise error when setting a removed rest_framework setting. Thanks to Luis San Pablo for the fix. (#3715)
+
Add missing csrf_token in AdminRenderer post form. Thanks to Piotr Śniegowski for the fix. (#3703)
+
Refactored _get_reverse_relationships() to use correct to_field. Thanks to Benjamin Phillips for the fix. (#3696)
+
Document the use of get_queryset for RelatedField. Thanks to Ryan Hiebert for the fix. (#3605)
+
Fix empty pk detection in HyperlinkRelatedField.get_url. Thanks to @jslang for the fix (#3962)
Third Party Packages allow developers to share code that extends the functionality of Django REST framework, in order to support additional use-cases.
+
We support, encourage and strongly favor the creation of Third Party Packages to encapsulate new behavior rather than adding additional functionality directly to Django REST Framework.
+
We aim to make creating third party packages as easy as possible, whilst keeping a simple and well maintained core API. By promoting third party packages we ensure that the responsibility for a package remains with its author. If a package proves suitably popular it can always be considered for inclusion into the core REST framework.
+
If you have an idea for a new feature please consider how it may be packaged as a Third Party Package. We're always happy to discuss ideas on the Mailing List.
You can use this cookiecutter template for creating reusable Django REST Framework packages quickly. Cookiecutter creates projects from project templates. While optional, this cookiecutter template includes best practices from Django REST framework and other packages, as well as a Travis CI configuration, Tox configuration, and a sane setup.py for easy PyPI registration/distribution.
+
Note: Let us know if you have an alternate cookiecutter package so we can also link to it.
You'll be prompted for some questions, answer them, then it'll create your Python package in the current working directory based on those values.
+
full_name (default is "Your full name here")? Johnny Appleseed
+email (default is "you@example.com")? jappleseed@example.com
+github_username (default is "yourname")? jappleseed
+pypi_project_name (default is "dj-package")? djangorestframework-custom-auth
+repo_name (default is "dj-package")? django-rest-framework-custom-auth
+app_name (default is "djpackage")? custom_auth
+project_short_description (default is "Your project description goes here")?
+year (default is "2014")?
+version (default is "0.1.0")?
+
To put your project up on GitHub, you'll need a repository for it to live in. You can create a new repository here. If you need help, check out the Create A Repo article on GitHub.
We recommend using Travis CI, a hosted continuous integration service which integrates well with GitHub and is free for public repositories.
+
To get started with Travis CI, sign in with your GitHub account. Once you're signed in, go to your profile page and enable the service hook for the repository you want.
+
If you use the cookiecutter template, your project will already contain a .travis.yml file which Travis CI will use to build your project and run tests. By default, builds are triggered every time you push to your repository or create Pull Request.
The cookiecutter template assumes a set of supported versions will be provided for Python and Django. Make sure you correctly update your requirements, docs, tox.ini, .travis.yml, and setup.py to match the set of versions you wish to support.
The cookiecutter template includes a runtests.py which uses the pytest package as a test runner.
+
Before running, you'll need to install a couple test requirements.
+
$ pip install -r requirements.txt
+
+
Once requirements installed, you can run runtests.py.
+
$ ./runtests.py
+
+
Run using a more concise output style.
+
$ ./runtests.py -q
+
+
Run the tests using a more concise output style, no coverage, no flake8.
+
$ ./runtests.py --fast
+
+
Don't run the flake8 code linting.
+
$ ./runtests.py --nolint
+
+
Only run the flake8 code linting, don't run the tests.
+
$ ./runtests.py --lintonly
+
+
Run the tests for a given test case.
+
$ ./runtests.py MyTestCase
+
+
Run the tests for a given test method.
+
$ ./runtests.py MyTestCase.test_this_method
+
+
Shorter form to run the tests for a given test method.
+
$ ./runtests.py test_this_method
+
+
To run your tests against multiple versions of Python as different versions of requirements such as Django we recommend using tox. Tox is a generic virtualenv management and test command line tool.
+
First, install tox globally.
+
$ pip install tox
+
+
To run tox, just simply run:
+
$ tox
+
+
To run a particular tox environment:
+
$ tox -e envlist
+
+
envlist is a comma-separated value to that specifies the environments to run tests against. To view a list of all possible test environments, run:
Sometimes, in order to ensure your code works on various different versions of Django, Python or third party libraries, you'll need to run slightly different code depending on the environment. Any code that branches in this way should be isolated into a compat.py module, and should provide a single common interface that the rest of the codebase can use.
+
Check out Django REST framework's compat.py for an example.
Create a Pull Request or Issue on GitHub, and we'll add a link to it from the main REST framework documentation. You can add your package under Third party packages of the API Guide section that best applies, like Authentication or Permissions. You can also link your package under the Third Party Packages section.
djoser - Provides a set of views to handle basic actions such as registration, login, logout, password reset and account activation.
+
django-rest-auth - Provides a set of REST API endpoints for registration, authentication (including social media authentication), password reset, retrieve and update user details, etc.
+
drf-oidc-auth - Implements OpenID Connect token authentication for DRF.
+
drfpasswordless - Adds (Medium, Square Cash inspired) passwordless logins and signups via email and mobile numbers.
djangorestframework-hstore - Serializer class to support django-hstore DictionaryField model field and its schema-mode feature.
+
djangorestframework-jsonapi - Provides a parser, renderer, serializers, and other tools to help build an API that is compliant with the jsonapi.org spec.
+
html-json-forms - Provides an algorithm and serializer to process HTML JSON Form submissions per the (inactive) spec.
djangorestframework-queryfields - Serializer mixin allowing clients to control which fields will be sent in the API response.
+
drf-flex-fields - Serializer providing dynamic field expansion and sparse field sets via URL parameters.
+
drf-action-serializer - Serializer providing per-action fields config for use with ViewSets to prevent having to write multiple serializers.
+
djangorestframework-dataclasses - Serializer providing automatic field generation for Python dataclasses, like the built-in ModelSerializer does for models.
+
django-restql - Turn your REST API into a GraphQL like API(It allows clients to control which fields will be sent in a response, uses GraphQL like syntax, supports read and write on both flat and nested fields).
django-versatileimagefield - Provides a drop-in replacement for Django's stock ImageField that makes it easy to serve images in multiple sizes/renditions from a single field. For DRF-specific implementation docs, click here.
djangorestframework-jsonapi - Provides a parser, renderer, serializers, and other tools to help build an API that is compliant with the jsonapi.org spec.
djangorestframework-jsonapi - Provides a parser, renderer, serializers, and other tools to help build an API that is compliant with the jsonapi.org spec.
+
drf_ujson - Implements JSON rendering using the UJSON package.
+
rest-pandas - Pandas DataFrame-powered renderers including Excel, CSV, and SVG formats.
django-url-filter - Allows a safe way to filter data via human-friendly URLs. It is a generic library which is not tied to DRF but it provides easy integration with DRF.
+
drf-url-filter is a simple Django app to apply filters on drf ModelViewSet's Queryset in a clean, simple and configurable way. It also supports validations on incoming query params and their values.
+
django-rest-framework-guardian - Provides integration with django-guardian, including the DjangoObjectPermissionsFilter previously found in DRF.
cookiecutter-django-rest - A cookiecutter template that takes care of the setup and configuration so you can focus on making your REST apis awesome.
+
djangorestrelationalhyperlink - A hyperlinked serializer that can can be used to alter relationships via hyperlinks, but otherwise like a hyperlink model serializer.
django-versatileimagefield - Provides a drop-in replacement for Django's stock ImageField that makes it easy to serve images in multiple sizes/renditions from a single field. For DRF-specific implementation docs, click here.
+
drf-tracking - Utilities to track requests to DRF API views.
+
drf_tweaks - Serializers with one-step validation (and more), pagination without counts and other tweaks.
Want your Django REST Framework talk/tutorial/article to be added to our website? Or know of a resource that's not yet included here? Please submit a pull request or email us!
In order to provide schema support REST framework uses Core API.
+
Core API is a document specification for describing APIs. It is used to provide
+an internal representation format of the available endpoints and possible
+interactions that an API exposes. It can either be used server-side, or
+client-side.
+
When used server-side, Core API allows an API to support rendering to a wide
+range of schema or hypermedia formats.
+
When used client-side, Core API allows for dynamically driven client libraries
+that can interact with any API that exposes a supported schema or hypermedia
+format.
REST framework supports either explicitly defined schema views, or
+automatically generated schemas. Since we're using viewsets and routers,
+we can simply use the automatic schema generation.
+
You'll need to install the coreapi python package in order to include an
+API schema, and pyyaml to render the schema into the commonly used
+YAML-based OpenAPI format.
+
$ pip install coreapi pyyaml
+
+
We can now include a schema for our API, by including an autogenerated schema
+view in our URL configuration.
Now that our API is exposing a schema endpoint, we can use a dynamic client
+library to interact with the API. To demonstrate this, let's use the
+Core API command line client.
+
The command line client is available as the coreapi-cli package:
+
$ pip install coreapi-cli
+
+
Now check that it is available on the command line...
+
$ coreapi
+Usage: coreapi [OPTIONS] COMMAND [ARGS]...
+
+ Command line client for interacting with CoreAPI services.
+
+ Visit https://www.coreapi.org/ for more information.
+
+Options:
+ --version Display the package version number.
+ --help Show this message and exit.
+
+Commands:
+...
+
+
First we'll load the API schema using the command line client.
As well as the command line client, developers can also interact with your
+API using client libraries. The Python client library is the first of these
+to be available, and a Javascript client library is planned to be released
+soon.
+
For more details on customizing schema generation and using Core API
+client libraries you'll need to refer to the full documentation.
With an incredibly small amount of code, we've now got a complete pastebin Web API, which is fully web browsable, includes a schema-driven client library, and comes complete with authentication, per-object permissions, and multiple renderer formats.
+
We've walked through each step of the design process, and seen how if we need to customize anything we can gradually work our way down to simply using regular Django views.
The coreapi library is required as a dependency for the API docs. Make sure
+to install the latest version. The Pygments and Markdown libraries
+are optional but recommended.
+
To install the API documentation, you'll need to include it in your project's URLconf:
+
from rest_framework.documentation import include_docs_urls
+
+urlpatterns = [
+ ...
+ url(r'^docs/', include_docs_urls(title='My API title'))
+]
+
+
This will include two different views:
+
+
/docs/ - The documentation page itself.
+
/docs/schema.js - A JavaScript resource that exposes the API schema.
+
+
+
Note: By default include_docs_urls configures the underlying SchemaView to generate public schemas.
+This means that views will not be instantiated with a request instance. i.e. Inside the view self.request will be None.
+
To be compatible with this behaviour, methods (such as get_serializer or get_serializer_class etc.) which inspect self.request or, particularly, self.request.user may need to be adjusted to handle this case.
+
You may ensure views are given a request instance by calling include_docs_urls with public=False:
+
from rest_framework.documentation import include_docs_urls
+
+urlpatterns = [
+ ...
+ # Generate schema with valid `request` instance:
+ url(r'^docs/', include_docs_urls(title='My API title', public=False))
+]
+
You can document your views by including docstrings that describe each of the available actions.
+For example:
+
class UserList(generics.ListAPIView):
+ """
+ Return a list of all the existing users.
+ """
+
+
If a view supports multiple methods, you should split your documentation using method: style delimiters.
+
class UserList(generics.ListCreateAPIView):
+ """
+ get:
+ Return a list of all the existing users.
+
+ post:
+ Create a new user instance.
+ """
+
+
When using viewsets, you should use the relevant action names as delimiters.
+
class UserViewSet(viewsets.ModelViewSet):
+ """
+ retrieve:
+ Return the given user.
+
+ list:
+ Return a list of all the existing users.
+
+ create:
+ Create a new user instance.
+ """
+
+
Custom actions on viewsets can also be documented in a similar way using the method names
+as delimiters or by attaching the documentation to action mapping methods.
+
class UserViewSet(viewsets.ModelViewset):
+ ...
+
+ @action(detail=False, methods=['get', 'post'])
+ def some_action(self, request, *args, **kwargs):
+ """
+ get:
+ A description of the get method on the custom action.
+
+ post:
+ A description of the post method on the custom action.
+ """
+
+ @some_action.mapping.put
+ def put_some_action():
+ """
+ A description of the put method on the custom action.
+ """
+
The rest_framework.documentation module provides three helper functions to help configure the interactive API documentation, include_docs_urls (usage shown above), get_docs_view and get_schemajs_view.
+
include_docs_urls employs get_docs_view and get_schemajs_view to generate the url patterns for the documentation page and JavaScript resource that exposes the API schema respectively. They expose the following options for customisation. (get_docs_view and get_schemajs_view ultimately call rest_frameworks.schemas.get_schema_view(), see the Schemas docs for more options there.)
title: Default None. May be used to provide a descriptive title for the schema definition.
+
description: Default None. May be used to provide a description for the schema definition.
+
schema_url: Default None. May be used to pass a canonical base URL for the schema.
+
public: Default True. If True schema is generated without a request instance being passed to views.
+
patterns: Default None. A list of URLs to inspect when generating the schema. If None project's URL conf will be used.
+
generator_class: Default rest_framework.schemas.SchemaGenerator. May be used to specify a SchemaGenerator subclass to be passed to the SchemaView.
+
authentication_classes: Default api_settings.DEFAULT_AUTHENTICATION_CLASSES. May be used to pass custom authentication classes to the SchemaView.
+
permission_classes: Default api_settings.DEFAULT_PERMISSION_CLASSES. May be used to pass custom permission classes to the SchemaView.
+
renderer_classes: Default None. May be used to pass custom renderer classes to the SchemaView. If None the SchemaView will be configured with DocumentationRenderer and CoreJSONRenderer renderers, corresponding to the (default) html and corejson formats.
The built-in API documentation includes automatically generated code samples for
+each of the available API client libraries.
+
You may customise these samples by subclassing DocumentationRenderer, setting
+languages to the list of languages you wish to support:
+
from rest_framework.renderers import DocumentationRenderer
+
+
+class CustomRenderer(DocumentationRenderer):
+ languages = ['ruby', 'go']
+
+
For each language you need to provide an intro template, detailing installation instructions and such,
+plus a generic template for making API requests, that can be filled with individual request details.
+See the templates for the bundled languages for examples.
Under-the-hood, any subclass of coreapi.AutoSchema here will trigger use of the old CoreAPI schemas.
+Otherwise you will automatically be opted-in to the new OpenAPI schemas.
+
All CoreAPI related code will be removed in Django REST Framework v3.12. Switch to OpenAPI schemas by then.
+
+
For reference this folder contains the old CoreAPI related documentation:
A machine-readable [schema] describes what resources are available via the API, what their URLs are, how they are represented and what operations they support.
API schemas are a useful tool that allow for a range of use cases, including
+generating reference documentation, or driving dynamic client libraries that
+can interact with your API.
You'll need to install the coreapi package in order to add schema support
+for REST framework. You probably also want to install pyyaml, so that you
+can render the schema into the commonly used YAML-based OpenAPI format.
To generate a static API schema, use the generateschema management command.
+
$ python manage.py generateschema > schema.yml
+
+
+
Once you've generated a schema in this way you can annotate it with any
+additional information that cannot be automatically inferred by the schema
+generator.
+
You might want to check your API schema into version control and update it
+with each new release, or serve the API schema from your site's static media.
REST framework uses Core API in order to model schema information in
+a format-independent representation. This information can then be rendered
+into various different schema formats, or used to generate API documentation.
+
When using Core API, a schema is represented as a Document which is the
+top-level container object for information about the API. Available API
+interactions are represented using Link objects. Each link includes a URL,
+HTTP method, and may include a list of Field instances, which describe any
+parameters that may be accepted by the API endpoint. The Link and Field
+instances may also include descriptions, that allow an API schema to be
+rendered into user documentation.
+
Here's an example of an API description that includes a single search
+endpoint:
In order to be presented in an HTTP response, the internal representation
+has to be rendered into the actual bytes that are used in the response.
+
REST framework includes a few different renderers that you can use for
+encoding the API schema.
+
+
renderers.OpenAPIRenderer - Renders into YAML-based OpenAPI, the most widely used API schema format.
+
renderers.JSONOpenAPIRenderer - Renders into JSON-based OpenAPI.
+
renderers.CoreJSONRenderer - Renders into Core JSON, a format designed for
+use with the coreapi client library.
+
+
Core JSON is designed as a canonical format for use with Core API.
+REST framework includes a renderer class for handling this media type, which
+is available as renderers.CoreJSONRenderer.
It's worth pointing out here that Core API can also be used to model hypermedia
+responses, which present an alternative interaction style to API schemas.
+
With an API schema, the entire available interface is presented up-front
+as a single endpoint. Responses to individual API endpoints are then typically
+presented as plain data, without any further interactions contained in each
+response.
+
With Hypermedia, the client is instead presented with a document containing
+both data and available interactions. Each interaction results in a new
+document, detailing both the current state and the available interactions.
+
Further information and support on building Hypermedia APIs with REST framework
+is planned for a future version.
By default, view introspection is performed by an AutoSchema instance
+accessible via the schema attribute on APIView. This provides the
+appropriate Core API Link object for the view, request method and path:
(In compiling the schema, SchemaGenerator calls view.schema.get_link() for
+each view, allowed method and path.)
+
+
Note: For basic APIView subclasses, default introspection is essentially
+limited to the URL kwarg path parameters. For GenericAPIView
+subclasses, which includes all the provided class based views, AutoSchema will
+attempt to introspect serializer, pagination and filter fields, as well as
+provide richer path field descriptions. (The key hooks here are the relevant
+GenericAPIView attributes and methods: get_serializer, pagination_class,
+filter_backends and so on.)
+
+
To customise the Link generation you may:
+
+
+
Instantiate AutoSchema on your view with the manual_fields kwarg:
A string representing the import path to the URL conf that you want
+to generate an API schema for. This defaults to the value of Django's
+ROOT_URLCONF setting.
If you need a little more control than the get_schema_view() shortcut gives you,
+then you can use the SchemaGenerator class directly to auto-generate the
+Document instance, and to return that from a view.
+
This option gives you the flexibility of setting up the schema endpoint
+with whatever behaviour you want. For example, you can apply different
+permission, throttling, or authentication policies to the schema endpoint.
+
Here's an example of using SchemaGenerator together with a view to
+return the schema.
You can also serve different schemas to different users, depending on the
+permissions they have available. This approach can be used to ensure that
+unauthenticated requests are presented with a different schema to
+authenticated requests, or to ensure that different parts of the API are
+made visible to different users depending on their role.
+
In order to present a schema with endpoints filtered by user permissions,
+you need to pass the request argument to the get_schema() method, like so:
An alternative to the auto-generated approach is to specify the API schema
+explicitly, by declaring a Document object in your codebase. Doing so is a
+little more work, but ensures that you have full control over the schema
+representation.
class ListUsernames(APIView):
+ def get(self, request):
+ """
+ Return a list of all user names in the system.
+ """
+ usernames = [user.username for user in User.objects.all()]
+ return Response(usernames)
+
+
A ViewSet, with an explicit action docstring.
+
class ListUsernames(ViewSet):
+ def list(self, request):
+ """
+ Return a list of all user names in the system.
+ """
+ usernames = [user.username for user in User.objects.all()]
+ return Response(usernames)
+
+
A generic view with sections in the class docstring, using single-line style.
+
class UserList(generics.ListCreateAPIView):
+ """
+ get: List all the users.
+ post: Create a new user.
+ """
+ queryset = User.objects.all()
+ serializer_class = UserSerializer
+ permission_classes = [IsAdminUser]
+
+
A generic viewset with sections in the class docstring, using multi-line style.
+
class UserViewSet(viewsets.ModelViewSet):
+ """
+ API endpoint that allows users to be viewed or edited.
+
+ retrieve:
+ Return a user instance.
+
+ list:
+ Return all users, ordered by most recently joined.
+ """
+ queryset = User.objects.all().order_by('-date_joined')
+ serializer_class = UserSerializer
+
Return a nested dictionary containing all the links that should be included in the API schema.
+
This is a good point to override if you want to modify the resulting structure of the generated schema,
+as you can build a new dictionary with a different layout.
A class that deals with introspection of individual views for schema generation.
+
AutoSchema is attached to APIView via the schema attribute.
+
The AutoSchema constructor takes a single keyword argument manual_fields.
+
manual_fields: a list of coreapi.Field instances that will be added to
+the generated fields. Generated fields with a matching name will be overwritten.
Returns a string to use as the link description. By default this is based on the
+view docstring as described in the "Schemas as Documentation" section above.
Returns a string to indicate the encoding for any request body, when interacting
+with the given view. Eg. 'application/json'. May return a blank string for views
+that do not expect a request body.
Return a list of coreapi.Field() instances to be added to or replace generated fields. Defaults to (optional) manual_fields passed to AutoSchema constructor.
+
May be overridden to customise manual fields by path or method. For example, a per-method adjustment may look like this:
+
def get_manual_fields(self, path, method):
+ """Example adding per-method fields."""
+
+ extra_fields = []
+ if method=='GET':
+ extra_fields = # ... list of extra fields for GET ...
+ if method=='POST':
+ extra_fields = # ... list of extra fields for POST ...
+
+ manual_fields = super().get_manual_fields(path, method)
+ return manual_fields + extra_fields
+
Determines how the information is encoded into the request. Should be one of
+the following strings:
+
"path"
+
Included in a templated URI. For example a url value of /products/{product_code}/ could be used together with a "path" field, to handle API inputs in a URL path such as /products/slim-fit-jeans/.
Included as a URL query parameter. For example ?search=sale. Typically for GET requests.
+
These fields will normally correspond with pagination and filtering controls on a view.
+
"form"
+
Included in the request body, as a single item of a JSON object or HTML form. For example {"colour": "blue", ...}. Typically for POST, PUT and PATCH requests. Multiple "form" fields may be included on a single link.
+
These fields will normally correspond with serializer fields on a view.
+
"body"
+
Included as the complete request body. Typically for POST, PUT and PATCH requests. No more than one "body" field may exist on a link. May not be used together with "form" fields.
+
These fields will normally correspond with views that use ListSerializer to validate the request input, or with file upload views.
JSON encoded request content. Corresponds to views using JSONParser.
+Valid only if either one or more location="form" fields, or a single
+location="body" field is included on the Link.
+
"multipart/form-data"
+
Multipart encoded request content. Corresponds to views using MultiPartParser.
+Valid only if one or more location="form" fields is included on the Link.
+
"application/x-www-form-urlencoded"
+
URL encoded request content. Corresponds to views using FormParser. Valid
+only if one or more location="form" fields is included on the Link.
+
"application/octet-stream"
+
Binary upload request content. Corresponds to views using FileUploadParser.
+Valid only if a location="body" field is included on the Link.
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.
+
Every single sign-up helps us make REST framework long-term financially sustainable.
Add 'rest_framework' to your INSTALLED_APPS setting.
+
INSTALLED_APPS = [
+ ...
+ 'rest_framework',
+]
+
+
If you're intending to use the browsable API you'll probably also want to add REST framework's login and logout views. Add the following to your root urls.py file.
Let's take a look at a quick example of using REST framework to build a simple model-backed API.
+
We'll create a read-write API for accessing information on the users of our project.
+
Any global settings for a REST framework API are kept in a single configuration dictionary named REST_FRAMEWORK. Start off by adding the following to your settings.py module:
+
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'
+ ]
}
+
+
Don't forget to make sure you've also added rest_framework to your INSTALLED_APPS.
+
We're ready to create our API now.
+Here's our project's root urls.py module:
-
-
-
+# Routers provide an easy way of automatically determining the URL conf.
+router = routers.DefaultRouter()
+router.register(r'users', UserViewSet)
-
-
George Floyd
-
Natosha McDade, Yassin Mohamed, Finan H. Berhe, Sean Reed, Steven Demarco Taylor, Breonna Taylor, Ariane McCree, Terrance Franklin, Miles Hall, Darius Tarver, William Green, Samuel David Mallard, Kwame Jones, De’von Bailey, Christopher Whitfield, Anthony Hill, De’Von Bailey, Eric Logan, Jamarion Robinson, Gregory Hill Jr, JaQuavion Slaton, Ryan Twyman, Brandon Webber, Jimmy Atchison, Willie McCoy, Emantic Fitzgerald Bradford J, D’ettrick Griffin, Jemel Roberson, DeAndre Ballard, Botham Shem Jean, Robert Lawrence White, Anthony Lamar Smith, Ramarley Graham, Manuel Loggins Jr, Trayvon Martin, Wendell Allen, Kendrec McDade, Larry Jackson Jr, Jonathan Ferrell, Jordan Baker, Victor White III, Dontre Hamilton, Eric Garner, John Crawford III, Michael Brown, Ezell Ford, Dante Parker, Kajieme Powell, Laquan McDonald, Akai Gurley, Tamir Rice, Rumain Brisbon, Jerame Reid, Charly Keunang, Tony Robinson, Walter Scott, Freddie Gray, Brendon Glenn, Samuel DuBose, Christian Taylor, Jamar Clark, Mario Woods, Quintonio LeGrier, Gregory Gunn, Akiel Denkins, Alton Sterling, Philando Castile, Terrence Sterling, Terence Crutcher, Keith Lamont Scott, Alfred Olango, Jordan Edwards, Stephon Clark, Danny Ray Thomas, DeJuan Guillory, Patrick Harmon, Jonathan Hart, Maurice Granton, Julius Johnson, Jamee Johnson, Michael Dean...
-
-
+# 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'))
+]
+
+
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.
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.
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.
+
+
+
Neither the name of the copyright holder nor the names of its
+ contributors may be used to endorse or promote products derived from
+ this software without specific prior written permission.
+
+
+
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.
a",n=d.getElementsByTagName("*")||[],r=d.getElementsByTagName("a")[0],!r||!r.style||!n.length)return t;s=a.createElement("select"),u=s.appendChild(a.createElement("option")),o=d.getElementsByTagName("input")[0],r.style.cssText="top:1px;float:left;opacity:.5",t.getSetAttribute="t"!==d.className,t.leadingWhitespace=3===d.firstChild.nodeType,t.tbody=!d.getElementsByTagName("tbody").length,t.htmlSerialize=!!d.getElementsByTagName("link").length,t.style=/top/.test(r.getAttribute("style")),t.hrefNormalized="/a"===r.getAttribute("href"),t.opacity=/^0.5/.test(r.style.opacity),t.cssFloat=!!r.style.cssFloat,t.checkOn=!!o.value,t.optSelected=u.selected,t.enctype=!!a.createElement("form").enctype,t.html5Clone="<:nav>"!==a.createElement("nav").cloneNode(!0).outerHTML,t.inlineBlockNeedsLayout=!1,t.shrinkWrapBlocks=!1,t.pixelPosition=!1,t.deleteExpando=!0,t.noCloneEvent=!0,t.reliableMarginRight=!0,t.boxSizingReliable=!0,o.checked=!0,t.noCloneChecked=o.cloneNode(!0).checked,s.disabled=!0,t.optDisabled=!u.disabled;try{delete d.test}catch(h){t.deleteExpando=!1}o=a.createElement("input"),o.setAttribute("value",""),t.input=""===o.getAttribute("value"),o.value="t",o.setAttribute("type","radio"),t.radioValue="t"===o.value,o.setAttribute("checked","t"),o.setAttribute("name","t"),l=a.createDocumentFragment(),l.appendChild(o),t.appendChecked=o.checked,t.checkClone=l.cloneNode(!0).cloneNode(!0).lastChild.checked,d.attachEvent&&(d.attachEvent("onclick",function(){t.noCloneEvent=!1}),d.cloneNode(!0).click());for(f in{submit:!0,change:!0,focusin:!0})d.setAttribute(c="on"+f,"t"),t[f+"Bubbles"]=c in e||d.attributes[c].expando===!1;d.style.backgroundClip="content-box",d.cloneNode(!0).style.backgroundClip="",t.clearCloneStyle="content-box"===d.style.backgroundClip;for(f in x(t))break;return t.ownLast="0"!==f,x(function(){var n,r,o,s="padding:0;margin:0;border:0;display:block;box-sizing:content-box;-moz-box-sizing:content-box;-webkit-box-sizing:content-box;",l=a.getElementsByTagName("body")[0];l&&(n=a.createElement("div"),n.style.cssText="border:0;width:0;height:0;position:absolute;top:0;left:-9999px;margin-top:1px",l.appendChild(n).appendChild(d),d.innerHTML="
+ 
+ 
+ 
+ 
+ 
+ 