<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>API on bradleycarey.com</title>
    <link>https://bradleycarey.com/tags/api/</link>
    <description>Recent content in API on bradleycarey.com</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 07 Jun 2026 18:12:38 -0400</lastBuildDate>
    <atom:link href="https://bradleycarey.com/tags/api/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Your Browser Session Is Programmatic Access</title>
      <link>https://bradleycarey.com/posts/browser-session-is-programmatic-access/</link>
      <pubDate>Fri, 05 Jun 2026 12:00:00 -0400</pubDate>
      <guid>https://bradleycarey.com/posts/browser-session-is-programmatic-access/</guid>
      <description>&lt;p&gt;A service account is the right way to automate a production system.&lt;/p&gt;&#xA;&lt;p&gt;But refusing to issue one does not mean users cannot automate the system. It usually means they will automate it with their own browser session instead, which is worse in almost every way except paperwork.&lt;/p&gt;&#xA;&lt;p&gt;That is the uncomfortable part. If a user can do something in the web app, and the web app talks to backend APIs, then the user already has some form of programmatic access.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
