Posts Tagged: response

Best Practices for API Error Handling

Best Practices for API Error Handling

Error codes are almost the last thing that you want to see in an API response. Generally speaking, it means one of two things — something was so wrong in your request or your handling that the API simply couldn’t parse the passed data, or the API itself has so many problems that even the most well-formed request is going to fail. Read more

Weighing the Pros and Cons of API Chaining

From the very beginning, developers have sought to make their systems run more efficiently, delivering greater amounts of data and functionality in a slimmer, more useful methodology. Increased efficiency usually equates to money saved, so there is a very real drive behind the constant need for condensing and code tweaking. Read more

Accumulating Feedback: 4 Questions API Providers Need to Ask Their Users

American activist Bryant H. McGill once said, “one of the most sincere forms of respect is actually listening to what another has to say.” For API providers, listening to the average user, accepting feedback, ingesting these experiences, and iterating on this information is a powerful exercise. Read more

20+ Emotion Recognition APIs That Will Leave You Impressed, and Concerned

If businesses could sense emotion using tech at all times, they could capitalize on it to sell to the consumer in the opportune moment. Sound like 1984? The truth is that it’s not that far from reality. Machine emotional intelligence is a burgeoning frontier that could have huge consequences in not only advertising, but in new startups, healthcare, wearables, education, and more. Read more