- From: Fuqiao Xue <xfq@w3.org>
- Date: Wed, 26 Jul 2023 09:31:29 +0800
- To: Denis Ah-Kang <denis@w3.org>
- Cc: spec-prod <spec-prod@w3.org>
Thanks, Denis! Gargantua[1] should probably be updated as well, since it still uses the API key. Fuqiao [1] https://github.com/w3c/gargantua/blob/main/fetch-utils.js > On Jul 25, 2023, at 23:15, Denis Ah-Kang <denis@w3.org> wrote: > > Hi all, > > I'm pleased to inform that you no longer need an API key to access > the W3C API. It is now completely public. > > If you are already relying on the API in your different tools, we > recommend that you update them to remove the key (whether it's passed > as a query string parameter or in the Authorization header). > Note that some existing clients such as node-w3capi [1] or apiary [2] > have been updated to drop the key so please use the latest versions. > > If you never heard of the API, you can find more details at: > - https://w3c.github.io/w3c-api/ > - https://api.w3.org/doc > > Let me know if you have any questions. > > Regards, > > Denis > > [1] https://github.com/w3c/node-w3capi > [2] https://github.com/w3c/apiary >
Received on Wednesday, 26 July 2023 01:31:36 UTC