activities
Update Activity
Update activity (owner only).
── Sub-chapter 1 (May 2026, Activity Edit Parity) ───────────────────── No more silent ignores. If the request body contains keys outside ALLOWED_EDIT_FIELDS, we return 400 with a structured response so the frontend can highlight the specific rejected fields rather than show a generic toast that hides the bug.
Two layers of rejection are now made visible:
- Pydantic strips fields not in ActivityUpdate before this handler runs. To catch those, we read the raw JSON body BEFORE Pydantic parsing and compare to the dumped result.
- ALLOWED_EDIT_FIELDS gates fields that ActivityUpdate accepts but the PUT handler refuses to write. These were previously skipped silently — now they're surfaced too.
Sub-chapter 2 expands ALLOWED_EDIT_FIELDS to fix the actual silent drops (category, contact_, ticketing_, etc.). Sub-chapter 1 just makes the silence stop.
put/api/activities/{activity_id}
Request
- Base URL: https://api.activitia.net (the document declares no server; this is the origin it was published from)
- URL: https://api.activitia.net/api/activities/{activity_id}
- Auth: none declared
Path parameters
activity_idstring required
Headers
authorizationstring
Request body
Response
Successful Response
unknown required
Changes
No recorded changes to this operation across all 1 revision of this API.