# Fetching metadata using Fetch JSON **URL:** \ **Category:** Ask for Help\ **Created:** [November 6, 2022, 3:49pm UTC](https://community.glideapps.com/t/fetching-metadata-using-fetch-json/53469 "2022-11-06T15:49:58Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Trustin](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/trustin/32/88217_2.png) [@Trustin](https://community.glideapps.com/u/Trustin)\ **Post date:** [November 6, 2022, 3:49pm UTC](https://community.glideapps.com/t/fetching-metadata-using-fetch-json/53469/1 "2022-11-06T15:49:58Z")
Hello community! I would like to retrieve data from a URL with metadata using Fetch JSON. Would like to know if anyone know what code to use for retrieving it? heres the metadata url: [https://pub-cd02cb317b314644935dbaea4d3e658d.r2.dev/5060](https://pub-cd02cb317b314644935dbaea4d3e658d.r2.dev/5060) ---
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [November 6, 2022, 4:26pm UTC](https://community.glideapps.com/t/fetching-metadata-using-fetch-json/53469/2 "2022-11-06T16:26:28Z")
Looks like you will need to use a CORS proxy to access that with Fetch JSON, eg: ```auto https://corsanywhere.herokuapp.com/https://pub-cd02cb317b314644935dbaea4d3e658d.r2.dev/5060 ``` ![Screen Shot 2022-11-07 at 12.25.03 AM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/1/b/1b8f949c15666293e458e7bab5b882b968e6808a.jpeg) ---
**Author:** ![Trustin](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/trustin/32/88217_2.png) [@Trustin](https://community.glideapps.com/u/Trustin)\ **Post date:** [November 7, 2022, 9:09am UTC](https://community.glideapps.com/t/fetching-metadata-using-fetch-json/53469/3 "2022-11-07T09:09:02Z")
Thanks! figure out the jquery to fetch the data using “.attributes[1].value” Testing it with this page helps alot! [Glide • Fetch JSON column](https://www.glideapps.com/plugins/fetch) ---
**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\ **Post date:** [November 7, 2022, 10:55pm UTC](https://community.glideapps.com/t/fetching-metadata-using-fetch-json/53469/4 "2022-11-07T22:55:57Z")
Please note that the server for corsanywhere can go down if there’s a lot of requests at once (from users all over the world). > > > The demo server of CORS Anywhere (cors-anywhere.herokuapp.com) is meant to be a …demo of this project. But abuse has become so common that the platform where the demo is hosted (Heroku) has asked me to shut down the server, despite efforts to counter the abuse (rate limits in #45 and #164, and blocking other forms of requests). Downtime becomes increasingly frequent (e.g. recently #300, #299, #295, #294, #287) due to abuse and its popularity. > > To counter this, I will make the following changes: > > 1. The rate limit will decrease from 200 (#164) per hour to 50 per hour. > 2. By January 31st, 2021, cors-anywhere.herokuapp.com will stop serving as an open proxy. > 3. From February 1st. 2021, cors-anywhere.herokuapp.com will only serve requests after the visitor has completed a challenge: The user (developer) must visit a page at cors-anywhere.herokuapp.com to temporarily unlock the demo for their browser. This allows developers to try out the functionality, to help with deciding on self-hosting or looking for alternatives. > > \### What should current users of CORS Anywhere do in response to this announcement? > If possible, try to avoid the need for a proxy at all. CORS Anywhere works by combining proxy functionality with \[CORS\](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS). You may not need proxy functionality, if the web service that you are trying to access already supports CORS. This is the preferred solution because it is faster and more reliable. For development, you can also consider the use of browser extensions that automatically enables CORS for certain websites. > > If your use of CORS Anywhere is infrequent, then the exception from step 3 above will allow you to continue as before. The only difference is that you need to explicitly opt in before access is temporarily allowed. If you'd like to not have these restrictions, then you should self-host CORS Anywhere. > > For an example of self-hosting, see https://github.com/Rob--W/cors-anywhere#demo-server . There are also many questions and answers about hosting on the issue tracker here (https://github.com/Rob--W/cors-anywhere/issues). If you have questions, please search for existing issues first before opening a new issue. Please read more on the usage of it, and alternatives, in the link above. ---
**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/system/32/53398_2.png) [@system](https://community.glideapps.com/u/system)\ **Post date:** [November 8, 2022, 10:56pm UTC](https://community.glideapps.com/t/fetching-metadata-using-fetch-json/53469/5 "2022-11-08T22:56:59Z")
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.