> ## Documentation Index > Fetch the complete documentation index at: https://docs.fintoro.sk/llms.txt > Use this file to discover all available pages before exploring further. # Create quotation > Creates a new quotation. ### Recommended flow The recommended happy path is to send `clientId` and `items`. If the client does not exist in Fintoro yet, or you do not want to create it in a separate step, send a `client` object without `clientId`. The backend will try to match an existing client and create a new one only if nothing matches. If you send both `clientId` and a `client` object, the `client` object acts as a sparse snapshot override for this specific quotation. ### How defaults work Most document fields are optional. The backend resolves them in this order: 1. explicit payload value, 2. client defaults, 3. company document settings. In practice this means for example: - `number` and `numericalSeriesId` are resolved from the primary numbering series if you omit them, - `issueDate` defaults to today, - `validityDate` defaults to `issueDate + 30 days`, - `transferTaxLiability` defaults to `false`, - `currencyId`, `languageId`, `note`, and `textAboveItems` can be resolved from client defaults or company document settings. ### How client resolution works Client resolution is strictly deterministic: - if you send `clientId`, the backend loads that client within the token scope, - if you omit `clientId`, the `client` object is used for matching or creation, - if you send both `clientId` and `client`, the `client` object is used only as a document snapshot override. Matching is deterministic and uses this order: - for companies: `vatId`, then `countryId + subjectId`, then `name + email`, then `name + street`, - for people: `name + email`, then `name + street`. ### How item hydration works An item can be created in three ways: 1. as a manual item with explicit name, unit, price, and VAT, 2. via `priceListItemId` and `quantity`, 3. via `priceListItemId` plus sparse overrides for selected fields such as price or name. `priceListItemId` is used only for input hydration. The quotation response returns the final canonical item shape and does not echo this price list reference back as a separate field. Quotations do not use per-item `uuid`; if you send it, the backend ignores it. `warehouseAllocations` are not supported for quotations. The initial quotation status is `waiting`. If you send `Idempotency-Key`, the same key with the same payload returns the original response without creating a second quotation. ## OpenAPI ````yaml /en/openapi.yaml post /quotations openapi: 3.1.0 info: title: Fintoro API v1 version: 1.0.0 description: > Fintoro API v1 is a REST API for integrating Fintoro invoicing, CRM, and warehouse workflows into third-party systems. Production and sandbox companies use the same base URL `https://app.fintoro.sk/api/public/v1`. The bearer token decides which company you work with. The optional `Accept-Language` request header localizes system-owned labels in lookups, in related response objects, and in validation errors. The `Content-Language` response header returns the language used in the response. For onboarding and operational guidance, also see: - [Getting started](/en/getting-started) - [Authentication](/en/authentication) - [Webhooks](/en/webhooks) - [Sandbox testing](/en/sandbox-testing) - [API conventions](/en/conventions) - [Errors and idempotency](/en/errors-and-idempotency) servers: - url: https://app.fintoro.sk/api/public/v1 description: Production Fintoro API. security: - bearerAuth: [] tags: - name: Token identity description: >- Technical read-only endpoint that confirms which company the current bearer token belongs to. - name: Lookups description: >- Read-only lookup endpoints for integration data. These endpoints return lookup datasets with stable IDs that are safe to cache on your side. When new lookup values are added, existing IDs do not change or get reassigned. - name: Numerical Series description: >- Read-only endpoints for numerical series. They return the live configuration used when creating documents, including the next generated document number and variable symbol. - name: Subjects description: Look up and verify subject details before creating a client. - name: Clients description: >- Manage clients, including billing address, delivery address, and client-scoped default values that can be reused when building payloads for new documents. Create, update, and delete operations can emit `clients.created`, `clients.updated`, and `clients.deleted` webhook events. - name: Suppliers description: >- Manage suppliers, including billing address and identifier data used by the warehouse inbound resolve-or-create flow. Create, update, and delete operations can emit `suppliers.created`, `suppliers.updated`, and `suppliers.deleted` webhook events. - name: Business Case Statuses description: >- Manage business-case statuses. Statuses represent pipeline columns. In this API version, a reorder endpoint is not available; when a status is deleted, linked business cases are detached to `null`. Create, update, and delete operations can emit `business-case-statuses.created`, `business-case-statuses.updated`, and `business-case-statuses.deleted` webhook events. - name: Business Cases description: >- Manage business cases, including the nested client or supplier and an optional status. Reorder flows and changing the linked contact through update are not available in this API version. Create, update, and delete operations can emit `business-cases.created`, `business-cases.updated`, and `business-cases.deleted` webhook events. - name: CRM Events description: >- Manage CRM events for `note`, `email`, `phone_call`, and `document_linked`. Attachments use a separate two-step upload endpoint. Create, update, and delete operations can emit `contact-activity-logs.created`, `contact-activity-logs.updated`, and `contact-activity-logs.deleted` webhook events. - name: Bank Accounts description: >- Manage bank accounts, including bank details, primary account state, and open banking metadata. Create, update, and delete operations can emit `bank-accounts.created`, `bank-accounts.updated`, and `bank-accounts.deleted` webhook events. - name: Webhooks description: >- Manage outbound webhook subscriptions for Fintoro API. This section covers subscription CRUD, manual secret rotation, and the delivery payload contract for event-driven integrations. The delivery contract, signature verification, retry behavior, and full event catalog are documented in the [Webhooks guide](/en/webhooks). - name: Warehouses description: >- CRUD operations for warehouses, including inbound and outbound numbering series. Create, update, and delete operations can emit `warehouses.created`, `warehouses.updated`, and `warehouses.deleted` webhook events. - name: Warehouse Inbound Receipts description: >- CRUD operations for warehouse inbound receipts, including warehouse detail, supplier snapshot, receipt items, and `pdfDownloadUrl`. Create, update, and delete operations can emit `warehouse-inbound-receipts.created`, `warehouse-inbound-receipts.updated`, and `warehouse-inbound-receipts.deleted` webhook events. - name: Warehouse Outbound Receipts description: >- CRUD operations for warehouse outbound receipts, including warehouse detail, client snapshot, receipt items, and `pdfDownloadUrl`. Create and update use the same stock-availability validation as the web. Create, update, and delete operations can emit `warehouse-outbound-receipts.created`, `warehouse-outbound-receipts.updated`, and `warehouse-outbound-receipts.deleted` webhook events. - name: Price List Items description: >- CRUD operations for price list and warehouse items. These endpoints return the unit as a nested object, support filtering by name, EAN, warehouse code, price, and stock, and expose the same business contract that Fintoro uses for warehouse tracking, EANs, and purchase prices. Create, update, and delete operations can emit `price-list-items.created`, `price-list-items.updated`, and `price-list-items.deleted` webhook events. Stock changes caused by warehouse inbound and outbound receipts can emit the `price-list-items.stock-updated` webhook event. - name: Document Payments description: >- Payment records for public documents. This section covers listing payments of one document, creating a new payment, showing one payment, and deleting it. Supported document types are `invoice`, `proforma`, `credit-note`, `received-invoice`, and `received-receipt`. Create and delete operations can emit `document-payments.created` and `document-payments.deleted` webhook events. When a newly recorded payment makes a supported document fully paid, Fintoro can also emit the matching `*.paid` event for that document resource. - name: Document Emails description: >- Send supported public documents by email. The endpoint uses a single contract around `documentType` + `documentId`, validates document ownership, and supports `invoice`, `proforma`, `order`, `credit-note`, and `quotation`. - name: Invoices description: >- CRUD operations for invoices. Create, update, and delete operations can emit `invoices.created`, `invoices.updated`, and `invoices.deleted` webhook events. When a recorded payment makes the invoice fully paid, Fintoro can also emit `invoices.paid`. - name: Credit Notes description: >- CRUD operations for credit notes. The contract uses camelCase payloads, a full `PUT` update flow, and an explicit link to the original invoice through `invoiceId`. The credit-note client is always derived from the selected source invoice; `clientId` is not part of the request contract, and inline client resolution or create behavior is not supported here. Create, update, and delete operations can emit `credit-notes.created`, `credit-notes.updated`, and `credit-notes.deleted` webhook events. When a recorded payment makes the credit note fully paid, Fintoro can also emit `credit-notes.paid`. - name: Proformas description: >- CRUD operations for proformas. The contract follows the same philosophy as the public invoice API: camelCase payloads, deterministic client resolve/create behavior, create-like defaults, and a full `PUT` update flow with no patch fallback to the previous persisted document state. Create, update, and delete operations can emit `proformas.created`, `proformas.updated`, `proformas.deleted`, and, when a recorded payment makes the document fully paid, `proformas.paid`. - name: Orders description: >- CRUD operations for orders. The contract uses camelCase payloads, deterministic client resolve/create behavior, create-like defaults, and a full `PUT` update flow with no patch fallback to the previous persisted document state. Create, update, and delete operations can emit `orders.created`, `orders.updated`, and `orders.deleted` webhook events. - name: Quotations description: >- CRUD operations for quotations. The contract uses camelCase payloads, deterministic client resolve/create behavior, create-like defaults, and a full `PUT` update flow with no patch fallback to the previous persisted document state. Create, update, and delete operations can emit `quotations.created`, `quotations.updated`, and `quotations.deleted` webhook events. paths: /quotations: post: tags: - Quotations summary: Create quotation description: > Creates a new quotation. ### Recommended flow The recommended happy path is to send `clientId` and `items`. If the client does not exist in Fintoro yet, or you do not want to create it in a separate step, send a `client` object without `clientId`. The backend will try to match an existing client and create a new one only if nothing matches. If you send both `clientId` and a `client` object, the `client` object acts as a sparse snapshot override for this specific quotation. ### How defaults work Most document fields are optional. The backend resolves them in this order: 1. explicit payload value, 2. client defaults, 3. company document settings. In practice this means for example: - `number` and `numericalSeriesId` are resolved from the primary numbering series if you omit them, - `issueDate` defaults to today, - `validityDate` defaults to `issueDate + 30 days`, - `transferTaxLiability` defaults to `false`, - `currencyId`, `languageId`, `note`, and `textAboveItems` can be resolved from client defaults or company document settings. ### How client resolution works Client resolution is strictly deterministic: - if you send `clientId`, the backend loads that client within the token scope, - if you omit `clientId`, the `client` object is used for matching or creation, - if you send both `clientId` and `client`, the `client` object is used only as a document snapshot override. Matching is deterministic and uses this order: - for companies: `vatId`, then `countryId + subjectId`, then `name + email`, then `name + street`, - for people: `name + email`, then `name + street`. ### How item hydration works An item can be created in three ways: 1. as a manual item with explicit name, unit, price, and VAT, 2. via `priceListItemId` and `quantity`, 3. via `priceListItemId` plus sparse overrides for selected fields such as price or name. `priceListItemId` is used only for input hydration. The quotation response returns the final canonical item shape and does not echo this price list reference back as a separate field. Quotations do not use per-item `uuid`; if you send it, the backend ignores it. `warehouseAllocations` are not supported for quotations. The initial quotation status is `waiting`. If you send `Idempotency-Key`, the same key with the same payload returns the original response without creating a second quotation. operationId: createQuotation parameters: - $ref: '#/components/parameters/IdempotencyKey' requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/QuotationInput' responses: '201': description: The quotation was created. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' Idempotency-Key: description: Original idempotency key when it was sent in the request. schema: type: string Idempotency-Status: description: >- `Original` for the first processing or `Repeated` when the original response is replayed. schema: type: string enum: - Original - Repeated content: application/json: schema: $ref: '#/components/schemas/Quotation' '422': description: >- The request payload failed validation or cannot be processed because of a business rule. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: examples: idempotencyConflict: summary: Idempotency key reused with a different payload value: error: Idempotency-Key reused with different request payload schema: type: object properties: message: type: string example: The given data was invalid. error: type: - string - 'null' example: Idempotency-Key reused with different request payload errors: type: - object - 'null' additionalProperties: type: array items: type: string '429': $ref: '#/components/responses/TooManyRequests' '500': $ref: '#/components/responses/InternalServerError' '503': $ref: '#/components/responses/ServiceUnavailable' components: parameters: IdempotencyKey: name: Idempotency-Key in: header required: false description: >- Optional request identifier for safe retries. Use a unique value for each create request you want to retry safely. schema: type: string example: invoice-create-2026-03-03-001 schemas: QuotationInput: description: >- Payload used to create a quotation. In the common case, sending `clientId` and `items` is enough; the backend can resolve the remaining fields. You must send either `clientId` or the `client` object. type: object required: - items anyOf: - required: - clientId - required: - client properties: number: description: >- Manual quotation number. If omitted, the backend generates it from the numbering series. If you send `number`, do not send `numericalSeriesId` in the same payload. type: - string - 'null' minLength: 1 maxLength: 20 example: '20260001' clientId: description: >- Existing client ID. This is the recommended way to create a quotation. If you also send the `client` object, it is used as a sparse client snapshot override for this specific document. type: - integer - 'null' example: 101 client: description: >- Sparse client payload. If you send `clientId`, it acts as a snapshot override for this document. If you omit `clientId`, the backend uses these values to match or create a client. anyOf: - $ref: '#/components/schemas/QuotationClientInput' - type: 'null' businessCaseId: description: >- Optional business case ID. When sent, it must be available in the token scope and to the client resolved as the final `clientId`. type: - integer - 'null' example: 701 numericalSeriesId: description: >- Numbering series ID. If omitted together with `number`, the primary numbering series for quotations is used. If you send `numericalSeriesId`, do not send manual `number` in the same payload. type: - integer - 'null' example: 12 issueDate: description: >- Issue date in `Y-m-d` format. It must be after `2009-01-01` and before the date one year in the future. If omitted, today is used. type: string format: date example: '2026-03-03' validityDate: description: >- Validity date in `Y-m-d` format. It must be equal to or later than the final `issueDate`. If omitted, `issueDate + 30 days` is used. type: - string - 'null' format: date example: '2026-04-02' discountType: description: Document-level discount type. type: - string - 'null' enum: - percentage - fixed example: percentage discountValue: description: Document-level discount value. type: - number - 'null' format: float minimum: 0 example: 10 transferTaxLiability: description: Reverse-charge flag. If omitted, `false` is used. type: boolean example: false currencyId: type: integer description: >- Currency ID from the [currency reference table](/en/reference-tables#currencies). Resolution priority is payload -> client preference -> company document settings. example: 1 languageId: type: integer description: >- Language ID from the [language reference table](/en/reference-tables#languages). Resolution priority is payload -> client preference -> company document settings. example: 1 note: description: >- Document note. Resolution priority is payload -> client preference -> company document settings. type: - string - 'null' maxLength: 3000 example: This quotation is valid for 30 days. textAboveItems: description: >- Text displayed above items. Resolution priority is payload -> client preference -> company document settings. type: - string - 'null' maxLength: 3000 example: Thank you for your interest. items: description: >- Quotation items. This field is always required. Per-item `uuid` is not part of the request contract; if you send it, the backend ignores it. `warehouseAllocations` are not supported for quotations. type: array minItems: 1 maxItems: 100 items: $ref: '#/components/schemas/QuotationItemInput' Quotation: description: Quotation. type: object properties: id: type: integer example: 601 uuid: type: string example: 6b1b8c9e-66e6-4fb5-b2db-6d7c7f0f8f19 type: type: string example: quotation number: type: string example: '20260001' webDokladUrl: type: string format: uri description: Absolute URL of the public web document for this quotation. example: >- https://app.fintoro.sk/web-doklad/cp/4f3f8a95-5c4a-4c8b-9e6c-8a0c1a5df3a1 pdfDownloadUrl: type: string format: uri description: >- Absolute URL of the Fintoro API endpoint that downloads this quotation PDF as an attachment. example: https://app.fintoro.sk/api/public/v1/quotations/601/pdf company: $ref: '#/components/schemas/CompanySnapshot' description: Supplier snapshot stored directly on this document. clientId: description: Live ID of the client linked to the quotation. type: integer example: 101 client: $ref: '#/components/schemas/ClientSnapshot' description: Historical client snapshot stored directly on this document. issueDate: type: string format: date example: '2026-03-03' validityDate: type: - string - 'null' format: date example: '2026-04-02' businessCaseId: type: - integer - 'null' description: >- Optional business case ID. When sent, it must belong to the client selected on the document. example: 701 discountType: type: - string - 'null' enum: - percentage - fixed example: percentage discountValue: type: - number - 'null' format: float example: 10 transferTaxLiability: type: boolean example: false numericalSeriesId: type: - integer - 'null' example: 12 currencyId: type: integer description: >- Currency ID from the [currency reference table](/en/reference-tables#currencies). example: 1 languageId: type: integer description: >- Language ID from the [language reference table](/en/reference-tables#languages). example: 1 note: type: - string - 'null' example: This quotation is valid for 30 days. textAboveItems: type: - string - 'null' example: Thank you for your interest. itemsTotal: type: number format: float example: 200 itemsTotalWithVat: type: number format: float example: 240 total: type: number format: float example: 200 totalWithVat: type: number format: float example: 240 status: type: string enum: - waiting - accepted - rejected example: waiting hasVat: type: boolean example: true items: type: array items: $ref: '#/components/schemas/QuotationItem' QuotationClientInput: description: >- Sparse client payload used when creating or updating a quotation. If you send `clientId`, this object acts only as an optional snapshot override for this specific document. If you omit `clientId`, the backend tries to find an existing client from this object or creates a new one. allOf: - $ref: '#/components/schemas/InvoiceClientInput' QuotationItemInput: description: >- Payload of a single quotation item. Three modes are supported: a manual item, `priceListItemId + quantity`, or `priceListItemId` with sparse overrides for selected fields. `quantity` is always required. If you do not send `priceListItemId`, you must send `name`, `unitPrice`, and `vatRate`. `unitId` is optional; when you omit it for a manual item, the backend defaults to unit `1` (`piece` / `Unit::Piece`). If you do send `priceListItemId`, the backend can hydrate the name, unit, price, and VAT rate from the price list item and the payload acts only as a sparse override. `uuid` is not part of the quotation request contract; if you send it, the backend ignores it. `warehouseAllocations` are not supported for quotations. type: object required: - quantity anyOf: - required: - priceListItemId - required: - name - unitPrice - vatRate properties: name: description: >- Item name. Required for manual items. When using `priceListItemId`, this can override the hydrated name. type: - string - 'null' maxLength: 255 example: Consulting description: description: >- Optional item description. When using `priceListItemId`, this can override or supplement the hydrated description. type: - string - 'null' maxLength: 1000 example: Monthly consulting package unitPrice: description: >- Unit price excluding VAT. Required for manual items. When using `priceListItemId`, this can override the hydrated price. type: - number - 'null' format: float minimum: -10000000000000 maximum: 10000000000000 example: 100 unitId: description: >- Optional unit ID from the [unit reference table](/en/reference-tables#units). For a manual item, if you omit it, the backend uses unit `1` (`piece` / `Unit::Piece`). When using `priceListItemId`, this can override the hydrated unit. type: - integer - 'null' example: 1 quantity: description: >- Item quantity. This field is always required regardless of whether the item is manual or hydrated from a price list item. type: number format: float minimum: 0.00001 maximum: 1000000 example: 2 vatRate: description: >- VAT rate in percent. Required for manual items. When using `priceListItemId`, this can override the hydrated VAT rate. type: - number - 'null' format: float minimum: 0 maximum: 100 example: 20 discountType: description: >- Item-level discount type. Allowed values are `percentage` and `fixed`. type: - string - 'null' enum: - percentage - fixed example: percentage discountValue: description: >- Item-level discount value. If you send `discountType`, you must also send this field. type: - number - 'null' format: float minimum: -10000000000000 maximum: 10000000000000 example: 10 discountName: description: >- Item-level discount label. If you omit it while sending `discountType` and `discountValue`, the backend fills a localized default such as `Zľava` based on the document language. type: - string - 'null' maxLength: 255 example: Loyalty discount priceListItemId: description: >- Price list item ID. When sent, the backend can hydrate the name, unit, price, and VAT rate from that price list item and the payload can act only as a sparse override. type: - integer - 'null' example: 501 CompanySnapshot: description: >- Supplier snapshot stored directly on the document. This object represents the company details exactly as they existed when the document was issued or last re-saved, so the original supplier name, identifiers, and address remain preserved on the document. type: object properties: name: description: Supplier company name stored on the invoice. type: string example: Fintoro s.r.o. subjectId: description: Supplier business ID stored on the invoice. type: string example: '12345678' legalForm: description: Supplier legal form stored on the invoice. type: string example: Limited liability company taxId: description: Supplier tax ID stored on the invoice when it was available. type: - string - 'null' example: '2020123456' vatId: description: Supplier VAT ID stored on the invoice when it was available. type: - string - 'null' example: SK2020123456 vatPayerTypeId: description: Supplier VAT payer type stored on the invoice. type: integer example: 4 country: description: Supplier country stored on the invoice as a plain text value. type: string example: Slovakia city: description: Supplier city stored on the invoice. type: string example: Bratislava street: description: Supplier street and house number stored on the invoice. type: string example: Main Street 1 zip: description: Supplier ZIP or postal code stored on the invoice. type: - string - 'null' example: '81101' registrationCourt: description: >- Supplier registration court stored on the invoice, when it was available. type: - string - 'null' example: City Court Bratislava III registrationNumber: description: >- Supplier registration number stored on the invoice, when it was available. type: - string - 'null' example: 12345/B email: description: Supplier contact email stored on the invoice. type: - string - 'null' example: support@fintoro.sk phone: description: Supplier contact phone stored on the invoice. type: - string - 'null' example: '+421900000000' web: description: Supplier website stored on the invoice. type: - string - 'null' example: https://fintoro.sk ClientSnapshot: description: >- Historical client snapshot stored directly on the document. This object represents the client data exactly as it existed when the document was issued or last re-saved. If the client changes later, for example the name or billing address, the document keeps this historical value for auditability and long-term data persistence. Example: a document issued to `Main Street 1, Bratislava` remains historically correct even if the client profile now contains a different billing address. type: object properties: name: description: >- Person name or company name stored on the invoice at that moment in time. type: string example: Acme s.r.o. type: description: Client type stored on the invoice. type: string example: company subjectId: type: - string - 'null' description: >- Business ID of the client or company. For Slovak entities, you can typically also find this value through the [subject registry lookup](#operation/searchSubjects). example: '12345678' taxId: description: Tax ID stored on the invoice when it was available. type: - string - 'null' example: '2020123456' vatId: description: VAT ID stored on the invoice when it was available. type: - string - 'null' example: SK2020123456 isVatPayer: description: >- Indicates whether the client was marked as a VAT payer when this snapshot was stored. type: boolean example: true email: description: Client contact email stored on the invoice. type: - string - 'null' example: billing@acme.test street: description: Billing street and house number stored on the invoice. type: - string - 'null' example: Main Street 1 city: description: Billing city stored on the invoice. type: - string - 'null' example: Bratislava zip: description: Billing ZIP or postal code stored on the invoice. type: - string - 'null' example: '81101' countryId: description: >- Country ID from the [country reference table](/en/reference-tables#countries). type: - integer - 'null' example: 703 country: description: Billing country stored on the invoice as a nested object. anyOf: - $ref: '#/components/schemas/Country' - type: 'null' hasDeliveryAddress: description: >- Indicates whether this snapshot contains a separate delivery address. type: boolean example: true deliveryStreet: description: Delivery street and house number stored on the invoice. type: - string - 'null' example: Warehouse 9 deliveryCity: description: Delivery city stored on the invoice. type: - string - 'null' example: Kosice deliveryZip: description: Delivery ZIP or postal code stored on the invoice. type: - string - 'null' example: '04001' deliveryCountryId: description: >- Country ID from the [country reference table](/en/reference-tables#countries). type: - integer - 'null' example: 703 deliveryCountry: description: Delivery country stored on the invoice as a nested object. anyOf: - $ref: '#/components/schemas/Country' - type: 'null' QuotationItem: description: Single quotation line item. type: object properties: id: type: integer example: 1 name: type: string example: Consulting description: type: - string - 'null' example: Monthly consulting package unitPrice: type: number format: float example: 100 unitId: description: Unit ID from the [unit reference table](/en/reference-tables#units). type: integer example: 1 quantity: type: number format: float example: 2 vatRate: type: number format: float example: 20 discountName: type: - string - 'null' example: Loyalty discount discountType: type: - string - 'null' enum: - percentage - fixed example: percentage discountValue: type: - number - 'null' format: float example: 10 total: type: number format: float example: 200 totalWithVat: type: number format: float example: 240 InvoiceClientInput: description: >- Sparse client payload used during invoice create or update. When you send `clientId`, this object acts as an optional snapshot override only for the specific document. When `clientId` is omitted, the backend tries to match an existing client or create a new one from this payload. type: object properties: name: description: >- Company name or person name. This field is required when `clientId` is not provided. type: string maxLength: 255 example: Acme s.r.o. type: description: >- Client type. Allowed values are `person` and `company`. If omitted, the backend infers it from the identification fields. type: string enum: - person - company example: company subjectId: description: Business ID of the client or company. type: - string - 'null' maxLength: 40 example: '12345678' taxId: description: Tax ID of the client or company. type: - string - 'null' maxLength: 20 example: '2020123456' vatId: description: VAT ID of the client or company. type: - string - 'null' maxLength: 20 example: SK2020123456 isVatPayer: description: >- Optional VAT payer flag. If omitted and `vatId` is provided, the backend derives it automatically. type: boolean example: true email: description: Client contact email. type: - string - 'null' format: email maxLength: 255 example: billing@acme.test street: description: >- Billing street of the client. With sparse overrides it changes only the snapshot stored on this document. type: - string - 'null' maxLength: 255 example: Main Street 1 city: description: Billing city of the client. type: - string - 'null' maxLength: 255 example: Bratislava zip: description: Billing ZIP or postal code of the client. type: - string - 'null' maxLength: 20 example: '81101' countryId: description: >- Country ID from the [country reference table](/en/reference-tables#countries). type: - integer - 'null' example: 703 hasDeliveryAddress: description: >- Optional delivery address flag. If omitted, the backend can infer it from the delivery address fields. type: boolean example: true deliveryStreet: description: Delivery street stored in the snapshot for this document. type: - string - 'null' maxLength: 255 example: Warehouse Street 5 deliveryCity: description: Delivery city stored in the snapshot for this document. type: - string - 'null' maxLength: 255 example: Trnava deliveryZip: description: >- Delivery ZIP or postal code stored in the snapshot for this document. type: - string - 'null' maxLength: 20 example: '91701' deliveryCountryId: type: - integer - 'null' description: >- Country ID of the delivery address from the [country reference table](/en/reference-tables#countries). example: 703 Country: description: >- Country available in Fintoro API lookup endpoints and in nested objects where the country is returned directly in the response. type: object properties: id: description: Stable country ID used across the API. type: integer example: 703 name: description: >- Localized country label. When you send `Accept-Language`, the backend translates this system-owned label accordingly. type: string example: Slovakia code: description: Two-letter ISO country code. type: string example: SK eu: description: Indicates whether the country is part of the European Union. type: boolean example: true headers: XRequestId: description: >- Unique request identifier used for tracing, audit logs, and support diagnostics. schema: type: string example: req_public_api_01 ContentLanguage: description: Language selected for the request based on `Accept-Language`. schema: type: string example: en responses: TooManyRequests: description: >- The company exceeded the Fintoro API rate limit. This 429 response includes the same `X-RateLimit-Limit` and `X-RateLimit-Remaining` headers as other throttled responses and additionally adds `Retry-After` and `X-RateLimit-Reset`. If you need a higher limit, contact info@fintoro.sk for custom enterprise terms. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' X-RateLimit-Limit: description: >- Maximum number of requests allowed for the company in the current 60-second window. This header is returned on all throttled responses, not only on 429. schema: type: integer example: 120 X-RateLimit-Remaining: description: >- Number of requests remaining for the company in the current 60-second window. This header is returned on all throttled responses, not only on 429. schema: type: integer example: 0 Retry-After: description: >- Number of seconds after which you can safely retry the request. This header is sent only on 429 responses. schema: type: integer example: 60 X-RateLimit-Reset: description: >- Unix timestamp when the current rate-limit window resets. This header is sent only on 429 responses. schema: type: integer example: 1774810800 content: application/json: schema: type: object properties: message: type: string example: Too Many Attempts. InternalServerError: description: >- An unexpected internal error occurred. This should not happen in normal operation and is automatically reported to us. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' Content-Language: $ref: '#/components/headers/ContentLanguage' content: application/json: schema: type: object properties: message: type: string example: Server Error ServiceUnavailable: description: >- The API is temporarily unavailable during scheduled maintenance. We announce planned downtime at least 24 hours in advance. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' Content-Language: $ref: '#/components/headers/ContentLanguage' content: application/json: schema: type: object properties: message: type: string example: Service Unavailable securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: Token description: Bearer token created for a specific company in Integrations → API. ````