# 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:** [01.Июль.2016 19:36:07 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:** 5

<div class="post-metadata">

### Author: ![cappslock](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cappslock/32/120789_2.png) [@cappslock](https://meta.discourse.org/u/cappslock)
#### Post date: [02.Июль.2016 21:16:13 UTC](https://meta.discourse.org/t/working-with-different-needs-in-raw-cooked-content/46723/5 "2016-07-02T21:16:13Z")

</div>

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`)

BTW, how do you know about that route? Is there some better API documentation than this topic: [Discourse REST API Documentation](https://meta.discourse.org/t/discourse-api-documentation/22706)

---

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