bitshares-explorer-api
bitshares-explorer-api copied to clipboard
bitshares
REST API for BitShares
Get volume data from more reasonable fields. By the way, since `get_markets` API is used by `get_most_active_markets` and volume of different assets gets added up, there might still be issues.
The only API node which works at this moment is https://api.bitshares.ws . This issue is follow-up of https://github.com/bitshares/bitshares-explorer-api/pull/74.
Hi. Could you please fix explorer api? https://explorer.bitshares-kibana.info/
When using /get_account_history sometimes `entry['operation_history']['op_object']` is null (`None`), I got this only on ES wrapper v2. Example: `curl -X GET --header 'Accept: application/json' 'https://wrapper.elasticsearch.bitshares.ws/get_single_operation?operation_id=1.11.1000908945'`
The UI would like to have the possibility to view historic feed price. If not mistaken, haven't tested though, es_objects does store feed price. Relevant code bits are - https://github.com/bitshares/bitshares-core/blob/cdc2db30c2f06aaddbfda965ee270b99dc24e0aa/libraries/plugins/es_objects/es_objects.cpp#L307...
In the Swagger YAML files, response `schema` specs are not given. For example, for `/account_name`: https://github.com/bitshares/bitshares-explorer-api/blob/9444323252b429fc6b2d9ac2781a05d2f7004c19/swagger/paths_explorer.yaml#L33-L51 In `responses`, it gives only `description` for each status code. The `schema` spec (https://swagger.io/docs/specification/2-0/describing-responses/)...
`most_active_markets` returns 100 market pairs. Sometimes less are needed, for example just the top 10. As we are here we maybe add pagination too.
- add `start` and `limit` parameters to `/top_proxy` - add `/proxy_count` - parallelize ES accounts retrieval
We can have an API to get all operations in a block, including virtual operations. See discussion in https://github.com/bitshares/bitshares-core/issues/243 and https://github.com/bitshares/bitshares-core/pull/1899. IMHO not a priority.