The basis of communication with the FlexiBee system is the XML format, which allows you to read all data that FlexiBee offers.
FlexiBee currently provides native FlexiBee XML, its variant in JSON format, and also standard XML for ISDOC invoices.
FlexiBee XML Principles
FlexiBee XML can be used for importing and exporting data, as well as for incremental updates, where the XML file contains only the changed items. This approach serves as the foundation for the FlexiBee REST API technology. Records and relationships can be identified in many ways — from the internal FlexiBee ID, UUID, EAN, and PLU, to custom identifiers (see Record Identifiers).
External ID Principle
Because it is necessary to establish a link between external systems and FlexiBee, the principle of external identifiers can be used. When creating a record in FlexiBee programmatically, you can assign an identifier in the format ext:SHOP:123, where SHOP is the identifier of the external system and 123 is the identifier within that system. A single record can have multiple identifiers, which simplifies communication with the system.
Case Sensitivity
The case of letters in tag and attribute names matters. Tag names for records are always in lowercase, with individual words separated by hyphens (e.g. faktura-vydana, faktura-prijata, typ-dokladu). Tag names for individual properties are in camelCase format (e.g. typDokl, vytvaretKorPol, typPolozkyK).
Example:
<winstrom version="1.0">
<faktura-prijata>
<typDokl>code:FAKTURA</typDokl>
<vytvaretKorPol>false</vytvaretKorPol>
</faktura-prijata>
</winstrom>