Commit graph

10 commits

Author SHA1 Message Date
e8c4f3e9b7 v10 2025-06-05 16:38:21 -04:00
e923a9bda7 v9 2025-06-05 16:38:10 -04:00
9ad8ad4a21 v8
> also, any reference to "tags" as params or args is likely needing to be "labels". Which means that the "get_bookmarks_by_tag() function can be deleted, since it is provided by the get_bookmarks_by_label() function

this generated v4, v5, v6, v7, and v8
2025-06-05 16:21:14 -04:00
39951de3c3 v7 2025-06-05 16:21:00 -04:00
01d5c1ac6a v6 2025-06-05 16:20:47 -04:00
1c95cde2f9 v5 2025-06-05 16:20:35 -04:00
bb2d8f0585 v4 2025-06-05 16:20:18 -04:00
bd55899a1e v3
> it looks like the GET /bookmarks/labels/{name} returns a JSON data that includes a "href_bookmarks" key that has the value of a URI endpoint that needs to be called to actually get all the bookmarks of a label
v3

> it looks like the GET /bookmarks/labels/{name} returns a JSON data
that includes a "href_bookmarks" key that has the value of a URI
endpoint that needs to be called to actually get all the bookmarks of a
label
2025-06-05 16:15:37 -04:00
6b537ae76a v2
> let's add an endpoint for getting bookmarks by label. The Readeck API enpoint for that is GET /bookmarks/labels/{name} (or to see all labels is GET /bookmarks/labels).
2025-06-05 16:10:09 -04:00
1b4131cec0 claude.ai:
> write a python program to run as a "tool" (https://openwebui.com/tools) for openweb-ui, which connects to a Readeck intance (https://codeberg.org/readeck/readeck).  This tool exposes OpenAPI endpoints to get bookmarks and collections from the user's Readeck account.
2025-06-05 16:08:11 -04:00