github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-11 16:34:10 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #984] Heads-up: Task creation via Vikunja API v0.24.x – only PUT works, not POST #6316

New Issue
Closed
opened 2026-04-20 16:54:02 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-20 16:54:02 -05:00
Owner
Copy Link

Originally created by @SoolinB8 on GitHub (Jun 19, 2025).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/984

Description

I spent hours debugging this and want to save others the same pain.

Problem:
The official Vikunja API docs state you should use a POST request to /api/v1/projects/<project_id>/tasks (or sometimes /api/v1/tasks) to create a new task.
However, on my installation (Vikunja v0.24.6, no custom config.yml, default Docker setup), POST always returns 404 Not Found — but the web frontend can create tasks just fine.

Solution:
The frontend actually uses a PUT request (not POST!) to /api/v1/projects/<project_id>/tasks to create a new task.

Working example (cURL):

curl -X PUT http://localhost:3456/api/v1/projects/3/tasks \
  -H "Authorization: Bearer <your_token>" \
  -H "Content-Type: application/json" \
  -d '{"title": "Task via PUT", "description": "Created by script", "project_id": 3}'

	•	POST to the same endpoint returns 404.
	•	PUT as above returns 201 Created and creates the task.

Background:
	•	The Vikunja web frontend uses this route/method as well — always double-check with browser devtools if API docs don’t match real behavior.
	•	This seems to be a version/build-specific quirk. (Tested on v0.24.6.)

Tips:
	•	If you get 404s with POST on /tasks or /projects/<id>/tasks, try PUT instead!
	•	No custom config, just a standard install.
	•	Double-check the API request method and route using the web frontend’s devtools.

Hope this saves someone a lot of head-scratching!
(Mods: Feel free to update the docs accordingly.)

### Vikunja Version

0.24

### Browser and version

_No response_

### Can you reproduce the bug on the Vikunja demo site?

Please select

### Screenshots

_No response_
Originally created by @SoolinB8 on GitHub (Jun 19, 2025). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/984 ### Description I spent hours debugging this and want to save others the same pain. **Problem:** The official Vikunja API docs state you should use a **POST** request to `/api/v1/projects/<project_id>/tasks` (or sometimes `/api/v1/tasks`) to create a new task. However, on my installation (Vikunja v0.24.6, no custom config.yml, default Docker setup), **POST always returns 404 Not Found** — but the web frontend can create tasks just fine. **Solution:** The frontend actually uses a **PUT** request (not POST!) to `/api/v1/projects/<project_id>/tasks` to create a new task. **Working example (cURL):** ```bash curl -X PUT http://localhost:3456/api/v1/projects/3/tasks \ -H "Authorization: Bearer <your_token>" \ -H "Content-Type: application/json" \ -d '{"title": "Task via PUT", "description": "Created by script", "project_id": 3}' • POST to the same endpoint returns 404. • PUT as above returns 201 Created and creates the task. Background: • The Vikunja web frontend uses this route/method as well — always double-check with browser devtools if API docs don’t match real behavior. • This seems to be a version/build-specific quirk. (Tested on v0.24.6.) Tips: • If you get 404s with POST on /tasks or /projects/<id>/tasks, try PUT instead! • No custom config, just a standard install. • Double-check the API request method and route using the web frontend’s devtools. Hope this saves someone a lot of head-scratching! (Mods: Feel free to update the docs accordingly.) ### Vikunja Version 0.24 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? Please select ### Screenshots _No response_
GiteaMirror added the waiting for reply label 2026-04-20 16:54:02 -05:00
GiteaMirror commented 2026-04-20 16:54:03 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jun 22, 2025):

Where in the docs have you seen this? The swagger docs correctly say PUT. https://try.vikunja.io/api/v1/docs#tag/task/paths/1projects1%7Bid%7D~1tasks/put

<!-- gh-comment-id:2994403200 --> @kolaente commented on GitHub (Jun 22, 2025): Where in the docs have you seen this? The swagger docs correctly say `PUT`. https://try.vikunja.io/api/v1/docs#tag/task/paths/~1projects~1%7Bid%7D~1tasks/put
GiteaMirror commented 2026-04-20 16:54:04 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jul 23, 2025):

Closing as inactive, please ping or open a new issue with relevant information if you still have this problem.

<!-- gh-comment-id:3106920342 --> @kolaente commented on GitHub (Jul 23, 2025): Closing as inactive, please ping or open a new issue with relevant information if you still have this problem.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label waiting for reply
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#6316
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?