🏠 back to Observable

API Keys!

Dear friends and authors,

We’ve just launched a new API key feature, now available in your settings, which will allow you to create secret API keys with read-only access to your private notebooks.

Here’s the full details:

But, in a small nutshell:

  • API keys allow reads of private notebooks, as .js file or a .tgz tarball, at any version.
  • Keys are specific to your personal or team account (your personal API keys can’t read team notebooks)
  • API keys don’t expire, and you can create as many as you like, and rotate them when you like.
  • Treat them like you would a password, and don’t embed them on any public webpage.

I’d love to hear your thoughts on this new features, what other API endpoints you’d like these keys to unlock in the future, and any other concerns, complaints or comments about the design…