Export a transaction workflow
GET
/transaction-workflows/{id}/exportReturns the workflow in the app's export format: its name, label, description and status, and its steps in order with temporary ids (step_0, step_1, ...), their fields, requirements, triggers and links. Links and step ids in trigger config use the temporary ids. POST /transaction-workflows/import and the app both accept it. Nothing is changed.
Path parameters
The record's id.
Responses
{
"data": {
"workflow": {
"name": "string",
"label": "string",
"description": "string",
"status": "draft",
"isDefault": true
},
"steps": [
{
"id": "string",
"name": "string",
"label": "string",
"description": "string",
"type": "default",
"isProtected": true,
"isFloating": true,
"showDefaultInternalMessage": true,
"stepFields": [],
"workflowCustomStepRequirements": [],
"workflowCustomStepTriggers": [],
"nextStepLinks": []
}
]
}
}403Error
Authorization failed. error.code is one of org_disabled,
ip_blocked, missing_scope, scope_disabled, user_disabled.
422Error
The request can't be processed (HTTP 422): validation_failed with one ErrorDetail per
problem, or a code documented on the operation.
Examples
curl https://your-org-domain/kong/core/api/v2/transaction-workflows/{id}/export\
-H "Authorization: Bearer $HELM_API_KEY"\
-H "Content-Type: application/json"