If you are a regular user of chat apps like Slack or Telegram you may have seen the increase of “bots” available on each platform. Bots? Yes! Like in the old times of IRC. But this time they’re supposed to be smarter. And it’s supposed to be easier for developers to build their own bots. Some people predict that 2016 will be the year of bots, with companies building bots instead of applications. That will change the way we consume information and the way we interact with applications. You can already see that with Birdly, a Slack bot that gathers data about your customers from different services like Salesforce and Mixpanel. Another example is Ottspott, a Slack bot that lets you receive calls directly into Slack. If you’re interested in learning more about this trend and what’s happening with bots, you should check out this announcement…
From the buzz on Twitter and blog posts, you could feel that ECMAScript 6 was finally coming. It has many things we’ve wished for for years, so it makes sense to start new projects with it in mind.
Others have written in depth about various ECMAScript 6 features. I’d like to focus just on one: module loading. There is no common way to load your ES6 modules natively in the browsers. For example babel, has support for three different module loaders. There was a
System dynamic module loader included in the ES6 specification, but in the end it was removed and work continued as WhatWG loader spec. Yes, you can define modules, classes, export them, and import them, but there is no way how to load them across files. This also means that the
Developer experience (DX) is about more than having a well designed API – it’s the packaging and delivery of the API, which are key to ensuring it gets adopted by developers.
This is the seventh part of the Building Effective API Programs blog post series. In the previous parts we covered benefits of APIs, alignment between API programs, strategy and business models, API design and implementation, and API operations. In this part, we discuss aspects of how to market your APIs.
API marketing is often see…
Exposing assets (data or services) via APIs can prove to be extremely valuable for an organization. However in most cases, it’s not enough to solve only the technical challenges of opening an API. It can even be counterproductive for the organization if the API does not contribute to the overarching business strategy, if no one knows about it, or if no one adopts it. A well-thought-out API program that surrounds the technical API is paramount.
This is the first part of the Building Effective API Programs blog series. This series is part of a larger collection of ebooks and articles, with which we aim to support decision making and help readers establish successful API-based products.
- The article “What is an API? Your Guide to the Internet Business (R)evolution” gives a general introduction and definition of…
This year at the API Strategy & Practice Conference (APIStrat) in Chicago (Sept. 24–26) we are trying something new – the API Speed Hack.
What is it?
Think of the Speed Hack as a “performance enhanced” hackathon. We think it’s a very effective, practical and fun way to promote APIs to developers.
VisionMobile’s Developer Economics Report 2014/Q3
In an earlier post, we announced that we had teamed up with VisionMobile as media partner for their 7th global survey for the Developer Economics Report 2014/Q3. We are very happy to announce that the final report is now available.
Developer Economics is the leading research program on mobile developers and the app economy, tracking developer experiences across platforms, revenues, apps, tools, APIs, segments and regions.
Based on a survey of 10,000+ app developers, the …
APIdays is a global tour covering six cities including Barcelona, Berlin, Moscow, Paris, San Francisco and Tokyo. The API’s & The Future of Software series is vendor-independent and genuinely wants to drive to API space forward, covering a wide range of topics including scalability, versioning, developer experience, testing, mobile, security and business models. We are proud to support the whole APIdays series as one of the main sponsors.
For the Berlin edition there are already 50 speakers in two tracks, and over 250 attendees are expected. APIdays Berlin is solely focused on the builders of the web. The goal is to provide a great learning experience and an open forum to bring together the finest minds in the API space and foster dialogue. For a complete overview of the agenda for APIdays Berlin
We are very happy to be official partner of the DevLab LIVE event in London on May 9 – 11, 2014, whose goal is to bring together developers and brands. As such we are happy to provide 5 free passes – first come, first served. To claim a pass please get in touch with me directly via twitter @ManfredBo.
Connecting bright minds with big brands
DevLab LIVE is a new 3-day event bringing innovators from the startup, digital and developer com…
- The App developer (consumer of the API) gets its client_id and client_secret via the buyer portal (in case of oAuth v1 would be consumer_key, etc.). These keys get provisioned after the account is validated, or by the provider through their portal, or via the Account API (e.g. Legacy systems or buyer portals not based on 3scale’s).
- The App developer does the requests to the API as per standard oAuth, any library is supported since he knows its client_id and client_secret. Regardless if it’s a call to the API or or the GetAccessToken the client_id is always sent to the API provider (even once the access_token has been granted). The request is signed with his client_secret.
The API provider calls 3scale’s backend with the client_id from the …