The WAX blockchain technology powering our platform has a lot of extra benefits that aren’t immediately apparent. By writing all our book catalog data into a public ledger it means anybody can utilize already existing blockchain explorer APIs to access that data.
Using these APIs can allow you to embed links to your books or profile, filter collections by tags or attribute, and even track third party sales data. In other words, by using chainletter.io you get all the benefits of creating assets on the WAX Blockchain without all the hassle!
View the demo on Glitch!
https://chainletter-public-api-1.glitch.me
Prerequisites
Basic understanding of html, css, and javascript including the jQuery library.
Familiarity with web REST APIs
Do you have an API I can use on my own website?
Yes! We do not gatekeep a custom API and you can use the dozens of publicly available ones to get all the data about all your books.
While it might seem like the Third-Party API is missing a lot of data access functions, that’s by design. All that stuff already exists and is ready to use right now!
What about the cover images?
All images returned from Chainletter.io assets are compatible IPFS hash codes. This means you can use one of any number of IPFS image service gateways to download or display the images on your website. Since IPFS doesn’t automatically scale these images, it’s recommended you implement your own image cache system (resizer gateway.)
Chainletter.io is built using Filebase.com as our IPFS provider. See the code demo for an example of how to embed the images without caching them.
Public AtomicAssets APIs
AtomicAssets.io API – https://wax.api.atomicassets.io/docs/
Blokcrafters – https://wax.blokcrafters.io/docs/
You can always try to find more on this list… https://validate.eosnation.io/wax/reports/endpoints.html