Skip to content
ShankarStack

Foundations & inventory

REST, GraphQL and the API attack surface

APIs expose business logic directly, often with less implicit protection than a server-rendered UI. Knowing how they're structured tells you where to look.

What this lesson covers

  • REST resource modelling vs GraphQL's single endpoint
  • Reading API documentation and schemas
  • GraphQL introspection and schema discovery
  • How clients consume APIs and what that reveals
  • Why 'the UI never calls this' is not a control

In depth

With an API, the client is frequently just a convenience over endpoints that must defend themselves. For GraphQL, the schema documents the entire surface — including fields a UI never shows. Understanding the shape of the API is the prerequisite for everything else.

Common pitfalls

  • Testing only the endpoints the official client calls
  • Assuming an undocumented endpoint is unreachable

Reporting mindset: for every observation, record what you did, what you saw, the business impact, and a clear, verifiable remediation. Evidence and clear writing are what turn testing into value.

This is a free preview. Sign in to track progress and unlock the full course.

Sign in