Write API access to Recall
Sankari Nair
The ability to make changes in your Recall knowledge base via an API, such that you could add content and adjust content.
Log In
Sankari Nair
Merged in a post:
two way integration with AI models
C
Chris Smith
right now Claude can only read access my recall library, it would be great to give it write access too
Sankari Nair
Merged in a post:
Mcp that alters and produces content
R
Raphael Pinho
It is possible that the mcp is not only for reading, but also for production and editing to actually be a second living brain.
s
schroell
If you would write your requests in English, you would probably have more success in upvoting from other users
r
recall
I am now in one month testing phase to decide whether to switch to Recall or not - the write API is a soft breaking point. I have some some Make workflows that are storing info into my current PKM and the unability to do such things in Recall do play against it. All I need is actually to create a new card (e. g. when the workflow decides to store an e-mail for future reference).
P
Poe Nauta
Hi team,
I'm a paying user and I've been following the write API since you shipped the read-only API back in April. Since then the answer has always been "coming soon" / "follow up soon" / "further down the line" — but with no date and no endpoints, and the July 12 changelog still describes it as the "first step in development."
Let me explain why this is urgent for me specifically. I want to programmatically create and edit notebook content — including inserting internal [[ ]] links between related cards. I've already run a manual pilot and it works, but it's not viable at scale without a write API. Right now my only option is browser automation, which is slow and fragile.
The minimum that would unblock me: the ability to create/edit notebook content via the API, internal links included. Even if that's all you ship first, it would be huge for me.
Could you share even a realistic date range, or the scope of the first write-API release — will it cover notebook editing and links, or only card creation? Knowing that would help me decide whether to keep waiting or build a workaround.
Thanks for the work you put in — Recall has become central to how I think, which is exactly why I need to get my data out and edit it programmatically.
Miguel
Sankari Nair
Merged in a post:
Mcp that Edits
R
Raphael Pinho
The mcp be abble not only to only read, but also edit the content
Sankari Nair
For sure, this is on our radar, we are working towards it. It first requires a couple changes to our our backend, and then this can come right after. Just merging it into the write API request.
R
Rhys Gottwald
I would absolutely love this, being able to use a third-party LLM to generate connections.
Sankari Nair
Merged in a post:
The REST API currently supports read-only operations. A write API is on the roadmap.
t
tgp_chat
I am currently exploring the use of OpenClaw to write structured data into Recall AI, specifically for fields such as title, summary, tags, and source. I would like to understand the current status of this integration and whether these metadata fields are supported or require custom implementation.
A
Anton
Popping a comment to get onboarded to beta test 🫡
Load More
→