# Find events for instalments which changed status

Events for status changes of instalment bills only.

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

## Query parameters:

  - `lastEventSixId` (string)
    SIX 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

  - `sixId` (string, required)
    SIX event ID
    Example: "EVID82A65938766547EBBBA39BA6F7B07F24"

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

  - `businessCaseId` (integer)
    Business Case ID
    Example: 12345

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

  - `paymentByInstalmentsId` (integer, required)
    PaymentByInstalments ID
    Example: 12345

  - `paymentByInstalmentsSixId` (string)
    external ID of the respective paymentByInstalment
    Example: "298031-2999"

  - `instalmentId` (integer, required)
    Instalment ID
    Example: 12345

  - `instalmentSixId` (string)
    external ID of the instalment
    Example: "298031-2999-ACX01"

  - `newStatus` (string)
    the new status of the instalment
    Enum: "OPEN", "APPROVED", "REJECTED", "COMPLETED", "CHARGEBACK_INITIATED"

  - `approvedAmount` (object)
    Amount provided by status changed events if the new status is APPROVED. The value is always greater than zero.

  - `approvedAmount.value` (number, required)
    The amount value. Take care when using JavaScript libraries to parse this value - it should be treated as a financial amount and therefore not as a floating point number but rather using a precise decimal representation (like BigDecimal in Java).  :   :
    Example: 99.99

  - `approvedAmount.currencyCode` (string, required)
    The amount currency code according to ISO-4217.
    Example: "CHF"

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