CoinAPI provides data on request limits, exchanges used in aggregation of OHLCV data, and possibly more that I'm not aware of in the response headers. As far as I can see, the response header is currently neither parsed nor stored. I think it would be good to capture that information, either by parsing it for the relevant request or by just giving the CoinAPIv1 class an attribute response_header and leaving it to the user to parse it. I have only looked at the Python SDK, but I imagine the other languages are similar.
Do you think this makes sense generally and one of the implementations above specifically? If so, I'm happy to make a PR for the Python SDK.
CoinAPI provides data on request limits, exchanges used in aggregation of OHLCV data, and possibly more that I'm not aware of in the response headers. As far as I can see, the response header is currently neither parsed nor stored. I think it would be good to capture that information, either by parsing it for the relevant request or by just giving the
CoinAPIv1class an attributeresponse_headerand leaving it to the user to parse it. I have only looked at the Python SDK, but I imagine the other languages are similar.Do you think this makes sense generally and one of the implementations above specifically? If so, I'm happy to make a PR for the Python SDK.