/c/<identifikátor firmy>/<evidence>/<ID záznamu>.<výstupní formát>

<company identifier>: unique company identification
<record type>: type of records (address book, order, invoice, …), a complete list can be found here, or you can look up Evidence list directly in your web interface.
<record ID>: record identifier
<output format>: output format (XML, JSON, …). If not specified, the Accept header is taken into account, or the HTML form is returned.

Listing records

If you want a listing of records in a given evidence (see listing), do not specify any record identifier:

/c/<identifikátor firmy>/<evidence>

You can also use filtering:

/c/<identifikátor firmy>/<evidence>/(<filtr>)

Record summarization

If you need to get basic summary information about a given evidence, use summarization:

/c/<identifikátor firmy>/<evidence>/$sum

You can also combine filtering and summarization:

/c/<identifikátor firmy>/<evidence>/(<filtr>)/$sum

Attribute overview

For each evidence, you can get a list of attributes that this evidence supports. This overview takes access rights and licensing into account.

/c/<identifikátor firmy>/<evidence>/properties

Print report overview

For an evidence, you can display a list of supported reports for printing to PDF:

/c/<identifikátor firmy>/<evidence>/reports

Sub-evidence overview

Each evidence can have a sub-evidence (relation). An example would be invoice items or contacts in the address book. These records are usually also accessible directly as evidence. The difference is that the sub-evidence is filtered by the given relation. You can get a list of sub-evidences as follows:

/c/<identifikátor firmy>/<evidence>/relations

Sub-evidences can then be worked with in the same way as evidence:

/c/<identifikátor firmy>/<evidence>/<ID záznamu>/<podevidence>

If you want to also export the sub-evidence of a record when exporting from ABRA Flexi, use the ?relations=vazby,prilohy,bankovniSpojeni parameter.

All supported parameters

ABRA Flexi supports many attributes, and this page describes them.

`?dry-run=true`	Test save (dry-run)
`?fail-on-warning=true`	If a warning occurs, do not save the record (Data validation)
`?report-name=faktura`	Name of the print output when exporting to PDF
`?report-lang=en`	The language in which the print output should be generated when exporting to PDF
`?report-sign=true`	Whether the PDF export should be electronically signed
`?detail=summary`	Definition of the level of detail
`?mode=ruby`	Support for RubyOnRails
`?limit=100`	Pagination
`?start=10`	Pagination
`?order=nazev@A`	Sorting records
`?sort=nazev&dir=desc`	Sorting records for ExtJS
`?add-row-count=true`	Adding the total number of records to the output (Pagination)
`?relations=vazby`	Adding data from a relation (see levels of detail). An overview of relations can be obtained for each evidence (`/relations`).
`?includes=faktura-vydana/stredisko`	Including a related object level of detail
`?use-ext-id=ESHOP,MUJ`	If an object contains an external ID of type ESHOP or MUJ, use it as the linking identifier.
`?use-internal-id=true`	In addition to the `ref` and `showAs` attributes, it also adds the `internalId` attribute to objects, which contains the internal record ID
`?stitky-as-ids=true`	Labels will be both exported and imported not as a list of codes, but as a list of numeric IDs
`?only-ext-ids=true`	The primary key will not be exported; the `<id>` elements will contain only the external ID. Similar to `no-ids`, but it also affects sub-evidences.
`?no-ext-ids=true`	The response will not contain external identifiers (performance optimization)
`?no-ids=true`	The response will not contain any primary identifiers (performance optimization). Affects only the main evidence.
`?code-as-id=true`	If an object has a unique code, it will also be exported (in addition to the `<kod>` element) as `<id>code:...</id>`
`?no-http-errors=true`	If a 4xx error occurs while processing the request, the server will still send 200 OK
`?nastaveni=true`	Export one extra record with the current settings at the beginning as well
`?as-gui=true`	Enables features that add outputs for GUI processing
`?code-in-response=true`	In the response, each object will contain not only the ID and URL, but also the code.
`?add-global-version=true`	The response will contain the global version number current at the time of the export.
`?encoding=iso-8859-2`	Specifies the encoding of the input/output file in CSV format.
`?delimeter=;`	Specifies the delimiter of the input/output file in CSV format.
`?format=awis`	One of the compiled XSL transformations will be applied to the output XML (see `awis` here).
`?auth=http`	Forces login using HTTP authentication, which can, for example, change the default login method in the WUI.
`?auth=html`	Forces authentication using an HTML form. This can be useful for suppressing automatic SSO authentication.
`?skupina-stitku=SKUPINA1,SKUPINA2`	Allows grouping of labels by group during export (more on labels).
`?mode=simple`	The response will not contain comments or additional attributes (e.g. `showAs`, `ref` etc.).
`?access-attribs=true`	Fills in the editability attributes of the record and collections: `editable` indicates the possibility of editing, `deletable` indicates the possibility of deleting, and `insertable` indicates the possibility of adding to the collection.
`?mode=xml_import_export`	A special response format that facilitates data transfers. The response uses Hybrid identifiers and, if needed, splits the export of 1 record into 2 elements (e.g. setting a reference to the main attachment of a user report).
`?xpath=//winstrom/adresar/email/text()`	Allows applying an XPath expression to the resulting XML and returning only the selected part of the output.
`?no-comments=true`	The response will not contain comments on the exported elements.

Building URLs