Changes only the fields you send on an existing Action. Every field you leave out keeps its current value.
Use Patch rather than Update (PUT) whenever you only want to change some values, for example to move a schedule item's dates or a card to another column. Update replaces the Action, so it needs every field sent back.
Patch an Action
HTTP
PATCH https://organisation.fluid.work/rest/api/action/{id}?version=3.0cURL
curl --user username:patToken --request PATCH 'https://organisation.fluid.work/rest/api/action/4360?version=3.0' \
--header 'Content-Type: application/json' \
--data '{ "fields": { "startDate": "2026-12-01", "endDate": "2026-12-12" } }'{id} is the Action's id or guid. The response is the updated Action, in the same form as Get Action. The fields, expand and version query parameters work as they do for Update.
How the body is applied
Only the names in
fieldschange. A field sent asnullis cleared.titleis optional, but cannot be sent empty.assignee,ownersandviewers: the list you send replaces the current one.[]ornullclears it.A name in
fieldsthat is not a field is refused with422, listing the names that can be sent. So is a read-only field that Get returns, such ascreateDateormodifiedBy: send only the values to change, not a whole Get response.A body that changes nothing is refused with
422.A value that cannot be read, such as a
dueDatethat is not a date orpointsthat is not a number, is refused with422naming the field, and nothing changes. It is not treated asnull: to clear a field, sendnull.customPropertieschanges only the properties listed. Akeythat is not one of the Action's custom properties is refused with422, listing the keys that can be sent, and nothing changes. Keys are matched ignoring case, soregionandREGIONboth setRegion. The same custom property sent twice in one request is refused with422.
Status
statuscan be set. On a board card it must be one of the board's columns (otherwise422, listing them), and the move must be one the board allows (otherwise403, and nothing changes). A board owner can move a card to a restricted column.Sending the status the Action already has changes nothing.
Archiving is not a status: to archive an Action, use Delete.
Schedule (Gantt) items
The dates you send are kept, and the item's effort is recalculated from them on the project calendar, as when you change dates in the Gantt.
endDateanddueDateare the same date on a schedule item: send either one. Sending both with different values is refused with422.A date that falls on a non-working day moves to the next working day.
An
endDatebefore thestartDateis refused with422.A milestone has one date. Send
startDateorendDate; if you send both,endDateis used. A milestone can be moved earlier or later either way.A
ragStatusofCompletedcompletes the item (statusCompletedat 100%), as in the Gantt. It is refused with422on an auto-calculated item, which is completed by its sub-items, and on sites where a Completed RAG is not set by hand: send"status": "Completed"instead.subTypemust be one of your site's schedule sub types that applies to the item'staskType(otherwise422, listing them), and is stored with its configured spelling.nullor""clears it. On any other kind of Action asubTypeis refused with422.
Board cards
On a board with start dates enabled, a
startDatelater than thedueDateis refused with422, as in the card dialog. The same day is allowed.
Examples
Move a schedule item's dates
{ "fields": { "startDate": "2026-12-01", "endDate": "2026-12-12" } }Move a milestone
{ "fields": { "endDate": "2026-12-11" } }Move a card to another column
{ "fields": { "status": "In Progress" } }Set a schedule item's sub type
{ "fields": { "subType": "Epic" } }Set one custom property
{ "customProperties": [ { "key": "Region", "value": "EMEA" } ] }Clear a field
{ "fields": { "description": null } }Patch or Update?
Update (PUT) | Patch (PATCH) | |
|---|---|---|
Fields left out | Cleared, except | Kept |
| Required | Optional, cannot be empty |
Schedule item dates | Written as sent; the effort is kept | Kept as sent; the effort is recalculated; milestones take one date |
Unknown or read-only names in | Ignored | Refused with |
Several Actions in one call | Not available: one Action per call |
Status, custom properties, a Completed RAG, card dates and subType follow the same rules on both.
Responses
Code | Description |
|---|---|
200 | The updated Action |
400 | The request body is missing or is not valid JSON |
401 | Not an authorised user: the username or token is invalid |
403 | You do not have Editor permission on the Action, or the board does not allow the status move |
404 | The Action is not found |
422 | The body is refused; the message says why (see the rules above) |
429 | Too many requests: see the RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset response headers |