Security Testing for API Securitys
API security testing checks an API for vulnerabilities by sending crafted requests, both manually and with automation. It includes testing authorisation by swapping tokens and IDs, fuzzing inputs, and running static and dynamic scanners, using tools like Postman, Burp Suite and OWASP ZAP against a safe test environment.
Stage: Testing · Part of the API Security roadmap · Last reviewed 19 November 2026
What to learn in Security Testing
- Test for BOLA by replaying one user's request with another user's token
- Fuzz parameters and headers to find unexpected errors and injections
- Import an OpenAPI file into ZAP or Burp to scan every endpoint
- Write automated security regression tests that run in CI
- Report a finding with steps to reproduce, impact and a suggested fix
Security Testing interview questions
How do you test an API for broken authorisation?
Create two ordinary users and an admin. Capture a request as user A, then replay it with user B's token and with no token, and try admin-only routes as a normal user. Any success where access should be denied indicates broken object or function-level authorisation.
What is the difference between SAST and DAST for APIs?
SAST analyses source code without running it and finds patterns like unsafe queries early. DAST attacks a running API from outside and finds issues in deployment and configuration, such as missing headers. They find different problems, so mature pipelines use both.
Where Security Testing fits in the API Security roadmap
Security Testing belongs to the Testing stage (advanced level). Verify.
Back to the full API Security roadmap