API Digest #59: Leveraging Machine Learning for API Error Handling

16 August 2017 |

api digest

Welcome back to our API Digest series. This time, we are covering the following articles:

  • API error handling using Machine learning
  • The future of front-end development
  • Why APIs need to be both machine and developer friendly
  • Why this CEO pumped the brakes on growth before stepping on the gas
  • Why you should be measuring time to utility for your product
  • Assembling the API management Jigsaw in big (and small) companies
  • Ultimate guide to 30+ API documentation solutions

Machine learning is a very in depth technology that, if used right, can be beneficial in a lot of ways, many of which are yet to be discovered. And now Steven Cooper tells how to leverage machine learning for API error handling.

Should we make our kids learn to code? This question, posed to Carson Miller at a dinner party, incited him to reflect on it and share his thoughts and conclusions the article “The future of front-end development is design”.

Creating a positive developer experience may seem like the easiest goal ever, but it is not. Taija Björklund has explained why APIs need to be both machine and developer friendly, and how to nail developer experience if you own an API product.

Drew Hansen has told the story of SendGrid’s growth and a big shift regarding recruiting they commenced. For details, read “Why this CEO pumped the brakes on growth before stepping on the gas”.

“Do you measure your product's time to utility? If not, you should. The best products reward users as quickly as possible after installation and account creation.” - Tomasz Tunguz states in his article “Why you should be measuring time to utility for your product”.

On example of Josh Wang’s experience with implementing an API management solution, Art Anthony has explained what it takes to implement a new process in a big company. Read about it in the article “Assembling the API management Jigsaw in big (and small) companies”.

Say you have developed a web API and now you want to show it to the world. Next comes documentation, and there’s a tool for that. But, in the sea of API documentation generation tools, which one is suitable to your specific environment? Bill Doerrfeld has written the ultimate guide to 30+ API documentation solutions to help you decide which one to choose.

For more API news and insights, read API developer weekly #140 by Keith Casey and James Higginbotham.

See you in a fortnight! In the meanwhile, send us article suggestions and ideas. Either way, we are happy to hear from you. :)

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