Api call blocked by missing Access-Control-Allow-Origin header about ethgaswatch HOT 3 CLOSED

Thank you for the reply! The app I am working on has no backend and is a client side only app. Is it possible to change the allowed origins to be more permissive?

from ethgaswatch.

CORS has its benefits, even though the API only has GET methods and doesn't mutate anything.
This way, it also requires a bit of effort for other projects to consume the services. Which also prevents anyone to just spam the service.

So I'm a bit hesitant to just allow anyone.
But I did update the 3 endpoints described in the docs to allow all (*) for now.
Should make it work for you.

I'll continue to monitor traffic and usage.

from ethgaswatch.

Have you tried calling it from your own back-end/service?

If you're calling the service from the client-side, then you might indeed run into a CORS issue. As only ethgas.watch itself is a known origin.

from ethgaswatch.