Building APIs for Backend Developers
Building APIs is designing the interface through which clients use a backend. REST models resources over HTTP with consistent URLs and status codes, GraphQL lets clients query exactly the fields they need, gRPC with Protobuf gives fast typed service-to-service calls, and documentation such as OpenAPI makes any of them usable.
Stage: Web and APIs · Part of the Backend Developer roadmap · Last reviewed 19 November 2026
What to learn in Building APIs
- Design REST resources, URLs and status codes for a small domain
- Add pagination, filtering and versioning to a list endpoint
- Compare a REST endpoint with a GraphQL query for the same data
- Define a gRPC service in a .proto file
- Write an OpenAPI description and generate docs from it
Building APIs interview questions
When would you choose GraphQL over REST?
GraphQL fits when many different clients need different shapes of related data and you want to avoid over-fetching or many round trips. REST is simpler, cacheable over HTTP and often enough. GraphQL adds server complexity, such as query cost limits and N+1 resolution.
Why do many companies use gRPC between internal services?
gRPC uses Protobuf, a compact binary format with a strict schema, over HTTP/2, giving smaller messages, streaming and generated client code in many languages. It suits internal service calls. Browsers support it less directly, so public APIs often stay REST.
Where Building APIs fits in the Backend Developer roadmap
Building APIs belongs to the Web and APIs stage (beginner level), which takes about 6 hours. HTTP, API design and the architecture of web services.
Other units in this stage
Back to the full Backend Developer roadmap