Digital Asset Supply Data Collection for Upbit Exchange

[blocks8]

Is your feature request related to a problem? Please describe.
We received a notice from Upbit Operations Team via Project Communication project-comm@upbit.com that they require additional data API endpoints to support their STX listing. The request is outlined below. There is not a clear timeline for the request but it is stated as a required data pull for Upbit, an important exchange in Korea.

Describe the solution you'd like
We would like to fulfill the data API endpoints as outlined in detail below to specification.

Describe alternatives you've considered
We tried sending a static data pull but they requested end points. The data is available on Coin Market Cap as well but it does not suffice for Upbit, as they describe here:

"Unfortunately, we are requiring projects to provide us with an API link that we can utilize to put on our website's info tab.

As you can see in this link, STX has its own info tab and it has Market Cap & Circulating Supply information provided by CMC, CG and your team. We are currently missing information from your team and that is why we are requesting your assistance.

Please note that we only accept API links with the format that we requested. Let us know if you have any questions or concerns.

Additional context
Here is the full request from Upbit Operations Team. I've notified @diwakergupta about the request as well.

We received a notice from Upbit Operations Team via Project Communication project-comm@upbit.com that they require additional data API endpoints to support their STX listing. The request is outlined below:

--start email--
Hello, this is the Upbit Operations Team.

We are currently in the process of reinforcing the information tab for all digital assets supported by Upbit.
In order to provide more objective and accurate data, we would like to collect data from the project teams as well- apart from Coinmarketcap, Coingecko, etc.
We therefore would like to request token supply-related information in the format below.

IMPORTANT!!! - We WON'T be able to use custom format APIs, so PLEASE follow the given format below :

1. Protocol Format and Response Content

• HTTP(S) GET format
• Response Content-Type: application/json; charset=utf-8

2. Required Data Fields

• (Required) symbol : [String] Symbol (ex: BTC, ETH)
• (Required) currencyCode : [String] Fiat Currency (ex: KRW, USD, IDR, SGD, THB) Data for all 5 fiat currencies are required
• (Required) marketCap : [Decimal] (based on designated fiat currency) Market Cap
• (Required) circulatingSupply : [Decimal] Circulating Supply (Total no. of tokens available for trading)
• (Required) maxSupply : [Decimal] Max Supply
• (Required) provider : [String] Provider(Name of Entity) has to be identically appointed to the slug
• (Required) lastUpdatedTimestamp : [Long] Last Updated Unix Timestamp (Milliseconds since Unix Epoch)
• accTradePrice24h : [Decimal] (based on designated fiat currency) 24H Total Trading Volume
• price : [Decimal] (based on designated fiat currency) Global Coin Price

You may keep 'accTradePrice24h', 'price' data null at the moment, however, we would appreciate it if you have all the data ready in case we need additional information during the development process.

Reference: API JSON Response Example
example) GET /api/xxx/info

[
{
"symbol": "BTC",
"currencyCode": "KRW",
"price": 39296339.41959793,
"marketCap": 731119437172996.5,
"accTradePrice24h": 64801881977219.54,
"circulatingSupply": 18605431,
"maxSupply": 18605431,
"provider": "Your company",
"lastUpdatedTimestamp": 1611133137325
},
{
"symbol": "BTC",
"currencyCode": "SGD",
"price": 47217.20293252,
"marketCap": 878496411174.0282,
"accTradePrice24h": 77046842282.20059,
"circulatingSupply": 18605431,
"maxSupply": 18605431,
"provider": "Your company",
"lastUpdatedTimestamp": 1611133137325
}
// ... list by currency
]

--end email--

[zone117x]

Not yet clear if this makes sense to add to this repo. Should be put into icebox (where is that category now?)