# Define request body schema

**URL:** <https://community.postman.com/t/define-request-body-schema/6748>\
**Category:** Help Hub\
**Created:** [July 24, 2019, 6:48pm UTC](https://community.postman.com/t/define-request-body-schema/6748 "2019-07-24T18:48:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![helder.pinhal](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/helder.pinhal/32/2391_2.png) [@helder.pinhal](https://community.postman.com/u/helder.pinhal)\
**Post date:** [July 24, 2019, 6:48pm UTC](https://community.postman.com/t/define-request-body-schema/6748/1 "2019-07-24T18:48:24Z")

</div>

Hi all,

I would to document our product’s API with Postman.  
I see the API’s BETA feature which allows me to design it based on the OpenAPI specification.  
This would be the preferred scenario, however, I cannot understand how I can publish the document from the spec other than “generate collection \> publish documentation”.  
The problem with this approach is that it loses the schema definitions (request body, response schema).

What’s the go-to with Postman when it comes to documenting the schema of bodies and responses?

Kind regards,  
Helder

---

<div class="post-metadata">

**Author:** ![postman-kyle](https://avatars.discourse-cdn.com/v4/letter/p/47e85d/32.png) [@postman-kyle](https://community.postman.com/u/postman-kyle)\
**Post date:** [July 26, 2019, 5:01pm UTC](https://community.postman.com/t/define-request-body-schema/6748/2 "2019-07-26T17:01:09Z")

</div>

Hey Helder,

Basically you’d save your response from your API as an example and it would actually show as the response schema.

 ![save_to_response](https://us1.discourse-cdn.com/getpostman/original/3X/0/9/099c20a7f587f535d1d10e305db93a426efad64b.png)