# Deserializing JSON response using RestSharp

**URL:** <https://club.ministryoftesting.com/t/deserializing-json-response-using-restsharp/18229>\
**Category:** Discussions\
**Tags:** automation\
**Created:** [7 September 2018 08:15 UTC](https://club.ministryoftesting.com/t/deserializing-json-response-using-restsharp/18229 "2018-09-07T08:15:01Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![tilston1001](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/tilston1001/32/2095_2.png) [@tilston1001](https://club.ministryoftesting.com/u/tilston1001)\
**Post date:** [7 September 2018 09:59 UTC](https://club.ministryoftesting.com/t/deserializing-json-response-using-restsharp/18229/6 "2018-09-07T09:59:02Z")

</div>

@vivrichards I’ve logged a separate post for my other question so that it’s separated

> [@What are the pro's and con's of writing an API test automation framework at code level as opposed to using a tool](https://club.ministryoftesting.com/t/what-are-the-pros-and-cons-of-writing-an-api-test-automation-framework-at-code-level-as-opposed-to-using-a-tool/18232):
>
> As I look into writing automation frameworks at the API layer(relatively new to this area), a question that keeps cropping up in my mind is…why should I write an automation framework at code level in C#(with RestSharp) or Java(RestAssured), as opposed to using a tool like Postman or SoapUI and utilising what they have to create a framework? What would be the pro’s and con’s of each?

---

_[View the full topic](https://club.ministryoftesting.com/t/deserializing-json-response-using-restsharp/18229)._