Download OpenAPI specification:Download
The API allows you to define the static information found in the header and footer of printed receipts, such as logotype, address, opening hours etc.
A layout consists of:
Inbetween headers and footers are line items. These are not part of a receipt layout entity.
The ordering of the layouts headers/footers will be reflected on the stores' receipts.
Each text- or image-section can be extended with custom properties.
Add a receipt layout
Correlation-Id | string <uuid> Example: fe0aded2-ba52-11eb-a075-e3d570c587ed Id used for tracking a request throughout the system(s). |
businessUnitGroupId required | string Identifier for the business unit group that this layout applies to. |
effectiveDate | string <date> The date when this layout should be applied, if present. It is up to the integrator
to make sure that a current layout exists in the final system, if a layout has a
future effectiveDate set. |
Array of objects (ImagesType) [ items ] | |
required | Array of ImageSection (object) or TextSection (object) (Section) [ items ] A ReceiptLayout consists of Sections. |
{- "businessUnitGroupId": "store-1",
- "sections": [
- {
- "type": "HEADER_IMAGE",
- "value": "string"
}
]
}