#Expected a dict object code#

Set automatically by the APIView or immediately before the response is returned from the view. Set automatically by the APIView or immediately before the response is returned from the view.renderer_contextĪ dictionary of additional context information that will be passed to the renderer's. The media type that was selected by the content negotiation stage. Set automatically by the APIView or immediately before the response is returned from the view.accepted_media_type The renderer instance that will be used to render the response. Only required if HTMLRenderer or some other custom template renderer is the accepted renderer for the response.accepted_renderer render() method must have been called before.

#Expected a dict object code#

The numeric status code of the HTTP ntent

The unrendered, serialized data of the response.status_code 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. content_type: The content type of the response.headers: A dictionary of HTTP headers to use in the response.template_name: A template name to use if HTMLRenderer is selected.

status: A status code for the response.

data: The serialized data for the response.

You can use REST framework's Serializer classes to perform this data serialization, or use your own custom serialization. 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. Instead you pass in unrendered data, which may consist of any Python primitives.

Unlike regular HttpResponse objects, you do not instantiate Response objects with rendered content. Signature: Response(data, status=None, template_name=None, headers=None, content_type=None) 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. Unless you want to heavily customize REST framework for some reason, you should always use an APIView class or function for views that return Response objects. Using the Response class simply provides a nicer interface for returning content-negotiated Web API responses, that can be rendered to multiple formats. 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. REST framework then uses standard HTTP content negotiation to determine how it should render the final response content. Response objects are initialised with data, which should consist of native Python primitives. The Response class subclasses Django's SimpleTemplateResponse. 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 final output of the response is not computed until it is needed, later in the response process.

Unlike basic HttpResponse objects, TemplateResponse objects retain the details of the context that was provided by the view to compute the response.