
Welcome to Understanding APIs and RESTful APIs. This course is NOT about coding, so if you're trying to implement an API on your website, this course is not for you.
This course is for you if you are trying to understand how APIs and RESTful APIs work.
API = Application Programming Interface. It's not visual though, so it's kind of a misleading name. Let's learn more about this.
The slides that are referenced in this course can be found here (its a free Google Slide)
Technology comes with a lot of crazy terminology. Honestly, use computer geeks use big words to make ourselves feel smarter — but underneath all the crazy buzzwords is a very simple analogy that you can relate to as a human. You don't need to be a coder to get this one, I promise :)
Let's take a look at a real life example of a service that uses LOTS of APIs to make their website run.
Are APIs restricted by programming language? Watch to find out!
RESTful APIs are a form of API. It's a way of sending two commands at once to a server. Are we DELETING a user? And if so, which user?
JSON = JavaScript Object Notation. Again, a fancy acronym for "a fairly common and easy-to-read way to talk to other computers".
I'll show you how to make a simple GET request to a JSON-based RESTful API. You don't need to know JavaScript, though. This can be done in ANY language.
GET requests = you are GETting data from a server. No create, update, or delete operations. You simply want to see the data.
POST requests = you are CREATING data on a server. Ask the server to make a new resource, and it will.
DELETE requests = you are DELETING data from a server. Ask the server to delete a new resource, and it will.
PUT/PATCH requests = you are UPDATING data from a server. Ask the server to update a resource, or a piece of a resource, and it will.
How can you use an API? You need to "consume" it — a.k.a. you need to be able to reason JSON.
Requests and responses are how we ask for something, and receive something in return.
Status codes are numbers that tell you what went wrong, or what when right when asking the server for data.
APIs keys are your authentication credentials. It's like logging into a website, but with a randomly generated username and password.
A brief summary about what we learned in this course.
Resource that were mentioned in this course.
Questions? Comments? Feedback? IDEAS?! DID YOU HATE MY PRESENTATION STYLE?!?!
Let me know what you thought about this course. Was it helpful, or not? And where can I improve so my next course is much better?
In this course you will learn about APIs and RESTful APIs, and how they work. There is no coding in this course.
By the end of this course you will completely understand how APIs work, and how computers talk to each other. You'll also be familiar with RESTful APIs which make use of the HTTP protocol. If that sounded confusing, scary, or overly technical — it's not — it's just a fancy way of saying "it uses the internet".
The goal of this course is to help you understand APIs and RESTful APIs without needing to write any code. So next time someone says "API" you will know exactly what they are talking about (and you'll also know it's not really that technical or fancy, but that'll be our secret ;)
———
This course is designed to remove the sense of overwhelm and "scariness" when we start to talk about APIs. APIs and RESTful APIs come across as difficult or advanced subjects, but really it's just two computers talking to each other and exchanging commands and data. No different than when your friend sends you a text message, and you text back.
I'll give you several easy to remember metaphors so APIs don't feel scary or overwhelming, too.
APIs can be written and used by most programming languages, so we're not writing any code, although I do provide a live JavaScript demo.
All the slides will be provided for you, as well as reference material for when you've graduated this course and you're ready to take on the world of APIs.
———
This course is only 45 minutes, but I promise you that's all the time you'll need — not because I'm a good teacher, but because APIs are seriously that simple once someone takes the time to explain them.