<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>APIs on securecode.dev</title><link>https://securecode.dev/tags/apis/</link><description>Recent content in APIs on securecode.dev</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 26 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://securecode.dev/tags/apis/index.xml" rel="self" type="application/rss+xml"/><item><title>Threat Modeling Modern APIs</title><link>https://securecode.dev/insights/threat-modeling-modern-apis/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate><guid>https://securecode.dev/insights/threat-modeling-modern-apis/</guid><description>&lt;p>Threat modeling APIs is often reduced to a short checklist around authentication and transport security. That rarely surfaces the issues that matter most. Real API risk tends to come from workflow design, trust assumptions between services, and weak authorization at object or action boundaries.&lt;/p></description></item></channel></rss>