# Search for multiple bill recipients

For each item in the request body, the endpoint will respond if it is allowed to submit a business case for a bill recipient with the provided ID. In addition to the provided ID, the response will always contain the billRecipientId, if a business case submission is allowed.

Endpoint: POST /api/v1/bill-recipients/search
Version: 1.1
Security: X-API-Key

## Request fields (application/json):

  - `items` (array, required)

  - `items.emailAddress` (string)
    email address of the bill recipient
    Example: "peter@muster.ch"

  - `items.billRecipientSixId` (string)
    SIX ID of the bill recipient
    Example: 41010560425610180

  - `items.enterpriseIdentificationNumber` (string)
    Swiss enterprise identification number (UID) without dashes, dots or extension. Note that this has to contain the swiss enterprise identification number (UID) from the commercial register (Handelsregister) which may be different from the VAT UID (Mehrwertsteuer UID).
    Example: "CHE123456789"

## Response 200 fields (application/json):

  - `items` (array, required)

  - `items.emailAddress` (string)
    email address of the bill recipient
    Example: "peter@muster.ch"

  - `items.billRecipientSixId` (string)
    SIX ID of the bill recipient
    Example: 41010560425610180

  - `items.activeSubscription` (boolean)

  - `items.enterpriseIdentificationNumber` (string)
    Swiss enterprise identification number (UID) without dashes, dots or extension. Note that this has to contain the swiss enterprise identification number (UID) from the commercial register (Handelsregister) which may be different from the VAT UID (Mehrwertsteuer UID).
    Example: "CHE123456789"

  - `items.submissionStatus` (string, required)
    Defines if the biller can submit a business-case for the provided ID in the request (=ALLOWED) or if the ID is either not known to the eBill infrastructure or the submission is not allowed (=NOT_ALLOWED).
    Enum: "ALLOWED", "NOT_ALLOWED"

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