Start an ad-hoc process

Use this resource to start an ad-hoc process. This triggers a new instance of a technical workflow at the module specified by the ad-hoc process starter ID. This module is usually a Task Generator or is followed by a Task Generator.

Request

To start the process, send a POST request to the endpoint defined below.

URL: /task/adhoc/{user}/{id}

Method: POST

Authorization: required

POST /ibis/rest/task/adhoc/testuser/74933f6c-72c6-44c5-9e90-91070f98c7dd HTTP/1.1
Accept: application/xml
Host: localhost:8080

The request body is empty.

Path Parameters

The following table lists the path parameters for this request.

Name Description Required Allowed values

Name	Description	Required	Allowed values
`user`	Enter the username.	yes	Any existing username
`id`	Enter the ID of an ad-hoc process starter that the user can access.	yes	Any valid ad-hoc process starter ID

user

Enter the username.

yes

Any existing username

id

Enter the ID of an ad-hoc process starter that the user can access.

yes

Any valid ad-hoc process starter ID

Query Parameters

The following table lists the query parameters for this request.

Name Description Required Allowed values

Name	Description	Required	Allowed values
`lang`	Enter the language code.	no (default: `de`)	`de` or `en`
`client`	Enter the tenant name.	no	e.g. `Virtimo_AG`

lang

Enter the language code.

no (default: de)

de or en

client

Enter the tenant name.

e.g. Virtimo_AG

Response

If the request is successful, the server returns one of the following responses.

HTTP/1.1 201 Created
Content-Type: application/plain

10f66801-77e7-4dfa-8f40-0f5039d4552a

201 Created: A new task was created. The response body contains the ID of the new task. The new task receives the attributes popup=true and user=<username>.
204 No Content: The process was started successfully, but no follow-on task was created.

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