# A way to parse this rather strange api

**URL:** <https://community.thunkable.com/t/a-way-to-parse-this-rather-strange-api/1042302>\
**Category:** Questions about Thunkable X\
**Tags:** json\
**Created:** [January 7, 2021, 2:06am UTC](https://community.thunkable.com/t/a-way-to-parse-this-rather-strange-api/1042302 "2021-01-07T02:06:26Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![drted](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/drted/32/92694_2.png) [@drted](https://community.thunkable.com/u/drted)\
**Post date:** [January 7, 2021, 2:22am UTC](https://community.thunkable.com/t/a-way-to-parse-this-rather-strange-api/1042302/2 "2021-01-07T02:22:33Z")

</div>

Here is a link to my approach

> [@Extract a LIST from JSON](http://community.thunkable.com/t/extract-a-list-from-json/779954/5):
>
> Pedro, With the Web\_API URL you sent, I was able to get to the latitude and longitude values and use them to build a new list. Notice how at each step I checked. the value. My experience has taught me that when working with complex JSON in Thunkable, do not try to build all of the blocks up front. Build one loop at a time, and check the results as you go. I’ve included a screenshot as well as a link to the project (with the URL removed). [https://x.thunkable.com/copy/633fe638c21cb…](https://x.thunkable.com/copy/633fe638c21cbbdbfd6a695eddadb54b)

Go one level at a time checking the available properties. The is is a list of objects, which can make it a bit tricky. Try to isolate you parsing routine and post both the blocks and the results to the group and we can provide more specific feedback.

---

_[View the full topic](https://community.thunkable.com/t/a-way-to-parse-this-rather-strange-api/1042302)._