As we inch closer to the end of the week it’s time to bring you a review of the stories we couldn’t cover with a look at what what going on in the world of APIs. For those yearning for a little competition, the Real Estate Standards Organization (RESO) announced the 2017 RESO DataComp, its first-ever data competition will begin on September 17. The goal of the challenge is for developers to use an API that is compliant with the RESO Web API v1.0.2 standard to build a solution that can revolutionize real estate through data. Submissions can include technologies including but not limited to mobile, web, VR, AR, device, hardware, and drone. An interesting component of the competition is that it takes place over a month as opposed to a weekend long hackathon. There will be $25,000 in prize money with the overall winner receiving $10,000.
The Global Digital Asset Exchange (GDAX) announced a new Streaming API to allow for monitoring of real time market data. Until now, GDAX had only provided a full data feed that required high bandwidth and didn’t allow for filtered views of market data. The Streaming API allows users to: subscribe to a ticker channel to receive real time pricing data, connect to a level2 channel to maintain a copy of the order book, and join the user channel to listen to messages related to an individual account. Interested developers can check out the documentation.
Lastly comes news that SlashDB has announced an update to their API that turns relational databases into RESTful APIs. The release, version 0.9.51, now allows users to filter by multiple values when making data requests. This allows for single queries to do what previously required multiple queries without having to resort to SQL statements. For example, if you want to search for all artists with names beginning with A or B, and you want the data returned as JSON, you can use the following call
curl -H "Accept:application/json" http://demo.slashdb.com/db/Chinook/Artist/Name/A*,B*Other features of the update include full live synchronization between processes and nodes so that an API service can scale as traffic to it grows, new documentation and more.