Skip to content

Old Algoexplorer API Url causing 50X Bad Gateway Errors #16

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Flying-Bison-Appa opened this issue Dec 10, 2021 · 2 comments
Closed

Old Algoexplorer API Url causing 50X Bad Gateway Errors #16

Flying-Bison-Appa opened this issue Dec 10, 2021 · 2 comments

Comments

@Flying-Bison-Appa
Copy link

Flying-Bison-Appa commented Dec 10, 2021

Hey,

I'm getting frequent and inconsistent 500 Bad Gateway Errors from fetch_asset, fetch_pool, etc calls. Looking at tinyman/v1/client.py I noticed the AlgoExplorer API Link referenced seems to be the old API. Based on their developer docs: https://algoexplorer.io/api-dev/v2 the new URL is https://algoexplorerapi.io (Current used in file is https://api.algoexplorer.io). I tried changing that value in a local copy of this module and it started working consistently. I believe a similar shift is also needed for the testnet client as well.

@aleve99
Copy link

aleve99 commented Dec 19, 2021

Yes also all internal functions use the algod client and not possibilty to swap to the indexer. As algoexploer is dismissing the algod apis should be changed something. Indexer returns the response inside a key, like {'accounts': ...}, so the current tinymanClient is not compaitble with indexer

@gokselcoban
Copy link
Contributor

Hi, thank you for reporting this. I think this issue has been addressed with this PR #29 . So, I want to close this issue, please feel free to reopen it if you disagree.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants