liveBook · Manning

API security

API security is the protection of application programming interfaces, their functionality, and exposed data from unauthorized access, misuse, alteration, and disruption.

How 3 Manning books explain it

Secure APIs

The discipline of protecting application programming interfaces, including their exposed data, functionality, and access paths, from misuse and attack.

How it is used
Guides secure API design, implementation, testing, deployment, and operations across the full development lifecycle.
How deep it goes
Explains attack vectors, design flaws, mitigations, testing, architecture, and monitoring, while deferring detailed vulnerability implementation to focused treatments.
Examples
Uses SSRF through an avatar URL, SQL injection and oversized pagination requests, account takeover, data breaches, and business-flow abuse.
What you can do after
Build it from scratch, secure APIs by design, test vulnerabilities continuously, configure supporting infrastructure, and detect malicious activity.

Read how Secure APIs explains API security →

The Design of Web APIs, Second Edition

API security is the protection of an application programming interface, its operations, and the data and resources it exposes from unauthorized access or harmful use.

How it is used
Guides decisions about which API operations and data authorized consumers and end users can access.
How deep it goes
Explains call-level checks and design practices, but defers deeper treatment of OAuth 2.0 and OpenID Connect.
Examples
Uses a shopping order request, fitness profile and workout data, and banking scope changes to illustrate security decisions.
What you can do after
Practice/perform a design review that limits exposure, specifies access rules, protects updates, and documents secure behavior.

Read how The Design of Web APIs, Second Edition explains API security →

Automating API Delivery

API security is the protection of information exchanged through APIs and the reduction of risks arising from API vulnerabilities.

How it is used
Protects API-exposed information and business assets by bringing security checks into design, delivery, testing, and operation.
How deep it goes
Defines vulnerabilities and threat-modeling terms, then outlines design scans, dynamic testing, and runtime monitoring without detailing their implementation.
Examples
Uses an intentionally insecure OWASP crAPI OpenAPI definition for design review and a 42Crunch GitHub Action for scored pipeline checks.
What you can do after
Apply it via security-focused definition linting and a configurable pipeline gate, while planning separate testing and runtime protection.

Read how Automating API Delivery explains API security →

Also covered in

What to know first

Related concepts

Questions about API security

What is API security?

API security is the protection of application programming interfaces, their functionality, and exposed data from unauthorized access, misuse, alteration, and disruption.

Which Manning books explain API security?

Secure APIs, The Design of Web APIs, Second Edition and Automating API Delivery.

What should I know before learning API security?

Manning books that teach API security usually introduce authorization, api attack, authentication and business logic abuse first.

What is the difference between API security and authorization?

API security is the protection of application programming interfaces, their functionality, and exposed data from unauthorized access, misuse, alteration, and disruption. Authorization is the determination of which actions or resources an identity or other entity is permitted to access under defined permissions or policies.

What kinds of API security are there?

Kinds of API security include DDoS attack and sensitive data overexposure.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.