<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Api-Design on dplabs — Software Engineering &amp; Technology Consultancy</title>
		<link>https://dplabs.tech/tags/api-design/</link>
		<description>Recent content in Api-Design on dplabs — Software Engineering &amp; Technology Consultancy</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Mon, 29 Jun 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://dplabs.tech/tags/api-design/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Secure by Default: APIs That Are Hard to Misuse</title>
				<link>https://dplabs.tech/blog/secure-by-default-apis/</link>
				<pubDate>Mon, 29 Jun 2026 00:00:00 +0000</pubDate>
				<guid>https://dplabs.tech/blog/secure-by-default-apis/</guid>
				<description>&lt;p&gt;Security by default is a design principle, not a feature list. An API is secure by default when using it correctly produces secure behavior automatically, and producing insecure behavior requires deliberate effort.&lt;/p&gt;&#xA;&lt;p&gt;Most security failures are not the result of sophisticated attacks on well-designed systems. They&amp;rsquo;re the result of developers using APIs incorrectly, making incorrect assumptions about what defaults are safe, or forgetting to add security checks that should have been built in.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
