Get process diagram history
Use this resource to retrieve the version history of a specific process diagram.
Request
To retrieve the process diagram history, send a GET request to the endpoint defined below.
URL: /process/processes/{diagramType}/{diagramGroup}/{diagramName}/history
Method: GET
Authorization: required
GET /ibis/rest/process/processes/technical/ProcessDocumentation/TargetTWF_CL/history
Accept: application/json
Host: localhost:8000
Path Parameters
The following table lists the path parameters for this request.
| Name | Description | Required | Allowed values |
|---|---|---|---|
|
Enter the type of the diagram. |
yes |
|
|
Enter the diagram group. |
yes |
Any string |
|
Enter the diagram name. |
yes |
Any string |
Response
The response contains a JSON object with the process version history.
HTTP/1.1 200 OK
Content-Type: application/json
{
"diagramName": "TargetTWF_CL",
"historyEntries": [
{
"version": "11",
"date": "08.04.2026 17:26:25",
"user": "username",
"comment": "",
"tags": [],
"href": "http://localhost:8000/ibis/rest/process/processes/technical/ProcessDocumentation/TargetTWF_CL/version/11"
},
{
"version": "10",
"date": "08.04.2026 12:51:40",
"user": "username",
"comment": "DefaultRenameWorkflowCheckinComment@@@TargetTWF_CL/TargetTWF_CL_2@@@",
"tags": [
{
"name": "ThisIsANewTag",
"searchHref": "http://localhost:8000/ibis/rest/process/tag/ThisIsANewTag"
}
],
"href": "http://localhost:8000/ibis/rest/process/processes/technical/ProcessDocumentation/TargetTWF_CL/version/10"
},
{
"version": "9",
"date": "08.04.2026 12:51:26",
"user": "username",
"comment": "",
"tags": [],
"href": "http://localhost:8000/ibis/rest/process/processes/technical/ProcessDocumentation/TargetTWF_CL/version/9"
},
{
"version": "8",
"date": "08.04.2026 12:50:33",
"user": "username",
"comment": "ModifyProcessRolesToWorkflow",
"tags": [],
"href": "http://localhost:8000/ibis/rest/process/processes/technical/ProcessDocumentation/TargetTWF_CL/version/8"
},
{
"version": "7",
"date": "26.03.2026 16:11:29",
"user": "username",
"comment": "",
"tags": [],
"href": "http://localhost:8000/ibis/rest/process/processes/technical/ProcessDocumentation/TargetTWF_CL/version/7"
},
{
"version": "6",
"date": "26.03.2026 16:10:14",
"user": "username",
"comment": "DefaultRenameWorkflowCheckinComment@@@TargetTWF_CL_2/TargetTWF_CL@@@",
"tags": [],
"href": "http://localhost:8000/ibis/rest/process/processes/technical/ProcessDocumentation/TargetTWF_CL/version/6"
},
{
"version": "5",
"date": "26.03.2026 16:09:31",
"user": "username",
"comment": "ModifyProcessRolesToWorkflow",
"tags": [],
"href": "http://localhost:8000/ibis/rest/process/processes/technical/ProcessDocumentation/TargetTWF_CL/version/5"
},
{
"version": "4",
"date": "26.03.2026 16:09:15",
"user": "username",
"comment": "",
"tags": [],
"href": "http://localhost:8000/ibis/rest/process/processes/technical/ProcessDocumentation/TargetTWF_CL/version/4"
},
{
"version": "3",
"date": "26.03.2026 15:16:59",
"user": "username",
"comment": "DefaultMovedWorkflowCheckinComment@@@ProcessDocumentation/admin@@@",
"tags": [],
"href": "http://localhost:8000/ibis/rest/process/processes/technical/ProcessDocumentation/TargetTWF_CL/version/3"
},
{
"version": "2",
"date": "26.03.2026 15:08:13",
"user": "root",
"comment": "ModifyProcessRolesToWorkflow",
"tags": [],
"href": "http://localhost:8000/ibis/rest/process/processes/technical/ProcessDocumentation/TargetTWF_CL/version/2"
},
{
"version": "1",
"date": "26.03.2026 15:00:52",
"user": "root",
"comment": "",
"tags": [],
"href": "http://localhost:8000/ibis/rest/process/processes/technical/ProcessDocumentation/TargetTWF_CL/version/1"
}
]
}
Errors
This request might return one of the following error codes:
- Authorization Failed (401)
-
Authorization with the given username and password failed. Please revisit both values and provide valid credentials.
{
"statusCode": 401,
"message": "Unauthorized access",
"path": "/rest/<endpoint>",
"timestamp": "2025-06-07T14:21:11.781"
}
- Resource Not Found (404)
-
The 404 (Not Found) status code indicates that the requested endpoint or resource is unavailable or does not exist on the server.
- Server Error (500)
-
Execution on the INUBIT server failed. Have a look into the response message, otherwise access to the INUBIT log is required to retrieve further information.
{
"statusCode": 500,
"message": "Internal Server Error",
"path": "/rest/<endpoint>",
"timestamp": "2025-08-06T12:55:31.862"
}
- Service Unavailable (503)
-
In maintenance mode the INUBIT server endpoint will not respond to incoming requests but return this error response. Once the maintenance mode is switched off the endpoint will respond normally.
{
"statusCode": 503,
"message": "Service Unavailable",
"path": "/rest/<endpoint>",
"timestamp": "2025-08-06T12:58:06.688"
}