👽 APIs explained with aliens


Hi Reader,

today we are going to break down my favorite topic — APIs!

Why is this my favorite? Because I work with them daily as an integrations PM. So it better be!

I started this job with almost zero knowledge of how APIs work and a lot of fear :)

But it was worth it, because now I can break it down for you in very simple language — under 10 minutes.

If you’ve ever felt unsure about APIs, this one is for you.

Today in 10 minutes you will:

  • Understand what APIs actually are (with an alien twist)
  • Learn REST, GraphQL, and SOAP in simple words
  • Try testing them yourself
  • Bonus: see how to generate a REST API with AI

Why do you need to know about APIs?

Most modern products both use APIs and offer APIs to others.

  • If you have a web UI, it uses APIs.
  • If your system exchanges information with another, it uses APIs.
  • If you’re building internal tools, APIs enable integrations between apps.
  • If you’re building SaaS, customers will expect your APIs so they can build on top.

You don’t have to code them yourself.

But you do need to know how they work — otherwise, how can you design for customers and partners if you don’t understand the foundation?

APIs in simple words

API = Application Programming Interface.

Think of it as the language of applications.

APIs in alien language

Imagine Earth gets visited by friendly aliens.
They want to collaborate, trade, maybe share their advanced tech.

There’s just one problem — they don’t speak our language.
Not even hand gestures work.

So they hand us a guidebook of their language.

That guide is basically… an API.

It tells us:

  • What words mean
  • How to ask questions
  • What answers to expect

That’s exactly what APIs do for systems. They’re the translation layer between two worlds.

REST APIs – Alien common phrases page

The first page of the alien guidebook is common phrases.
That’s REST APIs.

  • REST uses simple, standard HTTP methods: GET, POST, PUT, DELETE.
  • Every piece of data has its own address (a URL).
  • Responses are usually neat and predictable (JSON).
  • The rules are consistent across systems.

Examples:

  • GET /alien/technology → “Show us your tech.”
  • PUT /alien/homeaddress → “Update alien homeaddress to Earth.”
  • POST /alien/recipes → “Share human recipes with aliens.”
  • DELETE /alien/cursewords → “Delete bad words from alien phrasebook.”

Want to test REST APIs in under 3 clicks and for free?
Try out a free Swagger Petstore UI — you can click “Try it out” and see how requests and responses work.

GraphQL – Alien custom translator headset

Now imagine instead of flipping through the guidebook, the aliens give you a translator headset.
You ask one custom question, and you get exactly what you asked for — no more, no less.

That’s GraphQL.

  • One single endpoint instead of many URLs.
  • You decide exactly which fields to return.
  • No “overfetching” (too much data) or “underfetching” (not enough).

Examples:

  • “Tell me alien recipes, but only names and spice levels.”
  • “Now also include tech items invented in the last 100 years.”

Benefits: Flexible and efficient.
Challenges: Without limits, you can overload the system with massive queries.

Try it here in under 3 clicks and for free: Star Wars GraphQL API.

SOAP – Alien formal ceremonies

Finally, some aliens are very traditional.
They don’t like casual phrases or flexible headsets.
They insist on formal ceremonies with long scripts, where every word must be exactly right.

That’s SOAP.

  • Uses XML and a WSDL document (the script).
  • Strict, verbose, reliable.
  • Common in banks, insurance, and government.
  • Includes built-in error handling and security standards.

Example:

  • “Perform the recipe-sharing ritual with full nutritional details, in the exact sequence required.”

Benefits: Very structured and safe.
Challenges: Slow to work with and overly complex compared to REST.

Want to see it? Download SoapUI and test a public SOAP service.

Advanced: Try Coding a REST API with AI

If you’re curious how APIs look under the hood, you can get AI to build one for you.

Copy-paste this prompt into ChatGPT (or your favorite AI tool):

Build a minimal REST API using Python + FastAPI.
Domain: Alien Recipes.
CRUD for recipes with fields: id, name, originPlanet, spiceLevel (1–5), ingredients (array of strings).

Requirements:

  • Endpoints: GET /recipes, GET /recipes/{id}, POST /recipes, PUT /recipes/{id}, DELETE /recipes/{id}
  • In-memory store (no DB needed)
  • Validation with Pydantic
  • Auto-generated docs at /docs
  • README with run instructions
  • Example cURL commands

Run it locally in 3 steps:

  1. pip install fastapi uvicorn
  2. Save the code as app.py
  3. Run: uvicorn app:app --reload → open http://localhost:8000/docs

That’s it — you’ll see the alien “guidebook” turned into real code you can play with.

Behind the Scenes

I am a bit of a health freak. I love cooking healthy food, but I’m not so great at cooking… so any time I learn a new recipe, I repeat it until I get tired of it.

Lately, it’s been coconut curries with spices on repeat. Add protein, veggies, microwave rice (for speed) — done.

Any recipes you’re cooking on repeat? Let me know!

What do you think?

Did this newsletter help you simplify APIs a bit?

Hit reply and let me know — do you love it, hate it, want more of something else?

Looking forward to hearing from you,

Maria

Frankfurt am Main, 60311, Germany
Unsubscribe · Preferences

Maria Korteleva

Hi, I’m Maria. For the past 7 years, I’ve been building internal products across FMCG and tech companies.Now, I share everything I’ve learned to help junior PMs master delivery from technical skills to stakeholder communication. Join 200+ Internal PMs who get weekly insights from the Build Internal Products newsletter.

Read more from Maria Korteleva

Hi Reader, Do you also hate bringing up security updates in roadmap reviews? It can't be just me. I don't like it because when I bring it up, the room feels like all the excitement gets sucked out of it. The conversation moves on quickly to the exciting stuff → the new feature, the integration, the thing leadership can demo. And just like that, your security work gets filed under "necessary but boring." It's not that the work isn't important. It's that the framing makes it sound like...

Hi Reader, What if you could generate more value from your product without building it all yourself? Design a good API, hand it to another product team, and let them build on top of your product. You get value. They get functionality. Leadership gets results. Interested? Then this one's for you. Today in 10 minutes you will: Learn why APIs should be on every PM's radar Get a quick refresher on API types Walk away with clear guidelines for good API design See how I built and tested an API in...

Hi Reader, today we're talking about processes. And most importantly: bad ones. You probably have a few lying around your product. Complicated user access. Messy incident management. Confusing onboarding flows. People struggle. Users struggle. But you just don't know where to start fixing it. If that sounds familiar: this one's for you. Today in 10 minutes you will: Learn a simple framework for improving any broken process See an example: how to fix a chaotic user access flow Get a workshop...