Public API#110

When you try to fully integrate nolt in your workflow, at some point you will have to access information, because you don’t want to store every post and comment on a separate database in order to match id’s with posts. Currently there is a problem with the post.status.updated webhook, where if you don’t store every post somewhere with all of their information, you will not be able to properly announce a post status update, since you don’t know what the post updated was actually about.

If there would be some sort of API, you could link your webhook integration with the API, so whenever you receive a post.status.update, you could just (for example) GET https://feedback.nolt.io/api/v0/posts/?id=<id> or https://nolt.io/api/v0/<board_id>/posts/?id<post_id>. You could add similar functions for /comments/ or /tags/ or /fields/. You could also add some kind of key & token system, so not every user can just crawl through the api and randomly collect data.

An API is pretty important, especially when webhooks do not share all the information necessairy to keep track of posts. An API could also be useful in the future, because it could also make it possible to automate the creation of comments or ideas, and allow integrations made in both directions.

Could you give an Update on the status?

Hi Steffen. I don’t have a precise update to share today. Product development can be unpredictable, so we don’t want to give promises that we might not uphold. We’ll make sure to update this thread as soon we have some news.

Our public API is in beta! Please reach out to hello@nolt.io to request an API key for your board.

The public API works well for us. It enables us to display a dashboard of votes with the information presented in a way that suits our needs.