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’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. That is meant for personal scripts and for trying things out, not for running an application.
Commercial applications registered through acoustid.biz are not affected.
The user API key already exists. It is generated when a user signs in to the website, and until now it has only been needed for submitting fingerprints.
If you maintain an application:
- Add a setting where the user can paste their own key, and link them to the page where it is generated. If you already support submissions, you have this and the same key works.
- Send it as the
userparameter on/v2/lookup, alongside yourclientkey. - Keep your application key. It is still required.
If you use an application like this, sign in at acoustid.org, generate a key and paste it in. If you have ever submitted fingerprints, you already have one.
Later on, high traffic open source applications will be able to opt in to user keys that are tied to their application key, so that a key a user generates for one application cannot be used with another. This will work something like OAuth, with a consent screen where the user approves the application by name. If you maintain such an application and want this, get in touch.
This does not change the submission API.