Edit workflow step

Requires ADMIN or PROJECT_MANAGER role with the setup-server access right. All fields are optional; omitted or null fields retain their existing values. Abbreviation must be unique within the organization. Returns 403 if the organization plan does not support workflow steps or if LQA is not enabled for the organization when lqaEnabled is true.

PUT /api2/v1/workflowSteps/{workflowStepUid}

Edit workflow step

cURL

curl --request PUT \
  --url https://cloud.memsource.com/web/api2/v1/workflowSteps/{workflowStepUid} \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "abbr": "<string>",
  "lqaEnabled": true,
  "name": "<string>",
  "order": 123
}
'

200

{
  "abbr": "<string>",
  "id": "<string>",
  "lqaEnabled": true,
  "name": "<string>",
  "order": 123,
  "uid": "<string>"
}

Authorizations

ApiTokenOAuth2

Authorization · string · header · required

Get a token from auth/login endpoint and then pass it in the Authorization HTTP header in every subsequent API call. For more information visit our help center.

Path Parameters

workflowStepUid · string · required

UID of the workflow step

Body

application/json

abbr · string

Abbreviation of the workflow step (1–3 characters)

Required string length: 1 - 3

lqaEnabled · boolean

When true, enables LQA for this step; omit to keep the existing value

name · string

Name of the workflow step

Required string length: 1 - 255

order · integer<int32>

Display order of the workflow step

Response

200

application/json

OK

abbr · string

Abbreviation of the workflow step (1–3 characters)

id · string

Internal numeric identifier, encoded as a string

lqaEnabled · boolean

When true, LQA is enabled for this step

name · string

Name of the workflow step

order · integer<int32>

Display order of the workflow step

uid · string

Unique identifier used in API paths