Update team quest (admin)
Changed onGate: canManageTeam (owner, editor, legacy admin, platform admin/superadmin). Viewers and outsiders get 403; anonymous 401. Every body field is optional; scalar-only bodies behave exactly as before. steps uses the same item shape as POST create: omitted leaves the quest's steps untouched, [] clears them, a list replaces them. Replacement runs in one transaction with the scalar edits under a row lock on the quest (scoped to quest id + team); step ids are always server-generated and order defaults to the item's index. If steps is supplied (including [] or an unchanged list) and ANY user has started the quest (a UserQuestStatus row exists), the request is refused with 409 CONFLICT and nothing is written, because deleting a QuestStep cascades to user step progress. Scalar-only edits stay allowed with progress. Response is Cache-Control: private, no-store.
Request
- Base URLhttps://app.d-sports.org
- AuthHTTP bearer
Path parameters
Team id or slug.
Team-scoped (non-template) quest id.
Request body
Response
{ success, data: TeamQuest } — the updated quest with steps ordered by order asc.
Changes
- info
endpoint added
- info