# Find events for bill recipients email address changes

This event is triggered after a biller has submitted a business case with an outdated, so called historically available email address. It notifies about the changed email address of a bill recipient, which has been adjusted in eBill. An email address is considered to be historically available if it was present up to 15 months prior to the submission time. The billers are able to submit business cases with historically available email addresses of a bill recipient. However, latest 15 months after the email address changed, the billers are required to submit the business cases with the currently valid email address of the bill recipient. 

Endpoint: GET /api/v1/events/six/bill-recipient-email-address-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"

  - `businessCaseId` (integer)

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

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

  - `oldEmailAddress` (string)
    the old email address of the bill recipient which has been used in the submission of a business case
    Example: "peter@muster.ch"

  - `newEmailAddress` (string)
    the new email address of the bill recipient
    Example: "peter_new@muster.ch"

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