DEV Community

Cover image for The Vonage Dev Discussion: Defining what an API is
Liz Acosta for Vonage Developers

Posted on

The Vonage Dev Discussion: Defining what an API is

This week we kicked off the first in a series of office hours. Our office hours are a judgment-free space for developers to come and ask questions about using Vonage – and get an answer live from an actual human!

Being able to ask questions without fear of judgment is so important for beginner engineers and being able to answer those questions is equally important for senior engineers. Have you ever noticed how explaining something makes you really think about what you actually know or don’t know? It's a really good feedback loop!

So here’s a chance to test your knowledge: How would you explain what an API is to someone? What are some examples of APIs you use?

A stylized robot with the questions: How would you explain what an API is to someone? What are some examples of APIs you use?

And if you’re new to APIs, here’s a walkthrough of how to use one from our office hours:

And don’t worry! If you run into any issues, we can help you out in our next office hours ♥️🤓

Let's keep the API conversation going in the comments below! 💻 👇

Top comments (1)

Collapse
 
lizzzzz profile image
Liz Acosta

One of the best ways I heard APIs explained was a comparison to an electrical wall socket. It abstracts away all the complexity of electricity and how electricity is delivered to you. All you have to do is plug in your electronics and as long as the plug is compatible, it will receive electricity. You don't need to understand all the complicated stuff in order to use it.