API Security
ELI5 — The Vibe Check
API security is protecting your APIs from abuse, data leaks, and unauthorized access. It covers authentication (who are you?), authorization (can you do this?), rate limiting (slow down!), input validation (that looks suspicious), and encryption (nobody's eavesdropping). Your API is a door to your data — API security is the lock, alarm, and guard.
Real Talk
API security encompasses the practices and tools for protecting APIs from threats including broken authentication, excessive data exposure, injection attacks, and resource abuse. It follows the OWASP API Security Top 10, implementing measures like OAuth2/JWT for auth, rate limiting, input validation, schema validation, and API gateways for centralized security controls.
When You'll Hear This
"Our API security audit found 3 endpoints leaking sensitive data in responses." / "API security isn't just auth — it's rate limiting, input validation, and response filtering."
Related Terms
API Gateway
An API Gateway is the front door for all your APIs.
JWT Security
JWT Security is about not screwing up JSON Web Tokens.
OAuth2
OAuth2 is the updated version of OAuth that everyone actually uses today.
OWASP API Top 10
The OWASP API Top 10 is a cheat sheet of the most common ways APIs get hacked.
Rate Limiting
Rate limiting is like a bouncer who says 'you can come in 100 times per hour, then you wait.