# Body in GET requests

**URL:** <https://community.smartbear.com/t/body-in-get-requests/118>\
**Category:** ReadyAPI\
**Tags:** readyapi, api, migrated\
**Created:** [April 18, 2019, 8:43am UTC](https://community.smartbear.com/t/body-in-get-requests/118 "2019-04-18T08:43:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://avatars.discourse-cdn.com/v4/letter/s/bcef8e/32.png) [@system](https://community.smartbear.com/u/system)\
**Post date:** [April 18, 2019, 8:43am UTC](https://community.smartbear.com/t/body-in-get-requests/118/1 "2019-04-18T08:43:08Z")

</div>

> Originally posted by **Voropaeva\_Kris** on April 18, 2019

Hello! How I can use the body with json-structure in GET requests? I haven’t MediaType place on GET requests so I haven’t place, which I can use for my request body.

Can I send body in GET response? How I can do it if it’s possible?

---

<div class="post-metadata">

**Author:** ![system](https://avatars.discourse-cdn.com/v4/letter/s/bcef8e/32.png) [@system](https://community.smartbear.com/u/system)\
**Post date:** [April 18, 2019, 9:08am UTC](https://community.smartbear.com/t/body-in-get-requests/118/2 "2019-04-18T09:08:45Z")

</div>

> Originally posted by **richie** on April 18, 2019

Hey Voropaeva\_Kris

Right - all the HTTP and w3c rules around the GET method indicate you don’t include a payload with a GET - you filter your GET based on the parameters on the request (URI/Template, Query and occasionally Header parms also).

REST rules apparently don’t define things as tightly as that - they just indicate use whatever method gets the job done, but as I say a GET request is filtered by the parms - not by a payload.

Someone else asked this quite recently on the board.

There are certain times that you have to switch the method from a GET to say a POST (if the query parms and values become too lengthy to be encoded) and this would allow you to create a payload with your GET request - cos essentially it wouldn’t be a GET anymore - but a POST.

Yes Postman does allow you to create a payload for a GET, but that’s only because there’s less field validation in Postman than SoapUI/ReadyAPI!

Including a GET on a payload has always been considered a faux pas in the places I’ve worked.

Are you sure you need to include a payload on yoru GET request? if I were you, I’d go back to the developers and query why they think you need a payload for a GET as this deviates from all the standard rules around GET requests - see w3c, etc.

Hence this is why SoapUI/ReadyAPI! doesn’t include any MediaType dropdown for the GET request - it was developed with the understanding you don’t include a payload with a GET request, so you don’t need to define the type!

Thanks,

richie

---

<div class="post-metadata">

**Author:** ![system](https://avatars.discourse-cdn.com/v4/letter/s/bcef8e/32.png) [@system](https://community.smartbear.com/u/system)\
**Post date:** [October 7, 2026, 5:11pm UTC](https://community.smartbear.com/t/body-in-get-requests/118/3 "2026-10-07T17:11:48Z")

</div>

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.