API access to your Recall knowledge base
under review
P
Paul Richards
The API would allow you to access all your Recall data as well as add more content and edit existing content.
Log In
S
Sunny M
still not done?
Sankari Nair
Merged in a post:
Live Data Connectors
M
Michael Bull
Recall needs live data connectors to external services - eg:
-> eg. Pocket, Obsidian, Notion, Raindrop, NotebookLM, Evernote, Google Drive, Gmail, etc
-> also live connectors for browser history - Chrome, Edge, opera
-> users could choose which connectors to use
-> the current method of manually uploading bookmarks & markdown files is old fashioned & clunky
-> someone is surely going to offer live connectors + chat feature very soon (if not already?!), so Recall urgently needs to get ahead of the game
Sankari Nair
Merged in a post:
Cloud Drive Folder for Recall App
9
9qyrw4wssp
Similar to iA Writer and Obsidian apps, mitigate your risks of financial losses, lawsuits and user data losses by implementing a Recall app feature where users data are mirrored to their iCloud drive, folder.
Sankari Nair
Merged in a post:
Integrations
R
Raphael Pinho
Integrations with apps like Tick Tock, Todoist and Aki Flow
Sankari Nair
Merged in a post:
Public API or Webhook to create Knowledge Cards (Solving the LinkedIn/Walled Content issue)
M
Matt Thompson
I am requesting a simple API endpoint (or a "Create Card" action in Zapier/Make) that allows external tools to push content into Recall programmatically.The ProblemI built a personal tool to capture LinkedIn posts because the Recall browser extension—like most scrapers—struggles with LinkedIn’s dynamic DOM and authentication walls.Current Workflow: I capture the post locally $\rightarrow$ Copy text $\rightarrow$ Paste into Recall manually.The Pain Point: I lose all structured metadata (Author, Source URL, Date) and the context of the original post during the manual copy-paste.The SolutionPlease provide a simple inbound endpoint. Even a basic webhook that accepts Markdown would solve this.Example Payload:JSONPOST /api/cards
{
"title": "Post by John Smith regarding AI Strategy",
"content": "## Extracted Text \n\n [Full text content...]",
"source_url": "https://linkedin.com/posts/johnsmith-123",
"tags": ["leadership", "strategy"],
"format": "markdown"
}
Why This MattersThe browser extension is great for static articles, but it fails on "walled gardens" (LinkedIn, private Discords, paywalled stacks, local PDFs). An API allows power users to build their own bridges to get this high-value data into Recall, keeping Recall as the central source of truth rather than forcing us to use other tools for these specific sources.Happy to beta test this if you are working on it!
C
Charles Gagnon
Would this item cover an MCP endpoint? It seems like a way to connect this AI/knowledge base to tools using MCP endpoints could be extremely helpful. If it’s considered a separate feature, I’m happy to file it just didn’t want to double up.
E
Edgar Lezama Haller
May your API allow me to connect and be able to make a white label, very grateful, greetings from Mexico
Sankari Nair
marked this post as
under review
J
Jody Dellinger (Chief D)
Facebook page integration would be great
A
Ali Hakimi
Or google drive
Load More
→