# Best way to parse json input? **URL:** https://discuss.elastic.co/t/best-way-to-parse-json-input/29809 **Category:** Logstash **Created:** [September 22, 2015, 7:43pm UTC](https://discuss.elastic.co/t/best-way-to-parse-json-input/29809 "2015-09-22T19:43:48Z") **Posts on this page:** 1 **Showing post:** 7
### Author: ![CraigFoote](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/craigfoote/32/4571_2.png) [@CraigFoote](https://discuss.elastic.co/u/CraigFoote) #### Post date: [September 23, 2015, 2:59pm UTC](https://discuss.elastic.co/t/best-way-to-parse-json-input/29809/7 "2015-09-23T14:59:46Z")
Yeah I think you're right. I think I can get my data as one line (not pretty-printed) though so where does that leave me? What's the best input to use with single line json? Eventually I need to fetch the json through a REST service using something like http\_poller but it doesn't seem to work for https ([Does http\_poller handle https?](https://discuss.elastic.co/t/does-http-poller-handle-https/28864)). In the meantime I have some of the json to test with, I'm just trying to get it into elasticsearch somehow. So far the file input with json\_lines codec is out. I guess I'll try flattening the json to one line and try some other configs. Any tips appreciated! --- _[View the full topic](https://discuss.elastic.co/t/best-way-to-parse-json-input/29809)._