<?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 AcoustID News and Updates</title>
    <link>https://blog.acoustid.org/tags/api/</link>
    <description>Recent content in api on AcoustID News and Updates</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 19 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.acoustid.org/tags/api/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Applications will need a user API key for lookups from January 1, 2027</title>
      <link>https://blog.acoustid.org/posts/2026-11-19-user-api-keys-required-for-lookups/</link>
      <pubDate>Thu, 19 Nov 2026 00:00:00 +0000</pubDate>
      
      <guid>https://blog.acoustid.org/posts/2026-11-19-user-api-keys-required-for-lookups/</guid>
      <description>Starting from January 1, 2027, lookups made by any application registered through acoustid.org will need both the application key in the client parameter and the user&amp;rsquo;s own key in the user parameter. This lets me account for use per person rather than per application, which has historically been a problem for larger open source applications.
A user key on its own, without a registered application, will be allowed a small number of lookups.</description>
    </item>
    
  </channel>
</rss>
