Expanded API endpoints
I would love to have expanded API to be able to programmatically interact with my spaces. While Capacities seems to be good in regards to holding my information for myself, I want to programmatically pull it into a web application to transform and display the information in a specific way.
For examples an endpoint like this:
"/space/{space-id}/Daily-Notes/{note-id}" or "/space/{space-id}/People/{person-name}"
Ideally this would work with custom objects as well, like "/space/{space-id}/Custom-Scenario/{record-id}".
These end points can be used for the following scenarios:
- Get a single record from a specific Id or Name & Object Id
- Get all the records of a specific object
- Create a new record of a specific object
- Create multiple records of a specific object
- Update an existing record.
14 Comments
Sign in to comment
This is absolutely needed, the current API&MCP endpoints are basically useless for real scenarios, Capacities will need to expose full CRUD abilities as API/MCP endpoints, just like Notion.
It would be nice to have an ability to create objects via API, its one of the best Notion abilities and the reason why i cannot fully transfer all my LifeOS to capacities
I second the request for a POST feature (create a new object from the MCP). Any update on this?
Hi Capacities - I was excited to see you've closed the MCP Connectors task (https://feedback.capacities.io/b/1v35e680/feature-ideas/capacities-mcp-server). That MCP server existed already, though, from 3rd party.
Can we get the CRUD functionality, pls ? I really want to run my Second Brain with Claude Code, AND I want Capacities to be the wonderful interface on that. But I can't have it work only one way, ie downloading the Capacities MD files - I need to be able to WRITE/EDIT to all object types, not just the Daily Notes.
With all that's happening on the Claude Code side these days, this is becoming quite urgent.
This was requested on sep 24, I came here to ask for the same thing, seems to be planned, do we have an ETA? It would be awesome to create objects and relations between them, in the recipes example, attach a recipe to a specific menu for example.
agree - add api endpoints for calendar
CRUD support would be huge. My current focus is on creating a recipe object and a chrome extension to import recipes from the internet. Can't do that without the ability to create new records of custom objects.
Agreed CRUD is a necessity!
Come on, do it asap.
+1 ! I NEED this feature for making my own automation ! Just a simple crud please 🥺 at least "creating entry"
- Full Task Management API Programmatic access to Task objects: create tasks, update status (open/complete), set/change due dates, reschedule. Currently task management via API is very limited.
- Media and File Support Upload images, PDFs, and other file attachments via API — to automatically archive documents (e.g. invoices, scans) directly into collections like "Receipts" or "Documents".
- Bidirectional Calendar / Daily Notes API Read and write calendar events and daily notes metadata programmatically — to enable context-aware AI assistance based on the daily schedule.
- Object Property Manipulation Update specific custom properties of any object type via API (not just appending text to the content block). Full property-level write access.
- Search API Enhancements More robust search and filtering API comparable to the in-app search experience — for precise retrieval in RAG (Retrieval-Augmented Generation) workflows.
Even some simple CRUD would be great. I'd like to be able to read the contents of an object like the Daily Note.
+1 to this. For example, I have a page in which I maintain very lists using headers and checkboxes and would like to be able to add items to lists within that page
We recently shipped a whole new version of our API: Capacities API 2.0.
https://capacities.io/whats-new/release-67