Update a task

PUT/task/{connection_id}/task/{id}

Parameters

fieldsstring array
Fields to return
rawstring
Raw parameters to include in the 3rd-party request. Encoded as a URL component. eg. raw parameters: foo=bar&zoo=bar -> raw=foo%3Dbar%26zoo%3Dbar
connection_idstring required
ID of the connection
idstring required
ID of the Task

Payload

idstring
created_atdate-time
(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
updated_atdate-time
(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
namestring
project_idstring
(reference to TaskProject)
parent_idstring
completed_atdate-time
(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
status enum
Valid values:
"OPENED"
"IN_PROGRESS"
"COMPLETED"
notesstring
due_atdate-time
(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
start_atdate-time
Scheduled/planned start of the task (distinct from created_at) (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
end_atdate-time
Scheduled/planned end of the task (distinct from due_at and completed_at) (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
prioritystring
assigned_user_idsstring array
(reference to HrisEmployee)
creator_user_idstring
The user who created this task (reference to HrisEmployee)
follower_user_idsstring array
(reference to HrisEmployee)
group_idsstring array
(reference to HrisGroup)
tagsstring array
urlstring
attachment_idsstring array
Array of attachment IDs retrieved from StorageFile.Get endpoint
metadata array
has_childrenboolean
typestring
The task/issue type name (e.g. Jira issue type).
time_spentnumber
time_spent_unitstring
progressnumber
0-100
story_pointsnumber

Returns

Response fieldTypeRequiredDescription
idstringNo
created_atstring (date-time)No(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
updated_atstring (date-time)No(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
namestringNo
project_idstringNo(reference to TaskProject)
parent_idstringNo
completed_atstring (date-time)No(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
statusenumNoValues: OPENED, IN_PROGRESS, COMPLETED
notesstringNo
due_atstring (date-time)No(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
start_atstring (date-time)NoScheduled/planned start of the task (distinct from created_at) (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
end_atstring (date-time)NoScheduled/planned end of the task (distinct from due_at and completed_at) (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
prioritystringNo
assigned_user_idsstring[]No(reference to HrisEmployee)
creator_user_idstringNoThe user who created this task (reference to HrisEmployee)
follower_user_idsstring[]No(reference to HrisEmployee)
group_idsstring[]No(reference to HrisGroup)
tagsstring[]No
urlstringNo
attachment_idsstring[]NoArray of attachment IDs retrieved from StorageFile.Get endpoint
metadataTaskMetadata[]No
metadata[].idstringNo
metadata[].valueobjectNo
metadata[].namespacestringNo
metadata[].formatenumNoValues: TEXT, NUMBER, DATE, BOOLEAN, FILE, TEXTAREA, SINGLE_SELECT, MULTIPLE_SELECT, MEASUREMENT, PRICE, YES_NO, CURRENCY, URL
metadata[].extra_dataobjectNo
metadata[].slugstringNo
has_childrenbooleanNo
typestringNoThe task/issue type name (e.g. Jira issue type).
time_spentnumberNo
time_spent_unitstringNo
progressnumberNo0-100
story_pointsnumberNo

Errors

Errors return the HTTP status code and a JSON body with statusCode, error (the short label) and message (a human-readable detail).

{
  "statusCode": 429,
  "error": "Too Many Requests",
  "message": "Too many requests to unified.to API; max requests per minute: N"
}
StatusErrorMeaning
400Bad RequestThe request was malformed or failed validation.
401UnauthorizedThe connection is likely broken; re-authorize it.
403ForbiddenThe connection is missing permissions or scopes.
404Not FoundThe requested resource does not exist.
429Too Many RequestsRate limit exceeded (see the two sources below).
500Internal Server ErrorAn unexpected error occurred.
501Not ImplementedNot supported by this integration.

Errors from the underlying integration pass through: the integration's status comes back as ours (429, 401, 403, 404 or 5xx), usually with its message. When the integration's error body is unclear, Unified extracts what it can and returns a clearer message.

429 Too Many Requests

A 429 has two possible sources:

  • The integration's own rate limit, passed through.
  • Unified's workspace limit: a rolling 60 seconds, set by plan, with the message Too many requests to unified.to API; max requests per minute: N.
const options = {
  method: 'PUT',
  url: 'https://api.unified.to/task/5de520f96e439b002043d8dc/task/5de520f96e439b002043d8d8',
  headers: {
    authorization: 'bearer .....'
  },
  data: undefined,
  params: {
    fields: '',
    raw: '',
  }
};

const results = await axios.request(options);
Are we missing anything? Let us know
Was this page helpful?