Plans for making API public?

1

Background

In one of my projects, there is a requirement for a dynamic blog posts platform.

Solution

A very convenient way for this would be using Observablehq API directly.

So, we would set up a new Observablehq user and we would use a collection of notebooks as the menu items and each notebook would be a blog post itself. Much like it is in the Observablehq platform itself.

Screen Shot 2020-09-24 at 14.55.46
Screen Shot 2020-09-24 at 14.55.461429×571 79.4 KB

I know I can integrate existing notebooks directly, but I want to automate as many things as I can. In my view, the client(human being) would just create a new notebook and it would be automatically added in the actual blog platform, which would live in the custom domain. This requires the usage of three, currently existing APIs (As I am aware, between them only one is public now )

Question

Do you recommend using existing (listed bellow) API’s or do you plan to publish similar API endpoints in the future, which would be used by external web apps?

Collections API
https://api.observablehq.com/collections/@bumbeishvili

Collections and notebooks API
https://api.observablehq.com/collection/@bumbeishvili/anatomy?page=1&with_listings=true

1 Like
2

Hi,
In terms of using these APIs… they are not meant to be publicly facing APIs, and could change in the future. I love your creative use of these APIs to create a simple UI to showcase your notebooks. We are also working hard to make the curating and browsing experience even more fun on the platform itself.
We do not have any firm plans to provide supported APIs for these types of queries into Observable, so I would at this point just warn you to use them at your own risk and be aware that they may not work in the future.

3 Likes