POST /api/applications/workspace/{workspace_id}/order/
Changes the order of the provided application ids to the matching position that the id has in the list. If the authorized user does not belong to the workspace it will be ignored. The order of the not provided tables will be set to 0
.
Servers
- /
Path parameters
Name | Type | Required | Description |
---|---|---|---|
workspace_id |
Integer | Yes |
Updates the order of the applications in the workspace related to the provided value. |
Request headers
Name | Type | Required | Description |
---|---|---|---|
ClientSessionId |
String | No |
An optional header that marks the action performed by this request as having occurred in a particular client session. Then using the undo/redo endpoints with the same ClientSessionId header this action can be undone/redone. |
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
ClientUndoRedoActionGroupId |
String | No |
An optional header that marks the action performed by this request as having occurred in a particular action group.Then calling the undo/redo endpoint with the same ClientSessionId header, all the actions belonging to the same action group can be undone/redone together in a single API call. |
Request body fields
Name | Type | Required | Description |
---|---|---|---|
application_ids[] |
Array | Yes |
Application ids in the desired order. |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.