[GH-ISSUE #1376] FR: set arbitrary metadata to bookmarks via the api #881

Open
opened 2026-03-02 11:53:28 +03:00 by kerem · 1 comment
Owner

Originally created by @thiswillbeyourgithub on GitHub (May 9, 2025).
Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/1376

Describe the feature you'd like

Hi,

Anticipating the many things I want to do with my karakeep bookmarks, I don't think I've see in the update a bookmark api doc how to set arbitrary metadata.

I think it would be tremendously useful and greatly expend what's possible.

I'm thinking something like the X-properties in caldav: basically any property of an attribute starting by X- will be ignored by any client that does not expect it. This allows any new client to store their own thing without worrying about backwards or forward compatibility.

My first use of it would probably be to store some scores and hook it up to my upcoming pairwise comparison tool. As well as to to sync my nextcloud caldav todo list items ids to map to karakeep bookmarks.

I'll only have a limited portion of my summer to dedicate to this so I hope it can be implemented in time :)

Describe the benefits this would bring to existing Karakeep users

A whole new ecosystem of karakeep utils could see the light of day. With the freefalling cost of vibe coding, I think the sooner the better!

Can the goal of this request already be achieved via other means?

No. Tags are not ideal to store data.

Have you searched for an existing open/closed issue?

  • I have searched for existing issues and none cover my fundamental request

Additional context

No response

Originally created by @thiswillbeyourgithub on GitHub (May 9, 2025). Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/1376 ### Describe the feature you'd like Hi, Anticipating the many things I want to do with my karakeep bookmarks, I don't think I've see in the [update a bookmark](https://docs.karakeep.app/API/update-a-bookmark/) api doc how to set arbitrary metadata. I think it would be tremendously useful and greatly expend what's possible. I'm thinking something like the `X-properties` in caldav: basically any property of an attribute starting by `X-` will be ignored by any client that does not expect it. This allows any new client to store their own thing without worrying about backwards or forward compatibility. My first use of it would probably be to store some scores and hook it up to my upcoming pairwise comparison tool. As well as to to sync my [nextcloud caldav todo list](https://github.com/thiswillbeyourgithub/CaldavTasksAPI) items ids to map to karakeep bookmarks. I'll only have a limited portion of my summer to dedicate to this so I hope it can be implemented in time :) ### Describe the benefits this would bring to existing Karakeep users A whole new ecosystem of karakeep utils could see the light of day. With the freefalling cost of vibe coding, I think the sooner the better! ### Can the goal of this request already be achieved via other means? No. Tags are not ideal to store data. ### Have you searched for an existing open/closed issue? - [x] I have searched for existing issues and none cover my fundamental request ### Additional context _No response_
Author
Owner

@thiswillbeyourgithub commented on GitHub (Jun 5, 2025):

A notable example of use case:

  • store the DOI of research papers
  • store the zotero ID to easily intersect databases

It would be nice to also allow x properties for highlights

<!-- gh-comment-id:2943119647 --> @thiswillbeyourgithub commented on GitHub (Jun 5, 2025): A notable example of use case: - store the DOI of research papers - store the zotero ID to easily intersect databases It would be nice to also allow x properties for highlights
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/karakeep#881
No description provided.