Bitrix24, an enterprise collaboration, project management and social network platform provider, has announced the launch of its Bitrix24 REST API, which provides developers programmatic access to the cloud version of the Bitrix24 platform.
2014 is already turning out to be a great year for BigML.
Late last month, ProgrammableWeb reported on the second annual Hackomotive competition presented by Edmunds.com. The annual three-day event brings together automakers, developers, and others in the automotive industry to develop new products that deliver a better car shopping experience. The winners of the 2014 Hackomotive contest have been announced, and Carcode.me, a Seattle company, took the top prize.
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.
In some of my more recent posts, I have written about upcoming transformations within the API space, ranging from orchestration layers to how Netflix pursued an optimized API design for the 1,000-plus device types that it supports. In this post, I will provide more context for these decisions and how they may (or, perhaps more likely, will) apply to your API designs–especially when it comes to the benefits of the separation-of-design model.
With a leadership team that has worked with enterprise customers in the past, raw engineering’s new built.io believes that it is well-positioned to take on the burgeoning enterprise MBaaS market. COO Matthew Baier and CTO and Founder Nishant Patel told ProgrammableWeb why interest in the built.io API was so high amongst attendees at the recent DeveloperWeek conference.
Facebook’s $19 billion acquisition of cross-platform messaging service WhatsApp was obviously a boon for WhatsApp’s founders, employees and investors, but it also proved to be a good thing for several of WhatsApp’s biggest competitors.
Big data analytics company Riskpulse has exclusively informed ProgrammableWeb about the launch of the Sense API, aimed at helping start-ups, innovators, data analysts, and new tech product makers to monetize the data they might be collecting. Matthew Wensing, CEO and cofounder, tells us how third-party developers can partner with Riskpulse, using the Sense API to commercialize risk assessment-related data.
Almost 12 years ago, Roy Fielding introduced Representational State Transfer (REST) in his dissertation on Architectural Styles and the Design of Network-based Software Architectures. Since then, APIs adopting the REST architectural style (so-called “RESTful” APIs) have gradually increased in popularity. Nonetheless, a key constraint that Fielding proposed has yet to be adopted as a mainstream feature of RESTful APIs. This feature is known as Hypermedia as the Engine of Application State, or HATEOAS. APIs that enforce this constraint are referred to as HATEOAS-compliant APIs. More generally, APIs that adopt the characteristics of HATEOAS are called “Hypermedia APIs.”