API Digest #77. Are your web and mobile APIs putting your business at risk?

11 September 2017 |

api business risk

Greetings from API2Cart! We are glad to welcome you at our regular fortnight API digest. We’ve collected the most interesting materials regarding API technologies and business from all around the internet:

  • The best developer experience KPIs
  • From customer self-service portals to web APIs
  • API design fundamentals: analytics or it didn’t happen
  • Designing API usage guidelines for bot clients
  • Want to create better API documentation? Ask questions
  • Are your web and mobile APIs putting your business at risk?
  • Understand your API customer — why you should embrace early adopters
  • Why microservices succeed in app integration where web services stumbled
 

Leaving all the productivity and success instructions aside, control has always been one of four major management functions which are meant to help the work to be done effectively. Thus, KPIs are not only measuring the current results but also help to distinguish the areas of growth. Jenny Wanger, a product manager at Arity, is sharing her observations concerning four potential domains of responsibilities and KPIs for web developer in the article The best Developer Experience KPIs.

A video presentation From customer self-service portals to web APIs by Florian Marquardt presents how Regiocom has created and uses web APIs to serve the energy market in several countries.

The role of analytics in designing APIs has been discussed by Diogo Lucas. He is giving an overview of the usage and performance monitoring and tracing calls in the article API design fundamentals: analytics or it didn’t happen. Continuing the designing APIs topic, a specifically tailored for bot clients material was published by Kristopher Sandoval, Designing API Usage Guidelines For Bot Clients. Bots are a really hot topic this year as you may have noticed, so if you are interested in learning more, read our article Why Chatbots are Poised for Growth in eCommerce as well.

Documentation is typically a weak point when it comes to API development, so it is never too much information concerning that. Today we suggest the blog post by James Higginbotham Want to create better API documentation? Ask questions. A very interesting approach in the form of popular these days coaching style. The author provides us with three major questions we have to ask ourselves in order to make a complete API documentation.

Another valuable article submitted by James Higginbotham is Are your web and mobile APIs putting your business at risk?. A well-structured article defines five realistic scenarios when your company may get in danger because of mobile APIs and provides smart solutions to each.

Jarkko Moilanen has posted a fine material Understand your API customer — why you should embrace early adopters. It is nothing else but a lesson in economics about client segmentation. An article will bring you the very best recommendations concerning early adopters.

The last article of today’s edition is Why microservices succeed in app integration where web services stumbled. It was written by Alex Handy, technology journalist, and starts with ‘Integrations aren’t sexy, but…’ Intrigued? Click to check it out.

If you are interested in getting latest news in the API world, check our digest #75 and 76 as well as stay tuned with the new blog posts.

P.S. In case you are interested in trying API2Cart, you can create an account and see how the API works on live stores.