Django Rest Framework - I have working API with curl commands, how can I change it to work with standard http requests in browser?

@Peksio- Actually, it is not that hard. You have two options if you are using Django

1. The typical Django way
2. The DRF way

You can create a Django view (GET/POST), wire up a models.py, and then add in urls.py. If you want it to be an API then you can simply call the endpoint depending on the HTTP method and Voila. You are done

The DRF way is even simpler.

1. Install Django rest framework
2. Create a file called serializers.py (to serialize your model)
3. Create a viewset which is kind of like the django view.Only that you have to add in a queryset, serializer
4. Add in a router or just a URL in urls.py and you are all done.

If you are using Token Based Authentication then DRF supports that too https://www.django-rest-framework.org/api-guide/authentication/

For JWT based authentication https://simpleisbetterthancomplex.com/tutorial/2018/12/19/how-to-use-jwt-authentication-with-django-rest-framework.html

I think you have a bit of a misunderstanding of what curl and HTTP requests actually are.

Both curl and web browsers make HTTP request calls the same way. For example when you type http://www.example.com/?apikey=123 into your browser then the browser actually makes a HTTP GET request to http://www.example.com/?apikey=123. The curl equivalent for this would be: curl -X "GET" http://www.example.com/?apikey=123 which sends the same HTTP GET request.

Now that that is clear lets see the difference between the two formats you provided.

For starters you need to have a basic understanding of what HTTP request actually is. Your typical HTTP request which would go to an API endpoint consists of the following:

• method - GET, POST, PATCH, ...
• URL - http://www.example.com/
• query params (which are actually part of the URL) - apikey=123 or ordering=created_at for example
• headers - Content-Type: application/json or Authorization: apikey 123 for example
• body - any kind of data (can be form like, json, raw text, binary, just about anything)

Now the only difference in the two formats you provided is placement of authorization value (Token, apikey). In your first format it is place in the headers part of the HTTP request as a value of Authorization key. In your second format it is placed in the query params part of the HTTP request as a value of apikey.

Hope that clears it up a bit.