The foundation of communication with ABRA Flexi is ABRA Flexi XML. It can be in either XML or JSON format. In both cases, the structure is identical. The only difference lies in how attributes are stored in JSON. There, they are stored as a record with an at sign: @rowCount.
Important features of ABRA Flexi XML include incremental updates, required attributes, record identifiers, and variable types.
Letter Case
Letter case matters in tag and attribute names.
Record type tag names are always lowercase, with individual words separated by a hyphen (e.g., faktura-vydana, faktura-prijata, typ-dokladu). Property tag names use camelCase format (e.g., typDokl, vytvaretKorPol, typPolozkyK).
Example:
<winstrom version="1.0">
<faktura-prijata>
<typDokl>code:FAKTURA</typDokl>
<vytvaretKorPol>false</vytvaretKorPol>
</faktura-prijata>
</winstrom>
⚠️ Incorrect letter case is the most common reason a value is "silently" not imported — an unknown tag is simply ignored, without causing the import to fail.
Attributes Used
For an overview of the attributes supported by a given record type, refer either to the sample XML (the first record is always commented) or to the documentation for the specific record type. All attributes have internal dependencies, so it's not necessary to include every attribute — the rest are either calculated automatically, inherited from the document type, or determined by another dependency (for example, on an invoice, selecting a company will also fill in the company ID, address, etc.).
💡 You can get a list of properties for a specific record type, including their types and a flag indicating whether they're considered during import, at /c/<identifikátor firmy>/<evidence>/properties.