Endpoint BayISSUE #20 of 45

graphql · query language for apis

RestaVSThe 401 Bandit

Resta saysGraphQL is a query language where the client asks for exactly the data it needs.

Instead of many fixed REST endpoints, GraphQL exposes one endpoint and a typed schema. The client sends a query specifying exactly which fields it wants — no over-fetching, no under-fetching, and related data in one round-trip. It shifts shaping power to the client at the cost of server complexity and caching trade-offs.

Power-ups you unlock

One endpoint, a typed schema
Client requests exactly the fields it needs
Avoids over/under-fetching
Related data in one round-trip

The 401 Bandit attacks — common mistakes

Treating GraphQL as a REST replacement always
Ignoring query-cost/depth limits
Losing HTTP caching benefits unawares

Boss battleWrite a GraphQL query fetching a user’s name and their posts’ titles.

Example code

<!doctype html><html><head><meta charset="utf-8"></head>
<body style="background:#06040d;color:#e6e0ff;font-family:monospace;padding:20px"><pre>query {
  user(id: 42) {
    name
    posts { title }
  }
}</pre></body></html>

▶ Open the interactive comic issue

‹ Versioning · /V1/ · Headers · Subdomains Graphql · Queries · Mutations · Subscriptions ›