I've spent some time watching the #developers channel in the Splinterlands Discord servers and every so often someone comes in asking if there is any documentation. There's been a Google Docs spreadsheet (here) but I decided to expand this list with examples on GitHub.
https://github.com/kiokizz/Splinterlands-API
Example:
For those developing anything related to Splinterlands and would like to contribute feel free to make suggestions or corrections. Hopefully this will be of use to someone else considering building something in the Splinterlands sphere.
I intend to at some point to start documenting the games custom JSONs with JavaScript examples and will likely include them in this repository.
Enjoy the rest of your day :)
@kiokizz
This is really cool well done!
Wow, really useful!
👍
This is high quality work! Thanks for sharing this helpful documentation.
Thanks so much for posting this. I am new to making API calls, so this is very helpful and saves me so much time.
Your welcome. I haven't been actively updating the list of API calls, so if you think something needs to be added let me know :)
Hey I came across something very cool today, so I wanted to share with you. You might already know it. I had a use case where I needed data for in-game DEC transfers that were older than 30 days. Initially, i tried the API, but I think Matt limited this type of data for 30 days? Luckily, I was able to find the data on the hiveSQL database using [tid] = ('sm_token_transfer'). The best part was that the hiveSQL db is currently being funded so it is free to Hive members.
Hello. I have considered using it before. I've got a couple project ideas that would need it. Haven't actually much unallocated time since it became available free.
Only thing to consider is that some transactions Splinterlands wise have failed previously (rare - e.g page not updated from previous tx) or it could be duplicated. You can do an individual checkup tx with on the Splinterlands API with the tx ID though, and that goes back further than 30 days.
What were you working on?