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
The summary/fees/{protocol} endpoint has some inconsistencies that I believe should be improved. I have not checked this behavior against the other fees/revenue endpoints, so it may also apply to those.
https://api.llama.fi/summary/fees/ethereum?dataType=dailyFees and https://api.llama.fi/summary/fees/ethereum?dataType=dailyRevenue both work as I would expect, but for dataType=totalFees and dataType=totalRevenue configs, I get a response with both totalDataChart and totalDataChartBreakdown returning null values. Based on the data I see in the dashboard, this shouldn't be the case. For Lyra, dailyFees is the only config that produces non-null results.
Volume endpoints include excludeTotalDataChart and excludeTotalDataChartBreakdown flags. Given that volume and fees/revenue are given in the same format, I believe that the fees/revenue endpoints should include this same behavior even if it has virtually no effect on final usage of this data.
The text was updated successfully, but these errors were encountered:
The
summary/fees/{protocol}
endpoint has some inconsistencies that I believe should be improved. I have not checked this behavior against the other fees/revenue endpoints, so it may also apply to those.https://api.llama.fi/summary/fees/ethereum?dataType=dailyFees
andhttps://api.llama.fi/summary/fees/ethereum?dataType=dailyRevenue
both work as I would expect, but fordataType=totalFees
anddataType=totalRevenue
configs, I get a response with both totalDataChart and totalDataChartBreakdown returning null values. Based on the data I see in the dashboard, this shouldn't be the case. For Lyra,dailyFees
is the only config that produces non-null results.Volume endpoints include excludeTotalDataChart and excludeTotalDataChartBreakdown flags. Given that volume and fees/revenue are given in the same format, I believe that the fees/revenue endpoints should include this same behavior even if it has virtually no effect on final usage of this data.
The text was updated successfully, but these errors were encountered: