# Couldn't send Gatling post request

**URL:** <https://community.gatling.io/t/couldnt-send-gatling-post-request/5136>\
**Category:** Gatling (Open-Source)\
**Created:** [July 19, 2019, 11:17am UTC](https://community.gatling.io/t/couldnt-send-gatling-post-request/5136 "2019-07-19T11:17:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Midhuna\_Kumar](https://avatars.discourse-cdn.com/v4/letter/m/ac91a4/32.png) [@Midhuna\_Kumar](https://community.gatling.io/u/Midhuna_Kumar)\
**Post date:** [July 19, 2019, 11:17am UTC](https://community.gatling.io/t/couldnt-send-gatling-post-request/5136/1 "2019-07-19T11:17:07Z")

</div>

Hi Team,

I am new for Gatling and for my current project i have stared working on it. I am able to create GET request and get the proper response  
But while try to send POST request using Gatling am getting 400 response even provided valid data.

Same POST request with Json file I am able to send by Jmeter and get the response.  
So can you please help me to overcode this issue. Below I am sharing post request code and error where i am strucking.

Thanks Advance.

**16:44:32.816 [WARN] i.g.h.a.ResponseProcessor - Request 'Create New Brand: status.find.is(200), but actually found 400**  
**Some Restful Service:**  
**{“timestamp”:“2019-07-19T11:14:32.740Z”,“errorCode”:“BRAND\_ALREADY\_EXISTS”,“message”:“GS00471392019071940318”,“path”:**

http(“Create Quotation”).post(some post path)  
.body(RawFileBody("/app/postBrand.json")).asJSON  
.headers(headers\_1)  
.check(status.is(200))  
.check(status.is(200), jsonPath("$.validationResult.isValid").is(“true”), jsonPath("$.brandId").exists)  
.check(jsonPath("$.brandId").find.saveAs(“brandId”))

---

<div class="post-metadata">

**Author:** ![James\_Warr](https://avatars.discourse-cdn.com/v4/letter/j/258eb7/32.png) [@James\_Warr](https://community.gatling.io/u/James_Warr)\
**Post date:** [July 20, 2019, 10:14am UTC](https://community.gatling.io/t/couldnt-send-gatling-post-request/5136/2 "2019-07-20T10:14:54Z")

</div>

Your API is returning a 400 status with a pretty clear error message - that’s where the problem lies