Databases
StackOverflow2013
Postsdbo
POWhy does HTTP POST request body need to be JSON enconded in Python?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy does HTTP POST request body need to be JSON enconded in Python?
    primarykey
    data
    text
    <p>I ran into this issue when playing around with an external API. I was sending my body data as a dictionary straight into the request and was getting 400 errors:</p> <pre><code>data = { "someParamRange": { "to": 1000, "from": 100 }, "anotherParamRange": { "to": True, "from": False } } </code></pre> <p>When I added a json.dumps wrap, it works:</p> <pre><code>data = json.dumps({ "someParamRange": { "to": 1000, "from": 100 }, "anotherParamRange": { "to": True, "from": False } }) </code></pre> <p>I don't entirely understand why this is necessary, as dictionaries and JSON objects are syntactically identical. Can someone help me understand what is going on behind the scenes here?</p> <p>For completeness, here are my headers:</p> <pre><code>headers = {'API-KEY': 'blerg', 'Accept-Encoding': 'UTF-8', 'Content-Type': 'application/json', 'Accept': '*/*', 'username': 'user', 'password': 'pwd'} </code></pre> <p>EDIT:</p> <p>I didn't mention this earlier but now I feel that it may be relevant. I am using the Python Requests library, and another post seems to suggest that you should never have to encode parameters to a request object: <a href="https://stackoverflow.com/a/14804320/1012040">https://stackoverflow.com/a/14804320/1012040</a></p> <p>"Regardless of whether GET/POST you never have to encode parameters again, it simply takes a dictionary as an argument and is good to go."</p> <p>Seems like serialization shouldn't be necessary?</p> <p>My request object:</p> <pre><code>response = requests.post(url, data=data, headers=headers) </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USacpigeon
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhy does HTTP POST request body need to be JSON enconded in Python?
      1. USuser1316408
      1. VTFavorite
    1. COyou should post the rest of your code .. I could make an http api where either would work equivalently.
      singulars
      1. POWhy does HTTP POST request body need to be JSON enconded in Python?
      1. UScwa
    2. COit's not a public API, o/w I would :( Are you saying that this could just be a function of the specific API as opposed to something general to HTTP requests?
      singulars
      1. POWhy does HTTP POST request body need to be JSON enconded in Python?
      1. USacpigeon
    3. COI suggest reading up on object serialization. `json.dump` serializes the object so that it can be sent as a data stream, in essence. Inserting the object directly will send across a binary stream of data that the server won't know how to decode.
      singulars
      1. POWhy does HTTP POST request body need to be JSON enconded in Python?
      1. USPhD
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload