Inconsistency in API output about docs HOT 6 CLOSED

Yes, exactly. Sorry if that was a bit confusing.

All of the current API endpoints for fetching posts (like the one above) can possibly return legacy posts alongside new NPF posts, depending on how the post was made. To maintain backwards compatibility, new NPF posts will look and act like legacy text/regular type posts using these endpoints (hence why they have body set). You can change this behavior and have post content served consistently as NPF by setting npf=true via a query string parameter, which is more closely aligned with how we deal with post content within Tumblr's official clients.

from docs.

I think you should state that in the docs, it's not really clear.

Sure, happy to try to make this clearer. I'll see what I can do. 👌

from docs.

This is likely a consequence of the newer post being saved in the Neue Post Format, and the older one being saved in the legacy format. Generally speaking, post types are becoming deprecated on Tumblr under the hood. You can read more about this here and on the Engineering blog in general, as well as the documentation in this repo for the NPF spec. I strongly encourage you to check out leveraging ?npf=true and the Neue Post Format JSON so you can get consistent results here. You can still use filters like /posts/photo, but it may not always work the way you expect for new posts, see the legacy post type mapping here. Hope this helps!

from docs.

Just to understand better, you mean that the above weird answer is a consequence of requesting a NPF post over the old API?

from docs.

Thank you for your answer @cyle! I've tried and it works with npf=true.
I think you should state that in the docs, it's not really clear.

from docs.

Updated the docs with some blurbs about this, FYI ba6c02e

from docs.