Dev News 19 -- eReceipt API
fiskaly eReceipt API Update
Section titled “fiskaly eReceipt API Update”A major version change to the eReceipt API (version 2.0.0) and updates are planned for Thursday, 23rd March 2023, starting at 2 pm. The new version will be more consistent and reliable, with several bug fixes included.
Changelog
Section titled “Changelog”-
Removal of default values for various schema fields in the CreateReceipt endpoint: For a list of properties (see Table 1 below), the default value 0 will be removed in the CreateReceipt endpoint. For mandatory fields, a value now needs to be provided explicitly. Invalid requests with missing mandatory fields will return error code 400 with the corresponding error message.
-
Removal of the possibility to send additional fields in the CreateReceipt endpoint: The option to send additional properties in various objects in the CreateReceipt endpoint will be removed. Until now, additional fields with any name and any type could be sent. This option will be removed to improve clarity and consistency. See Table 2 below for a list of affected objects. Exception: optional fields remain available for all objects contained in the
EkabsSecurityobject, to allow for flexibility when providing responses from different fiscalization endpoints.
Table 1: Affected schema fields
Section titled “Table 1: Affected schema fields”| Object type | Schema field | Mandatory |
|---|---|---|
| EkabsPaymentType | .amount | yes |
| EkabsLineItem | .quantity | yes |
| .price_per_unit | yes | |
| EkabsLineVatAmountGross | .percentage | yes |
| .incl_vat | yes | |
| EkabsLineVatAmountNet | .percentage | yes |
| .excl_vat | yes | |
| .vat | yes | |
| EkabsVatAmountTotal | .percentage | yes |
| .incl_vat | yes | |
| .excl_vat | yes | |
| .vat | yes | |
| EkabsData | .full_amount_incl_vat | yes |
| Discount | .discount_value | yes |
| EkabsPaymentType | .change | no |
| EkabsData | .full_amount_incl_vat_before_discount | no |
| .total_discount_value | no | |
| HospitalitySchema | .tip | no |
Table 2: Affected schema objects
Section titled “Table 2: Affected schema objects”The property name*: any field was removed from all objects below. The “Schema new” column shows the cleaned-up object without extra properties.
| Object | Fields removed |
|---|---|
| ReceiptSchemaEkabsV0 | property name*: any |
| EkabsData | property name*: any |
| EkabsLine | property name*: any |
| EkabsLineItem | property name*: any |
| EkabsLineVatAmountGross | property name*: any |
| EkabsLineVatAmountNet | property name*: any |
| EkabsPaymentType | property name*: any |
| EkabsVatAmountTotal | property name*: any |
| EkabsHead | property name*: any |
| EkabsBuyer | property name*: any |
| EkabsSeller | property name*: any |
| EkabsMisc | property name*: any |
fiskaly status page: status.fiskaly.com fiskaly support website: support.fiskaly.com
You can contact our support at dev-support@fiskaly.com.
Was this page helpful?