# Submit business case

This operation accepts either a QR-Invoice PDF or a PDF in the eBill Format, containing the business case information as XML attachment included in the PDF. The specific business case type (bill, advice...) is specified in the XML attachment. Ideally the PDF conforms to the PDF/A-3b, if not, conversion is attempted. Please note that PDF format conversion may fail due to various technical reason.

Endpoint: POST /api/v1/business-cases
Version: 1.1
Security: X-API-Key

## Query parameters:

  - `processingMode` (string, required)
    STAGE: BusinessCase gets validated and staged (proceed via web UI), DELIVER: BusinessCase gets validated, processed and delivered to the bill recipient
    Enum: "STAGE", "DELIVER"

## Header parameters:

  - `x-filename` (string)
    Filename for the business case PDF. This is only used for analytical purposes and support. The filename is not visible for the bill recipient. :  :

  - `x-anomaly-detection` (string)
    If the optional header is provided with the value 'SKIP', the anomaly detection does not prevent business case submission

## Request fields (application/pdf):

  - `body` (string)
    PDF as binary data

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