Skip to main content
Fintoro API uses JSON with camelCase field names. PDF endpoints return a file with the application/pdf content type.

Headers

Every request needs an API token. When sending a JSON body, add Content-Type: application/json:

Response format

Lists return a data array. An empty list looks like this:
Detail, create, and update responses return the object directly, without a data wrapper. Lists may contain fewer fields than detail responses; for example, the invoice list does not include line items.

Pagination and filters

Paginated endpoints accept page and perPage and return a paginator object. For example, fetch the first page of invoices:
Abbreviated illustrative response:
nextPageUrl contains the next page’s URL, or null when there are no more pages. Lookup endpoints and some other lists return all results at once, without paginator. Available filters, sort options, and perPage limits are listed for each endpoint in the API reference.

Response language

Use Accept-Language to select the language of system labels and validation errors:
The header affects labels in reference tables and the same objects nested in responses. Client names, notes, and other user-entered data remain unchanged. Supported language tags: sk, en, cs, de, et, es, fr, hr, hu, it, lt, nl, pl, pt, ro, sr, ru, sl, uk. If the header is missing or the language is unsupported, the API uses Slovak (sk). The response’s Content-Language header identifies the selected language. Standard validation messages are in Slovak for both sk and cs, and in English for the other languages listed above. Content-Language identifies the selected request language even when a validation message uses a fallback language.