<h2 id="datetimefield"><a class="toclink" href="#datetimefield">DateTimeField</a></h2>

<p>A date and time representation.</p>

<p>Corresponds to <code>django.db.models.fields.DateTimeField</code>.</p>

<li><code>format</code> - A string representing the output format. If not specified, this defaults to the same value as the <code>DATETIME_FORMAT</code> settings key, which will be <code>'iso-8601'</code> unless set. Setting to a format string indicates that <code>to_representation</code> return values should be coerced to string output. Format strings are described below. Setting this value to <code>None</code> indicates that Python <code>datetime</code> objects should be returned by <code>to_representation</code>. In this case the datetime encoding will be determined by the renderer.</li>

<li><code>input_formats</code> - A list of strings representing the input formats which may be used to parse the date. If not specified, the <code>DATETIME_INPUT_FORMATS</code> setting will be used, which defaults to <code>['iso-8601']</code>.</li>

<h4 id="datetimefield-format-strings"><a class="toclink" href="#datetimefield-format-strings"><code>DateTimeField</code> format strings.</a></h4>

<p>Format strings may either be <a href="https://docs.python.org/3/library/datetime.html#strftime-and-strptime-behavior">Python strftime formats</a> which explicitly specify the format, or the special string <code>'iso-8601'</code>, which indicates that <a href="https://www.w3.org/TR/NOTE-datetime">ISO 8601</a> style datetimes should be used. (eg <code>'2013-01-29T12:34:56.000000Z'</code>)</p>

<hr />

<p><strong>Note</strong>: With the exception of <code>DjangoObjectPermissions</code>, the provided

methods necessary to check object permissions.</p>

<p>If you wish to use the provided permission classes in order to check object

permissions, <strong>you must</strong> subclass them and implement the

<pre><code>pip install coreapi pyyaml

<h2 id="quickstart"><a class="toclink" href="#quickstart">Quickstart</a></h2>

<h3 id="generating-a-schema-with-the-generateschema-management-command"><a class="toclink" href="#generating-a-schema-with-the-generateschema-management-command">Generating a schema with the <code>generateschema</code> management command</a></h3>

<p>To generate a static API schema, use the <code>generateschema</code> management command.</p>

<pre><code class="shell">$ python manage.py generateschema &gt; schema.yml

user.save()

return user

<h2 id="relational-fields"><a class="toclink" href="#relational-fields">Relational fields</a></h2>

<p>When serializing model instances, there are a number of different ways you might choose to represent relationships. The default representation for <code>ModelSerializer</code> is to use the primary keys of the related instances.</p>

<p>Alternative representations include serializing using hyperlinks, serializing complete nested representations, or serializing with a custom representation.</p>

<p>The default implementation returns a serializer class based on the <code>serializer_field_mapping</code> attribute.</p>

<h3 id="build_relational_fieldself-field_name-relation_info"><a class="toclink" href="#build_relational_fieldself-field_name-relation_info"><code>.build_relational_field(self, field_name, relation_info)</code></a></h3>

<p>Called to generate a serializer field that maps to a relational model field.</p>

<p>The <code>relation_info</code> argument is a named tuple, that contains <code>model_field</code>, <code>related_model</code>, <code>to_many</code> and <code>has_through_model</code> properties.</p>

<h3 id="build_nested_fieldself-field_name-relation_info-nested_depth"><a class="toclink" href="#build_nested_fieldself-field_name-relation_info-nested_depth"><code>.build_nested_field(self, field_name, relation_info, nested_depth)</code></a></h3>

<p>Called to generate a serializer field that maps to a relational model field, when the <code>depth</code> option has been set.</p>

def to_representation(self, obj):

for attribute_name in dir(obj):

attribute = getattr(obj, attribute_name)

# Ignore private attributes.

pass

elif hasattr(attribute, '__call__'):

def to_representation(self, obj):

for attribute_name in dir(obj):

attribute = getattr(obj, attribute_name)

# Ignore private attributes.

pass

elif hasattr(attribute, '__call__'):

<hr />

<h2 id="39x-series"><a class="toclink" href="#39x-series">3.9.x series</a></h2>

<h3 id="392"><a class="toclink" href="#392">3.9.2</a></h3>

<p><strong>Date</strong>: <a href="https://github.com/encode/django-rest-framework/milestone/71?closed=1">3rd March 2019</a></p>

<li>Introduced <code>RemovedInDRF…Warning</code> classes to simplify deprecations. <a href="https://github.com/encode/django-rest-framework/issues/6480">#6480</a></li>

<h3 id="391"><a class="toclink" href="#391">3.9.1</a></h3>

<li>Resolve XSS issue in browsable API. <a href="https://github.com/encode/django-rest-framework/issues/6330">#6330</a></li>

<li>Upgrade Bootstrap to 3.4.0 to resolve XSS issue.</li>

</div> <!--/span-->

<li><a href="https://github.com/raphaelgyory/django-rest-messaging">django-rest-messaging</a>, <a href="https://github.com/raphaelgyory/django-rest-messaging-centrifugo">django-rest-messaging-centrifugo</a> and <a href="https://github.com/raphaelgyory/django-rest-messaging-js">django-rest-messaging-js</a> - A real-time pluggable messaging service using DRM.</li>

<li><a href="https://github.com/dealertrack/djangorest-alchemy">djangorest-alchemy</a> - SQLAlchemy support for REST framework.</li>

<li><a href="https://github.com/izimobil/django-rest-framework-datatables">djangorestframework-datatables</a> - Seamless integration between Django REST framework and <a href="https://datatables.net">Datatables</a>.</li>