# Working with different needs in raw/cooked content

**URL:** <https://meta.discourse.org/t/working-with-different-needs-in-raw-cooked-content/46723>\
**Category:** Development\
**Created:** [July 1, 2016, 7:36pm UTC](https://meta.discourse.org/t/working-with-different-needs-in-raw-cooked-content/46723 "2016-07-01T19:36:07Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [May 15, 2025, 12:20am UTC](https://meta.discourse.org/t/working-with-different-needs-in-raw-cooked-content/46723/8 "2025-05-15T00:20:01Z")

</div>

> [@cappslock](#):
>
> Yes, but doing that for every post is going to get expensive. Ideally I want a way to get this off the topic API (`t/:topicId.json`)

This is already implemented these days, by adding ?include\_raw=true

Eg:

```plaintext
https://meta.discourse.org/t/working-with-different-needs-in-raw-cooked-content/46723.json?include_raw=true

```

---

_[View the full topic](https://meta.discourse.org/t/working-with-different-needs-in-raw-cooked-content/46723)._