Skip to content
Learning pathIntermediate

Building and calling APIs

Design an HTTP API people can rely on, read its status codes, choose between REST, GraphQL and gRPC, receive webhooks safely and call a paginated API with retries.

By Grokem Editorial

  • 5lessons
  • ~50 minin total
  • Intermediatelevel
  • 3topics

Outcomes

What you will be able to do

  • Resources, methods, status codes, errors, pagination, versioning and security: the decisions that make an HTTP API predictable for the people who build on it.

  • Every status code a typical web application or API returns, grouped by what the client should do next, with the mistakes that cause each one.

  • Three ways to expose and call services, compared on data fetching, typing, performance, browser support and tooling, with a short guide to picking one.

  • A webhook endpoint is a public door. Build one that checks who sent the request, rejects old replays and survives the same event arriving twice.

  • Collect every page from an API that sometimes returns 503 or 429: follow the cursor, retry only what is worth retrying, wait with backoff and jitter, and stop when it is hopeless.

Covered

Topics and formats in this path

  • REST
  • APIs & Integrations
  • Webhooks
  • Best practices
  • Reference
  • Comparison
  • Integration

Learning plan

5 lessons, in order

Each lesson is short enough for one sitting and ends by pointing to the next.

  1. Best practices

    RESTDoneStarted

    A REST API design checklist

    Resources, methods, status codes, errors, pagination, versioning and security: the decisions that make an HTTP API predictable for the people who build on it.

    Grokem Editorial

Questions

Before you start

Who is this for?
Design an HTTP API people can rely on, read its status codes, choose between REST, GraphQL and gRPC, receive webhooks safely and call a paginated API with retries. It is written for intermediate readers.
How long does it take?
About 50 minutes of reading and doing across 5 lessons. Each lesson shows its own time, so you can do one at a sitting.
Do I need an account?
No. Everything here is free to read. An account is only needed to ask or answer a question in the community.
What if I get stuck on a lesson?
Ask in the community: say which lesson, what you tried and what happened. Every lesson also shows when it was last verified.

Ready when you are

Open the first lesson now: nothing to install, nothing to sign up for.

Choose what we may use. You can change this at any time with “Privacy choices” at the foot of every page. Details are in the Cookie policy and the Privacy policy.

Strictly necessary

Remembers your theme, the lessons you marked as done and this choice. It stays on your device, tracks nothing and cannot be switched off.

Always on
What exactly is collected, and why

Google Analytics

Collects
The pages you view, your device and browser type, your language, how you reached the site and your approximate location (country and city, worked out from your IP address).
Why
To understand which pages and lessons are used, so we can improve them.
Stored
Two cookies, _ga and _ga_<id>, for up to 2 years. Google acts for us; the data is processed by Google, including outside your country.

Grokem’s own counts

Collects
The pages you open and how long you stay, how far you scroll, where you came from, your device type, browser, screen size, language and time zone. Your IP address is turned into a code that changes every day; it is never stored as it is.
Why
To see how long lessons are read and where readers leave. Not shared with anyone.
Stored
A random visitor ID, a visit ID and the time of your last page view in your browser’s storage (gr_vid, gr_sid, gr_last). No name or email is attached.
Building and calling APIs | Grokem