Call GitHub’s Real API From Your Terminal

You just tried a practice API and saw it work. Now let’s go bigger. GitHub runs an API that millions of developers use every day, and the basics you already know are enough to call it too.

To call GitHub’s real API, you ask the address api.github.com for a user with one command: curl https://api.github.com/users/torvalds. Back comes that developer’s live public profile, no login needed.

What does it mean to call GitHub’s real API?

Think of a public records desk. You give a name, and the clerk pulls that person’s public file. GitHub’s API works the same way. You give a username, and it returns that developer’s public profile, live and real.

An API (Application Programming Interface) is simply a way for one program to ask another for data. GitHub opens part of its API to anyone, so you don’t need a password to read public information. That makes it the perfect place to practice on something real.

How is the GitHub API address built?

Every request has two parts: the service and the path. Let’s break it apart.

• api.github.com is the service. It’s the front door.
• /users is the section. It tells GitHub you want a person, not a repository.
• /torvalds is the specific person you’re asking about.

Put them together and you get a path that asks for exactly one thing: this user, right now.

https://api.github.com/users/torvalds

Reading an address this way is the same skill we used to learn step by step in earlier lessons. Once a URL stops looking like a wall of text and starts looking like “service, then section, then thing,” APIs feel a lot less scary.

How do I run the command?

Open your terminal and type one line:

curl https://api.github.com/users/torvalds

Press Enter. In a second or two, GitHub sends back real data about that account. You’ll see fields like their login name, how many public repositories they have, when they joined, and more.

{
  "login": "torvalds",
  "name": "Linus Torvalds",
  "public_repos": 8,
  "followers": 230000
}

This isn’t a fake demo. It’s the same live data the GitHub website shows. You just asked for it directly instead of clicking through a browser.

Why does calling a real API matter?

Because the exact same skill works on thousands of other APIs. Weather services, payment systems, maps, social platforms, AI tools, all of them speak this same request-and-response language. Learn to read one address and you can read them all.

It also builds confidence. When you call GitHub’s real API and watch live data come back, you stop feeling like an outsider to software. You’re now talking to the same systems professional developers use to build apps, just like the ones we cover when learning to build with Claude Code later in the course.

How can I try it with a different account?

Swap torvalds for any username you like. Try your own GitHub handle, a friend’s, or a famous developer’s:

curl https://api.github.com/users/your-username

Every name gives you a fresh, live profile. Change one word and you’ve made a brand-new request. That’s the whole idea: small commands you can repeat and adjust until they feel natural.

Key takeaways

• Call GitHub’s real API with one command: curl https://api.github.com/users/torvalds.
• The address has three parts: the service (api.github.com), the section (/users), and the person (the username).
• Public GitHub data needs no login, so it’s a safe place to practice.
• The same request skill works on thousands of other APIs.
• Swap the username to fetch any developer’s live public profile.

Next up: reading the docs, so you can turn an API’s instructions into your own requests. Keep the streak going.

---

🚀 Take the full free course: Zero to AI Hero — learn to build with AI from scratch. New lessons daily, in Hindi & English.