You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
adding all available get requests to the python client #2
api_items = [ {"assets": "https://api.glassnode.com/v2/metrics/endpoints"}, {"futures": ["https://api.glassnode.com/v1/metrics/derivatives/futures_volume_daily_latest", "https://api.glassnode.com/v1/metrics/derivatives/futures_volume_daily_all_sum", "https://api.glassnode.com/v1/metrics/derivatives/futures_open_interest_latest", "https://api.glassnode.com/v1/metrics/derivatives/futures_open_interest_all_sum", "https://api.glassnode.com/v1/metrics/derivatives/futures_open_interest_perpetual_sum", "https://api.glassnode.com/v1/metrics/derivatives/futures_funding_rate_perpetual" ]}] ###
would this be a good way to structure usable api requests
@L-47 Have a look at my forked repository. I made the API client object-oriented, thus no need to lookup endpoints, which to me is more developer-friendly and suits Python's OO nature better.
i think it's a good idea to add all the metrics inside the repo so that you can call metrics just from a variable.
an idea for ease of use