notionapi

> Around 3 months ago, I started having issues with their "Export" feature I'm surprised you continued relying on them even after you realized this feature isn't working 3 months ago. > I even exchanged emails with the founders giving detailed feedback It also seems like you've been an early adopter so didn't you half expect this product might have major flaws and probably not the best idea to rely on it so heavily? There seems to be an unofficial exporter you can use here: https://github.com/kjk/notionapi

Worst comes to worst, you could export using a library like this one: https://github.com/kjk/notionapi That being said, definitely not ideal and is always a risk when storing your data with a SaaS service (disclaimer: I'm the founder of dendron.so - a fast open source notion competitor made for developers)

This is a great news. I've been toying with the idea of generating parts of my blog from notion. There are currently some projects which reverse-engineered the API and provide an "unofficial" clients [1][2]. The problem though is that I'd like to blog to be minimum maintenance after a spike of work and I'm afraid the unofficial clients will inevitably break and will require updates. The problem with the current beta is the limits of the API. E.g. code block are not supported[3], so you can't really use it to generate a technical blog. Looking forward to the GA :) [1]: https://github.com/jamalex/notion-py [2]: https://github.com/kjk/notionapi [3]: https://developers.notion.com/reference/get-block-children

We combined different approaches to make it work: First, inspecting all network requests that are happening on the web client. That helped to inspect all requests made to read a page and edit content (a lot of data is transiting, maybe that's why it's slow on the startup...). And then I realized there were few existing open-source projects that already done that (https://github.com/kjk/notionapi and https://github.com/jamalex/notion-py), but there were lacking an HTTP API endpoint so that we can easily plug them that to Zapier/Integromat or a Webhook. These two repo didn't had a way to convert a Markdown to a Notion content - which would make it complicated to know every type of blocks that makes a Notion page. Finally you needed to be tech-savvy to be able to deploy the open-source projects and there wasn't any simple integration SaaS ou

I think Markdown does qualify as machine-readable. There are very good libraries to do all kinds of things with it. Edit: I guess you meant human-readable as opposed to things like base64, and not as a critique against Markdown. By now, there are several unofficial APIs at least, for read-access they are quite good apparently, did not yet use one myself though. E.g. https://github.com/kjk/notionapi

I use notion.so They support code snippets via code blocks. I use it for notes but also for much more. For example, my website (https://blog.kowalczyk.info/) is almost fully generated out of content stored in Notion via a custom program (https://github.com/kjk/blog) that uses my (unofficial, reverse-engineered) API library for Go (https://github.com/kjk/notionapi). Notion is very rich so it might be overwhelming at first but it's the last note-taking application I'll ever use.

I use notion.so (in the past I used evernote and simplenote via nv mac client). Notion is better because it's hierarchical (as opposed to "a bundle of independent documents" model of evernote/simplenote and pretty much everything else. And it has many unique features, like simple spreadsheets, trello-like boards, todo lists, dates and reminders and all of it presented in a cohesive UI. You can see example of my notes at https://blog.kowalczyk.info/article/9a07ca64c0c14dc09e8bd134... They are published on my website but the content is stored in notion (9a07ca64c0c14dc09e8bd134b348678d is the id of a page in notion). In fact, all of my website is re-published from content stored in Notion. I also keep private notes there but ability to publish non-private notes on the web is a nice bonus. To do that I wrote a Go library to access data from

Just in case someone might need it: I reverse engineered their API and wrote (an unofficial) client for accessing the data: https://github.com/kjk/notionapi It's for Go but one could easily port it to any other language. It's just HTTP requests and some light processing of JSON responses. I use it so that I can have my blog content in Notion. In a daily cron job I download the data from Notion, convert it to HTML and publish on Netlify as a static website. This script is open source: https://github.com/kjk/blog Basically I use Notion as CMS. I described my reverse-engineering process in https://blog.kowalczyk.info/article/88aee8f43620471aa9dbcad2...