The POST /user/filtered_content examples don't work about docs HOT 8 CLOSED

Docs have been updated in the latest commit to explicitly mention how Content-Type headers are expected to work: c08e8e9

Thanks again for raising this issue, and sorry it was confusing!

from docs.

The web client uses form data as the first example shows... are you maybe omitting Content-Type: application/x-www-form-urlencoded; charset=UTF-8 in the request headers?

from docs.

Ah, that's where the disconnect is, I'm implementing a client library, so I'm expecting API calls to be a standard post request.
If the web client uses a different request format, that should probably be documented on the web client documentation and not in the standard API documentation with all of the other JSON based APIs .

from docs.

Hello! Thanks for pointing this out. @AprilSylph is correct: this endpoint expects Content-Type: application/x-www-form-urlencoded, not Content-Type: application/json. Most of the Tumblr API endpoints can accept either, but in some cases, like creating NPF posts, they can only accept one format. We'll update the documentation to make this clearer.

from docs.

But the API currently does support application/json requests for POST, GET, and DELETE, is that unintentional functionality that will be removed?

from docs.

But the API currently does support application/json requests for POST, GET, and DELETE, is that unintentional functionality that will be removed?

No, definitely not. I just meant that we'll be clarifying these different acceptable Content-Type headers -- application/json is one of them. 👌 The core problem I think you've uncovered is that not providing the header at all can lead to unexpected behavior, as you saw.

from docs.

Actually, I always provided a header, but for my first attempts it was text/plain.

I'll update my PR to show both.

from docs.

We'll be pushing an update to the docs soon with a new top level section on valid Content-Type values across all endpoints that expect body parameters.

from docs.