Linkwarden API route is deprecated, returns 400 error

[emersonveenstra]

Which version of floccus are you using?

5.5.6

How many bookmarks do you have, roughly?

360

Are you using other means to sync bookmarks in parallel to floccus?

No

Sync method

Linkwarden

Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.

Brave v1.80.125 (Chromium 138.0.7204.184)

Which version of Nextcloud Bookmarks are you using? (if relevant)

No response

Which version of Nextcloud? (if relevant)

No response

What kind of WebDAV server are you using? (if relevant)

No response

Describe the Bug

In linkwarden/linkwarden@d870ffe, Linkwarden deprecated /api/v1/links, and it now returns a 400 error, which breaks syncing.

I created linkwarden/linkwarden#1318 which hopefully will have them revert that change, but wanted to write here as well

Expected Behavior

Syncing works

To Reproduce

1. Create a linkwarden profile using cloud.linkwarden.app
2. Attempt to sync bookmarks

Debug log provided

• I have provided a debug log file

[emersonveenstra]

2025-07-31T13:25:44.120Z Starting sync process for account Toolbar
2025-07-31T13:25:44.122Z Failed to load pending continuation. Continuing with normal sync
2025-07-31T13:25:44.122Z Using "merge default" strategy (no cache available)
2025-07-31T13:25:44.123Z Retrieving local tree
2025-07-31T13:25:44.124Z Overriding title of built-in node 1 Bookmarks => Bookmarks Bar
2025-07-31T13:25:44.124Z Filtering out unaccepted local bookmarks
2025-07-31T13:25:44.124Z Retrieving server tree
2025-07-31T13:25:44.124Z QUEUING GET https://cloud.linkwarden.app/api/v1/links?cursor=
2025-07-31T13:25:44.124Z FETCHING GET https://cloud.linkwarden.app/api/v1/links?cursor=
2025-07-31T13:25:44.308Z Receiving response for GET https://cloud.linkwarden.app/api/v1/links?cursor=
2025-07-31T13:25:44.310Z Syncing failed with E019: HTTP status 400. Failed GET request. Check your server configuration and log.

[github-actions]

Hello 👋

Thank you for taking the time to open this issue with floccus. I know it's frustrating when software
causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at
and if possible solved. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings.
I'm Marcel. I created floccus a few years ago, and have been maintaining it since. I currently work for Nextcloud
which leaves me with less time for side projects like this one than I used to have.
I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it.
Until then, please be patient. It helps when you stick around to answer follow up questions I may have,
as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report
and the issue cannot be solved without it, I will have to close the issue after a while.
Note also that GitHub in general is a place where people meet to make software better together. Nobody here is under any obligation
to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can
collaborate to make this software better. For everyone.
Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge
and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and
try to fix the odd bug yourself. Everyone will be thankful for extra helping hands!
If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way,
I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already.
You can find donation options at https://floccus.org/donate/. Thank you!

One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the Nextcloud forum,
to twitter or somewhere else. But this is a technical issue tracker, so please make sure to
focus on the tech and keep your opinions to yourself.

Thank you for reading through this primer. I look forward to working with you on this issue!
Cheers 💙

[marcelklehr]

Thank you for investigating I also noticed this recently, but haven't had time to investigate :)

[daniel31x13]

Hey, I posted a comment over here about what happened, sorry: linkwarden/linkwarden#1318 (comment)

Edit: It's worth mentioning that only the GET method is deprecated, all other routes, sub-routes, and methods are unchanged.

[daniel31x13]

@marcelklehr I just created a PR which should resolve this issue. Thanks for your work!

[bellash252]

Nice application Sharp software.