API Security: Safeguarding Your Software Interfaces
Understand API security essentials, including the OWASP Top 10, authentication practices, and how to ensure safe data exchanges.
What has been corrected on this page?
Every accepted correction to this page is recorded with the exact change, so readers can see how the page improved over time.
-
3 corrections applied: The USPS Informed Visibility API flaw was disclosed in November 2018, not 2019 | RFC 9700 was published January 2025, not 2023 | RFC 9700 was published January 2025, not 2023
Before(1) "In 2019, researchers disclosed a vulnerability in the US Postal Service's Informed Visibility API..." (2) "The Implicit Flow's deprecation (RFC 9700, 2023)" (3) "IETF. (2023). RFC 9700: OAuth 2.0 Security Best Current Practice."
After(1) "In 2018, researchers disclosed a vulnerability in the US Postal Service's Informed Visibility API. The flaw was straightforward: the API did not properly verify that users could only access their own account data." (2) "The Implicit Flow's deprecation (RFC 9700, 2025) reflects real attacks..." (3) "IETF. (2025). RFC 9700: OAuth 2.0 Security Best Current Practice. Internet Engineering Task Force."
Why: Verified: body text correctly gives the USPS Informed Visibility disclosure as 2018 and both RFC 9700 mentions (inline callout and bibliography) as 2025 (RFC 9700 was actually published January 2025). No stale 2019 or 2023 dates remain for these facts anywhere on the page, and the FAQ schema does not reference either the USPS incident or RFC 9700. No further changes needed.
View the full record →
Who checked this page?
1 contributor has checked "API Security: Safeguarding Your Software Interfaces" on When Notes Fly. Each name below links to that person's public CitePep profile, where every contribution they have made is listed with the exact change they proposed.