Like most accounting outputs, the balance can also be generated via the REST API.
The balance is used to determine the balance-reconciliation status of documents. ABRA Flexi groups all sources and payments for the given balance account by the source document number — source documents carry their variable symbol into the matching symbol, and payments, using a linking table, take over the source's variable symbol into the matching symbol.
If you're interested in the documentation for the desktop application, continue to this link.
How to call it
The balance is available using the HTTP method GET at the address /c/{firma}/saldo, where {firma} is the database company identifier.
GET https://demo.flexibee.eu/c/demo/saldo.xml
The output can be further customized using the parameters below. None of them are mandatory, and the URL can also carry general parameters such as pagination or detail level.
Parameters
Parameter | Meaning |
| Payment status of balance records — |
| Filtering by accounts. You can specify accounts, account prefixes, or a range thereof, separated by commas — e.g. |
| Filtering by counter-accounts, using the same notation — e.g. |
| Posting date range in the format |
| Document issue date range in the format |
| Filtering by accounting document modules; the parameter can be repeated. Allowed values: |
| Range of the debit amount in the domestic currency and in the foreign currency, respectively. |
| Range of the credit amount in the domestic currency and in the foreign currency, respectively. |
| Filtering by center, order, or company. The parameters can be repeated; the value uses the import identifier — e.g. |
| Posting status of documents — |
| Full-text filtering by description. |
| Filtering by the document's internal number, variable symbol, or matching symbol. Multiple comma-separated values can be specified. |
⚠️ For parameters with an enumerated set of values (stavUhrady, stavZauctovani, modul), an invalid value results in a 400 unsupported_param_value_exception error, and the server will list the allowed options in the response. Conversely, an unknown parameter name is ignored without an error, so a typo in the name has no visible effect — the filter simply won't be applied.
ℹ️ The parameter modul is written here with the prefix modulUcetni., while for payment status as of a date, only FAV, PHL, FAP and ZAV are used.
Sample calls
GET https://demo.flexibee.eu/c/demo/saldo.xml
GET https://demo.flexibee.eu/c/demo/saldo.xml?stavUhrady=neuhrazeno
GET https://demo.flexibee.eu/c/demo/saldo.xml?stavUhrady=neuhrazeno&filtrUcty=311001,311002
GET https://demo.flexibee.eu/c/demo/saldo.xml?stavUhrady=uhrazeno&filtrUcty=311001&filtrProtiucty=1-2
GET https://demo.flexibee.eu/c/demo/saldo.xml?stavUhrady=neuhrazeno&datumUctovaniOd=2025-01-01&datumUctovaniDo=2025-01-31
GET https://demo.flexibee.eu/c/demo/saldo.xml?stavUhrady=neuhrazeno&datumVystaveniOd=2025-01-01&datumVystaveniDo=2025-01-31
GET https://demo.flexibee.eu/c/demo/saldo.xml?modul=modulUcetni.FAV&modul=modulUcetni.FAP&stredisko=code:CENTRALA&stavZauctovani=zauctovano
GET https://demo.flexibee.eu/c/demo/saldo.xml?castkaMDOd=1000&castkaMDDo=5000&varSymbol=2026001,2026002
Sample output
XML:
<winstrom version="1.0">
<saldo>
<stavUhrK></stavUhrK>
<datVyst>2018-01-08</datVyst>
<datSplat>2018-01-22</datSplat>
<mena evidencePath="mena" showAs="CZK: Česká koruna"
ref="/c/demo/mena/31.xml">code:CZK</mena>
<firma evidencePath="adresar" showAs="4219: Odběratel č. 55"
ref="/c/demo/adresar/654.xml">code:4219</firma>
</saldo>
</winstrom>
JSON:
{
"winstrom": {
"@version": "1.0",
"saldo": [
{
"stavUhrK": "",
"datVyst": "2018-01-08",
"datSplat": "2018-01-22",
"mena": "code:CZK",
"mena@evidencePath": "mena",
"mena@showAs": "CZK: Česká koruna",
"mena@ref": "/c/demo/mena/31.json",
"firma": "code:4219",
"firma@evidencePath": "adresar",
"firma@showAs": "4219: Odběratel č. 55",
"firma@ref": "/c/demo/adresar/654.json"
}
]
}
}