Book
Secure APIs
Design, build, and implement
José Haro Peralta
Summary
José Haro Peralta organizes API security around moving it earlier: the design, build, and operate stages each get security work instead of leaving it to a review at the end. The book dissects the OWASP Top 10 API security risks and gives a chapter each to authentication and authorization flaws and to API configuration and management flaws, showing how an attacker exploits weak authentication, insufficient constraints, and a flawed architecture. From there it covers securing an API by design, implementing authorization and authentication, and building secure API infrastructure, with a separate chapter on the stricter requirements of financial-grade APIs. The closing chapters turn to running APIs: observability and monitoring for threat detection, and security testing. Case studies are drawn from e-commerce, ridesharing, and other high-visibility targets. Examples are in Python.
Target Readers
- Backend developers who want API security decided at design time rather than caught in a review at the end
- Engineers implementing or revisiting authentication and authorization, who want the common flaws named and demonstrated
- Teams running an API platform that needs monitoring and security testing in place, not just a hardened configuration
Tags
Colophon
- Publisher
- Shoeisha
- ISBN
- 978-4-7981-9633-6
- Published
- Jul 2026
- List price
- ¥4,950incl. taxMay differ from the actual selling price on Amazon
Get this book
* The link above is an advertisement via Amazon Associates.Related Books
Prerequisites
- Recommended
The Design of Web APIs
Arnaud Lauret
Reason: Having grasped the practice of API design—contract-first with OpenAPI, pagination, versioning—you start to see the next challenge: how to build security into that design. Secure APIs builds up a shift-left perspective, addressing authentication/authorization vulnerabilities and API configuration risks starting from the design stage.
- Recommended
OpenID Connect Nyumon (Introduction to OpenID Connect)
Practical Technical Guide for Application Developers
Kohei Toki
Reason: Once you understand OIDC's authorization code flow and JWT validation at the implementation level, widen your view to the security of the API as a whole. This book covers not only vulnerabilities rooted in authentication and authorization, but also API configuration risks, financial-grade API requirements, observability, and testing — building security in from the design stage.
Next Books
- Related
Hacking APIs
Breaking Web Application Programming Interfaces
Corey Ball
Reason: After learning to defend APIs from the design stage with a shift-left mindset, check from the attacker's side whether that design actually holds up. Learning authorization-gap vulnerabilities like BOLA/IDOR from the offensive side lets you work backward to reassess the robustness of your design.