subscan-explorer / subscan-issue-tracker

The issue tracker for Subscan.io.
3 stars 5 forks source link

Price endpoint validity #37

Closed YakirMo closed 1 year ago

YakirMo commented 1 year ago

Confirmation

Affected Network(s)

All networks

Steps to reproduce

It seems like the Historical price query endpoint doesn't work properly for any of the networks. Run this endpoint with any time on any network:

curl -X POST 'https://polkadot.api.subscan.io/api/open/price' \ --header 'Content-Type: application/json' \ --header 'X-API-Key: YOUR_KEY' \ --data-raw '{ "time": 1665107 }'

Expected output

Expected to get price of networks' tokens (per api call).

Actual output

Either "429 Too Many Requests" or Success without data.

Additional factoids or references

No response

freehere107 commented 1 year ago

@YakirMo HTTP 429 meaning you API usage exceeds the limit

YakirMo commented 1 year ago

@freehere107 What about getting the 'success' response without the data? It happens for most of the 'price' endpoints of networks. Example response for HydraDX and Kusama price endpoint: { "code": 10004, "message": "Record Not Found", "generated_at": 1665557426 }