The initial buzz at drinks for the end of day one of API Strategy and Practice was: “Our minds have been blown.” The audience response is evident from three talks yesterday at API Strategy and Practice in Amsterdam. Presentations aimed at developers moved from a global rethink of what coding actually is (Mike Amundsen) to how to think and manage APIs as the core unit in distributed systems (John Sheehan) to a best practice daily toolkit for developers writing code and integrating APIs (Bruno Pedro).
Of all the markets being impacted by the booming API economy, perhaps none has seen as much activity and innovation as the payments space. The past several years have seen the launch of a number of disruptive and successful API-centric upstarts, including Stripe and Balanced. Meanwhile, entrenched players like PayPal and Verifone have responded with new offerings of their own.
There are major advantages to today’s applications being built atop APIs. If you’re reading ProgrammableWeb, there’s a good chance you know all about integrating with other services. The major disadvantage of modern distributed architecture is pretty obvious—someone else’s service could go down and it’s outside of your control. You might not even know a service is down, which is why many top API providers are now making status pages available. These sites help communicate to developers when anything is amiss with the API.
ProgrammableWeb’s Editor-in-chief David Berlind moderated a lively panel session at the recent DeveloperWeek conference in San Francisco. The panel included industry thought leaders Jason Harmon from PayPal, Jeremiah Lee Cohick (Fitbit), Alex Salazar (Stormpath), Uri Sarid from MuleSoft (the parent company of ProgrammableWeb) and John Musser, founder of both ProgrammableWeb and API Science. In an hour-long panel on “emergent APIs,” panelists covered API design, SDKs versus APIs and the challenge of API versioning. Bonus points: Each shared their number one piece advice for developers in businesses charged with creating their first API.
Street Repairs API makes service of spotting problems easy, popular. AdStage launches platform API. Plus: API design tooling, SeriousBit launches NetBalancer, and 5 new APIs.
AeroFS launches auditing and content API. Put your API through its paces at the API testing Dojo. Plus: Sign up for Paypal research, having fun with the Marvel Comics API, and 8 new APIs.
AeroFS Auditing and Content API Launch
AeroFS, the company that provides cloud services yet keeps your files on your servers, has launched an [...]
Yesterday, Stripe launched its third version of Capture the Flag (CTF3). The first two editions of CTF were purely focused on security issues that developers face in the real world. Stripe has expanded the scope this time around. PW caught up to Stripe Engineer and CTF co-founder, Siddarth Chandrasekaran, to learn more about CTF.
Paymate launches an API to take on Square down under. Algolia revs up search with new real-time API. Plus: Stripe CTF3 coming soon, WSO2 has an upcoming seminar on secure API management, and 21 new APIs.
How an API was designed and implemented is usually of little interest to consumers of the thousands of APIs available today. What matters most is that an API works, is easy to integrate and solves a real problem. But for the growing number of companies looking to take advantage of the booming API economy and considering developing APIs, design is an important subject.
Rainforest, QA solution provider, uses the power of humans to test website quality. The Rainforest API allows developers to programmatically trigger the execution of tests. Rainforest finds that nothing tests a user interface like a good old-fashioned human being. Thus, users set up tests in plain English and Rainforest takes the customer through the steps of the tests.