# Clarion 6.3 and JSon Consumption

**URL:** <https://clarionhub.com/t/clarion-6-3-and-json-consumption/1765>\
**Category:** questions\
**Created:** [April 5, 2018, 2:02pm UTC](https://clarionhub.com/t/clarion-6-3-and-json-consumption/1765 "2018-04-05T14:02:55Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![brahn](https://clarionhub.com/user_avatar/clarionhub.com/brahn/32/756_2.png) [@brahn](https://clarionhub.com/u/brahn)\
**Post date:** [April 6, 2018, 12:25am UTC](https://clarionhub.com/t/clarion-6-3-and-json-consumption/1765/4 "2018-04-06T00:25:03Z")

</div>

Another option is to dabble in a little bit of interop and do it via .Net

> [@Querying JSON with SelectToken](https://clarionhub.com/t/querying-json-with-selecttoken/1499):
>
> For some time I have been using an UnmanagedExports wrapper around [JsonTextReader and JsonTextWriter](https://www.newtonsoft.com/json/help/html/ReadingWritingJSON.htm) from [Json.NET](https://www.newtonsoft.com/json) which was quite handy but had limitations. Today I have added the ability to Querying [JSON with SelectToken](https://www.newtonsoft.com/json/help/html/QueryJsonSelectToken.htm) which so far is pretty damn awesome! Consider this JSON data for input: { "solutions": [{ "departureTime": "08:24", "rego": "ABC123", }, { "departureTime": "09:24", "rego": "ZZZ321", }]…

---

_[View the full topic](https://clarionhub.com/t/clarion-6-3-and-json-consumption/1765)._