The goal of the REST API is to provide access to all relevant interfaces of the engine.

Structure

These documents explain all existing methods in the REST API. For each method they provide:

  • An informal description
  • HTTP verb and URL
  • Possible query, path or message body parameters
  • A detailed description of the response content
  • Possible response codes
  • A brief example request and response

    Engine Usage

The methods as described work on the default process engine as given by the available ProcessEngineProvider service.

You may prepend /engine/{name} to any of the methods (unless otherwise documented) to access another engine where {name} is the name of the process engine as returned by ProcessEngine#getName(), e.g., /engine/myEngineName/task.

Error Handling

For every method this documentation gives possible HTTP status codes. The error code explanations do not cover all possible error causes that may arise when the request is served, for example, most of the requests will not work properly if there are problems with database access. Any of these undocumented errors will be translated to a HTTP 500 error.

All errors also provide a JSON response body of the form:

  1.   {
  2.     "type" : "SomeExceptionClass",
  3.     "message" : "a detailed message"
  4.   }

Authorization Exceptions

If an already authenticated user interacts with a resource in an unauthorized way, the status code of the response will be set to 403 Forbidden. Details about the unauthorized interaction are provided in the response body.

Type

AuthorizationException

Response Body

  1. {"type" : "AuthorizationException",
  2.  "message" : "The user with id 'jonny' does not have 'DELETE' permission on resource 'Mary' of type 'User'.",
  3.  "userId" : "jonny",
  4.  "permissionName" : "DELETE",
  5.  "resourceName" : "User",
  6.  "resourceId" : "Mary"}

Migration Validation Exceptions

If a migration plan from one process definition version to another is notvalid, a migration exception is thrown. It can be a migration plan validationexception where the plan itself is not valid, e.g., it contains an invalidinstruction. Or it can be a migrating process instance validation exception when amigration plan cannot be applied to a specific process instance, e.g., an activeactivity was not mapped by the migration plan.

Migration Plan Validation Exceptions

Type

MigrationPlanValidationException

Response Body

A JSON object with the following properties:

Name Value Description
type String The type of exception, here MigrationPlanValidationException.
message String The error message.
validationReport Object A JSON object containing details about all detected validation errors. Its properties are described below.

Every validation report object contains the following properties:

Name Value Description
instructionReports Array A JSON array describing a single instruction validation report. Each report object consists of an instruction that is invalid and a failures array containing the validation messages for this instruction.

Example

  1. {
  2.   "type": "MigrationPlanValidationException",
  3.   "message": "ENGINE-23001 Migration plan for process definition 'invoice:1:8aa1533c-23e5-11e6-abb7-f6aefe19b687' to 'invoice:2:8accd012-23e5-11e6-abb7-f6aefe19b687' is not valid:\n\t Migration instruction MigrationInstructionImpl{sourceActivityId='approveInvoice', targetActivityId='assignApprover', updateEventTrigger='false'} is not valid:\n\t\tActivities have incompatible types (UserTaskActivityBehavior is not compatible with DmnBusinessRuleTaskActivityBehavior)\n",
  4.   "validationReport": {
  5.     "instructionReports": [
  6.       {
  7.         "instruction": {
  8.           "sourceActivityIds": [
  9.             "approveInvoice"
  10.           ],
  11.           "targetActivityIds": [
  12.             "assignApprover"
  13.           ],
  14.           "updateEventTrigger": false
  15.         },
  16.         "failures": [
  17.           "Activities have incompatible types (UserTaskActivityBehavior is not compatible with DmnBusinessRuleTaskActivityBehavior)"
  18.         ]
  19.       }
  20.     ]
  21.   }
  22. }

Migrating Process Instance Validation Exceptions

Type

MigratingProcessInstanceValidationException

Response Body

A JSON object with the following properties:

Name Value Description
type String The type of exception, here MigratingProcessInstanceValidationException.
message String The error message.
validationReport Object A JSON object containing details about all detected validation errors. Its properties are described below.

Every validation report object contains the following properties:

Name Value Description
processInstanceId String The id of the process instance that cannot be migrated when following the migration plan.
failures Array An array of general failure messages, which are not related to a specific activity or transition.
activityInstanceValidationReports Array An array of JSON objects describing the single activity instance validation errors. Each activity instance validation report consists of a migrationInstruction, if the error is related to an existing migration instruction, the activityInstanceId and sourceScopeId of the activity which cannot be migrated and an array failures, which is a list of all validation error messages for this report.
transitionInstanceValidationReports Array An array of JSON objects describing the single transition instance validation errors. Each transition instance validation report consists of a migrationInstruction, if the error is related to an existing migration instruction, the transitionInstanceId and sourceScopeId of the transition which cannot be migrated and an array failures, which is a list of all validation error messages for this report.

Example

  1. {
  2.   "type": "MigratingProcessInstanceValidationException",
  3.   "message": "ENGINE-23004 Cannot migrate process instance '96dc383f-23eb-11e6-8e4a-f6aefe19b687':\n\tCannot migrate activity instance 'approveInvoice:f59925bc-23eb-11e6-8e4a-f6aefe19b687':\n\t\tThere is no migration instruction for this instance's activity\n\tCannot migrate transition instance 'f598897a-23eb-11e6-8e4a-f6aefe19b687':\n\t\tThere is no migration instruction for this instance's activity\n",
  4.   "validationReport": {
  5.     "processInstanceId": "96dc383f-23eb-11e6-8e4a-f6aefe19b687",
  6.     "failures": [],
  7.     "activityInstanceValidationReports": [
  8.       {
  9.         "migrationInstruction": null,
  10.         "activityInstanceId": "approveInvoice:f59925bc-23eb-11e6-8e4a-f6aefe19b687",
  11.         "sourceScopeId": "approveInvoice",
  12.         "failures": [
  13.           "There is no migration instruction for this instance's activity"
  14.         ]
  15.       }
  16.     ],
  17.     "transitionInstanceValidationReports": [
  18.       {
  19.         "migrationInstruction": null,
  20.         "transitionInstanceId": "f598897a-23eb-11e6-8e4a-f6aefe19b687",
  21.         "sourceScopeId": "ServiceTask_1",
  22.         "failures": [
  23.           "There is no migration instruction for this instance's activity"
  24.         ]
  25.       }
  26.     ]
  27.   }
  28. }

Authentication

The REST API ships with an implementation of HTTP Basic Authentication. By default it is switched off (in the rest-api web application and therefore also in the pre-built Camunda BPM distributions). You can activate it by adding a servlet filter as described in the Authentication section.

原文: https://docs.camunda.org/manual/7.9/reference/rest/overview/