API security
API security is the protection of application programming interfaces, their functionality, and exposed data from unauthorized access, misuse, alteration, and disruption.
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.
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.
Also covered in
- Microservices Patterns, Second EditionIn early access (MEAP)
What to know first
- authorizationAuthorization is the determination of which actions or resources an identity or other entity is permitted to access under defined permissions or policies.
- authenticationAuthentication is the process of verifying the claimed identity of a user, service, device, or other entity.
Related concepts
- DDoS attackincludes · A distributed denial-of-service attack uses traffic or requests from multiple sources to overwhelm a target and impair its availability.
- OAuthaddressed by · OAuth is an authorization framework that enables a client to obtain limited, delegated access to protected resources without receiving the resource owner's credentials.
- sensitive data overexposureincludes · Sensitive data overexposure is a security vulnerability in which an API reveals more information, sensitive fields, or callable behavior than a consumer needs or is authorized to access.
- API Security Top 10used by · The API Security Top 10 is an OWASP publication identifying prevalent and critical security risks specific to application programming interfaces.
- vulnerabilityaddresses · A vulnerability is a weakness or condition that makes a system, person, or group susceptible to exploitation, compromise, or other harm.
- authorizationcontrasts with · Authorization is the determination of which actions or resources an identity or other entity is permitted to access under defined permissions or policies.
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.


