Get all diagram types for which processes are available

Use this resource to retrieve a list of diagram types for which data is available. Use the response to further call for the list of diagrams by each type, see Get all processes of a single diagram type.

Request

To retrieve the process list, send a GET request to the endpoint defined below.

URL: /process/processes

Method: GET

Authorization: required

GET /ibis/rest/process/processes?diagramType=bpd,technical,organigram,systemdiagram,constraintsdiagram,processmap
Accept: application/xml, application/json
Host: localhost:8000

Query Parameters

The following table lists the query parameters for this request.

Name Description Required Allowed values

Name	Description	Required	Allowed values
`diagramType`	Specify the diagram types to include in the result. Separate multiple types with a comma.	yes	`bpd` `technical` `organigram` `systemdiagram` `constraintsdiagram` `processmap`
`userGroup`	Specified user group	no	Any valid user group, e.g.: `admin`

diagramType

Specify the diagram types to include in the result. Separate multiple types with a comma.

yes

bpd
technical
organigram
systemdiagram
constraintsdiagram
processmap

userGroup

Specified user group

Any valid user group, e.g.: admin

Response

Depending on the Accept header, the response contains a list of processes that match the specified diagram types in XML or JSON format. The response will be empty if no diagrams with the given diagram types are matched.

XML
JSON

HTTP/1.1 200 OK
Content-Type: application/xml

<ProcessesList total="6">
    <Type href="http://localhost:8000/ibis/rest/process/processes/organigram?lang=en" name="organigram"/>
    <Type href="http://localhost:8000/ibis/rest/process/processes/technical?lang=en" name="technical"/>
    <Type href="http://localhost:8000/ibis/rest/process/processes/systemdiagram?lang=en" name="systemdiagram"/>
    <Type href="http://localhost:8000/ibis/rest/process/processes/bpd?lang=en" name="bpd"/>
    <Type href="http://localhost:8000/ibis/rest/process/processes/processmap?lang=en" name="processmap"/>
    <Type href="http://localhost:8000/ibis/rest/process/processes/constraintsdiagram?lang=en" name="constraintsdiagram"/>
</ProcessesList>

HTTP/1.1 200 OK
Content-Type: application/json

{
  "items": [
    {
      "href": "http://localhost:8000/ibis/rest/process/processes/organigram?lang=en",
      "name": "organigram"
    },
    {
      "href": "http://localhost:8000/ibis/rest/process/processes/technical?lang=en",
      "name": "technical"
    },
    {
      "href": "http://localhost:8000/ibis/rest/process/processes/systemdiagram?lang=en",
      "name": "systemdiagram"
    },
    {
      "href": "http://localhost:8000/ibis/rest/process/processes/bpd?lang=en",
      "name": "bpd"
    },
    {
      "href": "http://localhost:8000/ibis/rest/process/processes/processmap?lang=en",
      "name": "processmap"
    },
    {
      "href": "http://localhost:8000/ibis/rest/process/processes/constraintsdiagram?lang=en",
      "name": "constraintsdiagram"
    }
  ],
  "total": 6
}

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"
}