Steem API Explorer

in #steem8 years ago

Steem API Explorer is a tool for testing Steem API calls. It is useful for developers but also for people who just want to see the raw blockchain data.

Usage

Select what method you want to call and get a set of changeable parameters. The result can be viewed either as formatted JSON, raw JSON or expandable tree.

Errors

Errors are output explicitly and can be tracked to the the relevant API method in Steem, for example database_api::get_account_references as shown below.

Examples

Get this post
Get account lantto
Get trending categories
Get number of Steem accounts
Get pending Steem Dollar to Steem conversions for lantto
Get blockchain config
Get blockchain variables such as total supply and latest block number
Get block number 3963025
Get account creation fee
Get witness roadscape

Tips

  • Use the arrow keys to quickly browse methods and see what parameters they take.
  • Your last query is contained in the URL in case you want to share it.

Issues

  • get_account_references is not working due to this.
  • get_best_categories, get_active_categories and get_recent_categories seem unused if you look at this and will always return empty results. get_trending_categories works though.
  • For get_transaction and get_witnesses I haven't figured out what input they require. If anyone knows please give me a shout!

TODO

  • Add the remaining methods
  • Add loading spinner for slow methods
  • Description of parameters
  • Sortable table view for list results

Built with

Feedback

I would love to hear your feedback as I'm sure there are many ways to improve this.


steemroll.io/api-explorer


If you like my tools, please give me a follow! @lantto

Sort:  

I like it .. no more curl just to see some data from the API! Good Job!

Man, this is huge. Which node does it use underneath? Yours? I hope such node can survive traffic and last forever :) This one, this.piston etc. Getting SBD for such work could secure finances for maintaining hardware and developing software. Great work, thank you.

Thanks a lot! I'm using https://steem.ws/ so the traffic is load-balanced between several nodes. We should definitely support @xeroc and @jesta who provide it.

Great, @lantto answering you question about get_transaction, you put transaction tx as input, it works already:
http://steemroll.io/api-explorer/#method=get_transaction&params=["cd378a9da6f087f40c8baeb3e533ed09cea7dabe"]
this gives data of transaction you used to create this article
https://steemd.com/tx/cd378a9da6f087f40c8baeb3e533ed09cea7dabe

Thank you! I need to go through the API and see what endpoints expose this ID and add it as documentation in the next version. Thanks again. :)

Hello lantto, we would like to inform you that you have been chosen as a featured author by the @robinhoodwhale initiave. We are currently in alpha testing, if you would like more info join robinhood chat on steemit.chat or pm @repholder.

Nice Tool - Keep on Steeming!

I saw you said Description of parameters, but if you added full information about each method, what is was for, as well as the parameters... this could turn into the goto source for API documentation.

We could also use one for wallet commands ;)

Thank you! That's a great idea and definitely something I should add in the next version. Right now some methods are pretty confusing.

Yeah, wallet commands through RPC is something I'm currently digging into (for another project) so we'll see what happens. :)

I like this!

This will make it a lot easier to find related posts.

I actually made a post about it; no links to related posts on the pages, and this kind of solves that ... I like it!

And it's good for SEO!

Steemit took of like a rocket in Google

and those extra link-backs will make it even better!

Wow! This was something I had totally wanted! Haha =D

Great work! I follow for you.

Thank you!

Wow, good job. I love how this community of developers is coming together.

now I can migrate my toys from the python console to the web :) great job!

That's cool. Let me know if you have any questions. :)

Hi, some error :(
ERR_EMPTY_RESPONSE