Select Page

Category: API

So you need to parse an email?

Say you have a website with users who have accounts. Those users email you sometimes. What if you could parse that email for more context about that user, their account, and what they might want? There are email parsing services out there. For example, Zapier offers Parser, which is free, with the idea being that you use Zapier itself to interconnect that data with other apps. You teach it about your emails and then get programatic access to those data bits. mailparser.io is another service just for this. Same deal, you send the emails to them, and from within...

Read More

Creating a Static API from a Repository

When I first started building websites, the proposition was quite basic: take content, which may or may not be stored in some form of database, and deliver it to people’s browsers as HTML pages. Over the years, countless products used that simple model to offer all-in-one solutions for content management and delivery on the web. Fast-forward a decade or so and developers are presented with a very different reality. With such a vast landscape of devices consuming digital content, it’s now imperative to consider how content can be delivered not only to web browsers, but also to native mobile applications, IoT devices, and other mediums yet to come. Even within the realms of the web browser, things have also changed: client-side applications are becoming more and more ubiquitous, with challenges to content delivery that didn’t exist in traditional server-rendered pages. The answer to these challenges almost invariably involves creating an API — a way of exposing data in such a way that it can be requested and manipulated by virtually any type of system, regardless of its underlying technology stack. Content represented in a universal format like JSON is fairly easy to pass around, from a mobile app to a server, from the server to a client-side application and pretty much anything else. Embracing this API paradigm comes with its own set of challenges. Designing, building and deploying an...

Read More

Build a To-Do API With Node, Express, and MongoDB

API stands for Application Programming Interface. APIs allow the creation of an application to access features of an application or service. Building APIs with Node is very easy. Yes, you heard me right! In this tutorial, you will be building a To-Do API. After you are done here, you can go ahead to build a front end that consumes the API, or you could even make a mobile application. Whichever you prefer, it is completely fine. Application Setup To follow this tutorial, you must have Node and NPM installed on your machine. Mac users can make use of the command below to install Node. brew install node Windows users can hop over to the Node.js download page to download the Node installer. Ubuntu users can use the commands below: curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash - sudo apt-get install -y nodejs To show that you have Node installed open your terminal and run node -v. You should get a prompt telling you the version of Node you have installed. You do not have not install NPM; it comes with Node. To prove that, run npm -v from your terminal and you will see the version you have installed. Now go and create a directory where you will be working from, and navigate into it. mkdir node-todo-api cd node-todo-api Initialize npm in the current working directory by running: npm init...

Read More
www.000webhost.com