Project backup 404 not found? #1862
-
This is the Python script which intended to backup everything via the API,
I got this error: So I went to my browser to check out http://localhost:3000/api/projects/1/tasks, also showing 404 not found, what's wrong with this implementation? |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments
-
I think I got a typo, it should be "project" and not "projects", and "history" parameter seems not exists |
Beta Was this translation helpful? Give feedback.
-
http://localhost:3000/api/project/1/backup <- this is documented on API reference but it shows 404 not found |
Beta Was this translation helpful? Give feedback.
-
Hello @lkthomas I was also wondering why this API endpoint was throwing a 404 with my v2.9.45 (latest stable) installation while being documented officially Based on #1748 which shows that it this feature has been merged to the "develop" branch quite recently (540669a) I installed the version v2.9.53-beta and the api call works. So this is a non issue, but I would advise devs/maintainers to set some versionning on the api doc page. Thanks for the good work |
Beta Was this translation helpful? Give feedback.
-
Also the Singular and plural for the endpoint isn't consistent, some has "s", some doesn't |
Beta Was this translation helpful? Give feedback.
-
Docs: https://www.semui.co/api-docs/#/project/get_project__project_id__tasks |
Beta Was this translation helpful? Give feedback.
Hello @lkthomas
I was also wondering why this API endpoint was throwing a 404 with my v2.9.45 (latest stable) installation while being documented officially
Based on #1748 which shows that it this feature has been merged to the "develop" branch quite recently (540669a)
I can assume you're just like me : not running the latest beta version containing this change.
I installed the version v2.9.53-beta and the api call works.
So this is a non issue, but I would advise devs/maintainers to set some versionning on the api doc page.
It's currently displaying v2.9.4 hence the legitimate confusion we encountered.
Thanks for the good work