# Find events for business cases that changed processing status

Events business cases that changed processing status

Endpoint: GET /api/v1/events/processing-status-changed
Version: 1.1
Security: X-API-Key

## Query parameters:

  - `lastEventId` (integer)
    Id of the last received event. If omitted, the result starts with the oldest available event. :

  - `limit` (integer)
    Maximum number of items to be returned (technical maximum is 1000, no more will be returned).

## Response 200 fields (application/json):

  - `id` (integer, required)
    Event ID
    Example: 12345

  - `timestamp` (string, required)
    timestamp of the event
    Example: "2015-01-01T10:00Z"

  - `businessCaseId` (integer)
    Business Case ID

  - `businessCaseSixId` (string, required)
    business case SIX ID
    Example: "BCID0FB909852BBC4D06AD8336AAE87D7FC9"

  - `newStatus` (string)
    Enum: "OPEN", "INVALID", "PROCESSING", "FAILED", "DELIVERED", "DONE"

## Response 400 fields (application/json):

  - `status` (integer)
    The HTTP status code generated by the origin server for this occurrence of the problem.
    Example: 400

  - `message` (string)
    A human readable explanation specific to this occurrence of the problem.
    Example: "The submitted request contains invalid or missing data which can not be processed."

  - `fieldErrors` (array)

  - `fieldErrors.fieldName` (string)
    the name of the field with the error
    Example: "localizedData.ger.address.city"

  - `fieldErrors.message` (string)
    the message describing the error
    Example: "size must be between 1 and 35"

  - `fieldErrors.rejectedValue` (string)
    the provided value which was rejected if available
    Example: "Very Long Invalid City Name Which Is Rejected"