A Few Great Ways to Consume RESTful APIs in C#

ICYDK: By doing web development, you find yourself in the need to deal with external APIs (Application Programming Interface) sooner or later. In this article, my goal is to make the most comprehensive list of ways to consume RESTful APIs in your C# projects and show you how to do that with some simple examples. After reading the article, you will have more insight into which options are available to you and how to choose the right one next time you need to consume a RESTful API.

What Is a RESTful API?

So, before we start, you might be wondering what does API stand for, and what is the RESTful part all about? https://goo.gl/CJvnKx #DataIntegration #ML

Nexmo Manages Their OpenAPI 3.0 Definition Using GitHub

I’m big on supporting API providers that publish their OpenAPI definitions to GitHub. It is important for the wider API community that ALL API definitions are machine-readable and available in a way that can be forked and integrated into continuous integration pipelines. I’m not even talking about the benefits to the API providers when it comes to managing their own API lifecycle. I’m just focusing on the benefits to API consumers, and helping to make onboarding, integration, and keeping in sync with the roadmap as frictionless as possible.

To help incentivize API providers doing this, I’m committed to writing up stories for each API provider that publishes their OpenAPI, APIs.json, or Postman Collections to GitHub. Bonus points if you are doing it in an interesting way that further benefits your operations, as well as your community. Today’s API provider to showcase is the SMS, voice and phone verifications API provider Nexmo, who tweeted the GitHub repository at me, which contains their OpenAPI definition for their APIs. As they say, it is a work in progress, but it provides a damn good start for a machine-readable definition for their API(s), and I mean c’mon, aren’t all of our APIs a work in progress? https://goo.gl/R6C3MQ #DataIntegration #ML