The Latest News On The API Economy
Searching: No Search Term , Filtered By Article Type: "How To Elsewhere on the Web"
GraphQL is seen by some as the beginning of the end for RESTful APIs. GraphQL lets you get all the data you want in the way you want from an API while only ever calling one endpoint. But where to get started? Scott Domes over at MuseFind will take you from zero to hero in only twenty minutes.
In this tutorial, you’ll learn how to build a Shopify app from scratch with Node. You’ll learn how to request an access token from a shop and then make an API call. First, you’ll need to create a public HTTPS address for the purposes of authentication.
API documentation, as we all know, is rarely comprehensive and almost never up-to-date. An alternative way to get to know an API is by intercepting API calls from a mobile app and examining how they work. Here Jan Schwoebel over at his blog will show you how you can easily do that for iOS apps.
In this, developer-blogger Alex Kras shows us how to overcome the 60 second audio file limitation of the free tier of Google's Cloud Speech API by taking a longer audio file, breaking it up into short chunks, and then cycling through those chunks to make a complete transcription.
GraphQL was created by Facebook to solve nagging issues with RESTful APIs like having to make multiple roundtrips to the server to fetch required data. Tech titans like GitHub and Shopify are already using it in production but many businesses have yet to take the leap.
In this Microsoft tutorial the contributors share the steps for building a bot with their SDK and testing it with the Framework Emulator. Initially, you will need to install Node.js, create a folder for your bot, form a command prompt, and run the npm command nodejs npm init.
Would you like to add a photo gallery to an application with the help of Vue.JS framework? It could be useful to showcase products, demonstrate what a service can do for the users, or serve as a call to action. Vue.JS framework facilitates building user interfaces on the web.
GraphQL, the Facebook-backed open source tech, is making waves across the internet right now. Some people claim it’s going to revolutionise API design and leave REST in the dust. But what is it exactly and why the fuss? James Governor over at Redmonk explains.
A hypermedia API is an API that contains links in the responses. In this tutorial, you’ll learn what such an API looks like and why you might want to create one. Ismael Celis over at Thoughtbot will take you thru building a generic Ruby client written according to Hypermedia design patterns.
OAuth Newbies can find it tricky initially. In this tutorial you’ll learn how to get started with OAuth 2.0 while avoiding all the fiddly parts around handling tokens. The folks over at Insomnia will show you how to authenticate an API client for the GitHub API with OAuth 2.0 and the Insomnia app.
Microservices are all the rage these days but accessing data from multiple microservices can be a drag. In this tutorial, you’ll learn how to use GraphQL to make fetching and manipulating data from multiple sources easy as pie. Chris Anderson over at the Fauna blog will show you how.
A few years ago the best computer vision algorithms were the preserve of a few neural net researchers. Now, anyone can gain access to the best object detection algorithms in the world through public APIs. Wayne Walls, CTO at Filestack, put four of the best through their paces over at their blog.
Often API responses give you way more data than you ever wanted. Normally this isn’t a problem but sometimes you’d really rather receive just the fields you want in the payload to avoid putting strain on your app. Wesley Chun shows you how to do exactly that with Google APIs and field masks.
If you've ever used CodePen to prototype your own web apps or to closely inspect and fork someone else's code, then you know that one thing CodePen can't do is hide the API keys of any APIs that your app consumes in the process of doing whatever your app does. But now, there's a workaround.
‘Move fast and break things’ might be a good philosophy for web app development but it’s not so simple with API design. Client apps rely on your APIs. You can’t just release a radical new version every few months that breaks all previous integrations.
Want to track your pizza’s progress in real-time? Now you can with Pusher’s real-time APIs and Google Maps. In this tutorial, the guys over at the Pusher blog show you how to build your own food delivery-tracking web app hosted on Heroku.
Working with your API in a test environment can be a pain. Generating fake calls to test the API can require manually fiddling with things like urls, causing errors and frustration. Tom Wright over at his blog thinks he’s found the solution.
You need good API docs if devs are going to have success with their integrations. Just as importantly, your docs are also like marketing material. If on first reading, the prospective user doesn’t understand how your product works or thinks it would be a nightmare to integrate, you’re in trouble.
APIs need to be reliable and available and this can be put in question when there are sudden, unexpected increases in traffic. One way to ward off this danger is to use rate limiting. Paul Tarjan over at the Stripe blog takes you through the various types of rate limiting, when to use them and why.
Microservices promise much greater scalability than standard monolithic apps, but there’s always a catch. In the case of microservices it’s that managing security is more complicated. Scott Matteson sat down with Owen Garrett to learn more about microservices and its security best practices.