> ## 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 warehouse outbound receipt > Creates a new warehouse outbound receipt. If you send `clientId`, the existing client is used. If you omit `clientId` and send the `client` object, the backend resolves or creates the client from that payload. The request uses the same stock availability validation as the web, so the endpoint returns `422` when available stock is insufficient. ## OpenAPI ````yaml /en/openapi.yaml post /warehouse-outbound-receipts 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: /warehouse-outbound-receipts: post: tags: - Warehouse Outbound Receipts summary: Create warehouse outbound receipt description: >- Creates a new warehouse outbound receipt. If you send `clientId`, the existing client is used. If you omit `clientId` and send the `client` object, the backend resolves or creates the client from that payload. The request uses the same stock availability validation as the web, so the endpoint returns `422` when available stock is insufficient. operationId: createWarehouseOutboundReceipt parameters: - $ref: '#/components/parameters/IdempotencyKey' requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/WarehouseOutboundReceiptCreateInput' responses: '201': description: Warehouse outbound receipt created. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' Idempotency-Key: description: Original idempotency key when it was provided in the request. schema: type: string Idempotency-Status: description: >- `Original` for the first processed request or `Repeated` when the original response is replayed. schema: type: string enum: - Original - Repeated content: application/json: schema: $ref: '#/components/schemas/WarehouseOutboundReceipt' '422': $ref: '#/components/responses/ValidationError' '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: WarehouseOutboundReceiptCreateInput: description: Payload used to create a warehouse outbound receipt. type: object required: - number - warehouseId - languageId - issueDate - items properties: number: description: >- Warehouse outbound receipt number. If you want to use the next automatic warehouse number, send it explicitly according to the current warehouse numbering series. type: string minLength: 1 maxLength: 20 example: OUT-2026-0001 warehouseId: description: ID of a warehouse. type: integer example: 301 clientId: description: >- Optional ID of an existing client. If you send `clientId`, the `client` object is only used as a snapshot override for this specific receipt. type: - integer - 'null' example: 101 client: description: >- Sparse client payload. If you send `clientId`, it acts as a snapshot override for this receipt. If you omit `clientId`, the backend resolves or creates the client from this payload. anyOf: - $ref: '#/components/schemas/WarehouseOutboundReceiptClientInput' - type: 'null' languageId: description: Language ID from the language lookup endpoint. type: integer example: 1 issueDate: description: Outbound receipt issue date. type: string format: date example: '2026-03-11' note: description: Optional internal note on the outbound receipt. type: - string - 'null' maxLength: 3000 example: Manual stock issue items: description: >- Outbound receipt items. Every line item must target a warehouse-enabled price list item, and the backend validates available stock. type: array minItems: 1 items: $ref: '#/components/schemas/WarehouseReceiptLineInput' WarehouseOutboundReceipt: description: >- Warehouse outbound receipt including warehouse, client snapshot, and items. type: object properties: id: description: Internal warehouse outbound receipt ID. type: integer example: 951 uuid: description: >- Public warehouse outbound receipt UUID also used in the webDoklad URL. type: string example: 3f4c9fdd-6f9b-42c9-8c4b-a9d3a3435cf4 number: description: Warehouse outbound receipt number. type: string example: OUT-2026-0001 webDokladUrl: description: Public web document URL for this outbound receipt. type: string example: >- https://app.fintoro.sk/web-doklad/company/warehouse-outbound-receipt/uuid pdfDownloadUrl: description: Direct URL for downloading the PDF export of this outbound receipt. type: string example: >- https://app.fintoro.sk/api/public/v1/warehouse-outbound-receipts/951/pdf company: $ref: '#/components/schemas/CompanySnapshot' description: Historical supplier snapshot stored on the document. warehouse: $ref: '#/components/schemas/Warehouse' description: Warehouse from which the receipt deducts stock. clientId: description: >- Live client ID when the receipt is still linked to an existing client. type: - integer - 'null' example: 101 client: description: Historical client snapshot stored on the outbound receipt. anyOf: - $ref: '#/components/schemas/ClientSnapshot' - type: 'null' currency: $ref: '#/components/schemas/Currency' description: Outbound receipt currency. language: $ref: '#/components/schemas/Language' description: Outbound receipt language. issueDate: description: Outbound receipt issue date. type: string format: date example: '2026-03-11' note: description: Optional internal note on the outbound receipt. type: - string - 'null' example: Manual stock issue hasVat: description: Indicates whether the outbound receipt contains VAT. type: boolean example: true total: description: Total amount excluding VAT. type: number format: float example: 30 totalWithVat: description: Total amount including VAT. type: number format: float example: 36 items: description: Line items of the warehouse outbound receipt. type: array items: $ref: '#/components/schemas/WarehouseReceiptItem' WarehouseOutboundReceiptClientInput: description: >- Client payload used for resolve-or-create flow or snapshot override on a warehouse outbound receipt. type: object required: - name properties: name: description: Client trade name or personal name. type: string maxLength: 255 example: Client s.r.o. type: description: >- Client type. If omitted, the backend infers it from identifier fields. type: string enum: - person - company example: company subjectId: description: Client business ID when available. type: - string - 'null' maxLength: 40 example: '12345678' taxId: description: Client tax ID when available. type: - string - 'null' maxLength: 40 example: '2020123456' vatId: description: Client VAT ID when available. type: - string - 'null' maxLength: 40 example: SK2020123456 isVatPayer: description: >- Whether the client is a VAT payer. If omitted, the backend infers it from `vatId`. type: boolean example: true email: description: Client contact email. type: - string - 'null' format: email maxLength: 255 example: billing@client.test street: description: Client billing street and number. type: - string - 'null' maxLength: 255 example: Client Street 1 city: description: Client billing city. type: - string - 'null' maxLength: 255 example: Bratislava zip: description: Client ZIP or postal code. type: - string - 'null' maxLength: 10 example: '81101' countryId: type: - integer - 'null' description: >- Billing country ID from the [country reference table](/en/reference-tables#countries). example: 703 WarehouseReceiptLineInput: description: >- One line item of a warehouse inbound or outbound receipt create or update payload. type: object required: - priceListItemId - quantity - unitPrice - vatRate properties: priceListItemId: description: ID of a warehouse-enabled warehouse or price list item. type: integer example: 701 quantity: description: Item quantity. Minimum value is `0.00001`. type: number format: float minimum: 0.00001 maximum: 10000000000000 example: 3 unitPrice: description: Unit price excluding VAT. type: number format: float minimum: -10000000000000 maximum: 10000000000000 example: 15 vatRate: description: VAT rate on the line item in percent. type: number format: float minimum: 0 maximum: 100 example: 20 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 Warehouse: description: >- Warehouse, including inbound and outbound numbering-series configuration. type: object properties: id: description: Internal warehouse ID in Fintoro. type: integer example: 301 name: description: Warehouse name displayed in Fintoro. type: string example: Main warehouse code: description: Internal warehouse code unique within the token scope. type: string example: MAIN-WH inboundNumericalSeriesPattern: description: >- Numbering-series pattern used for warehouse inbound receipts of this warehouse. type: string example: INB-(YY)-(CCCC) inboundNumericalSeriesNextNumber: description: >- Next sequence number that will be used when automatically generating a warehouse inbound receipt. type: integer example: 12 outboundNumericalSeriesPattern: description: >- Numbering-series pattern used for warehouse outbound receipts of this warehouse. type: string example: OUT-(YY)-(CCCC) outboundNumericalSeriesNextNumber: description: >- Next sequence number that will be used when automatically generating a warehouse outbound receipt. type: integer example: 8 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' Currency: description: Currency available in Fintoro API lookup endpoints. type: object properties: id: description: Stable currency ID used across the API. type: integer example: 1 symbol: description: ISO or internal currency symbol. type: string example: EUR name: description: >- Localized currency label. When you send `Accept-Language`, the backend translates this system-owned label accordingly. type: string example: Euro mark: description: Short currency mark displayed in Fintoro. type: string example: € Language: description: Language available in Fintoro API lookup endpoints. type: object properties: id: description: Stable language ID used across the API. type: integer example: 1 name: description: >- Localized language label. When you send `Accept-Language`, the backend translates this system-owned label accordingly. type: string example: Slovak code: description: Short language code. type: string example: sk WarehouseReceiptItem: description: One line item of a warehouse inbound or outbound receipt. type: object properties: id: description: Internal warehouse-document item ID. type: integer example: 7001 priceListItemId: description: ID of the warehouse or price list item. type: integer example: 701 priceListItemName: description: Warehouse or price list item name stored on the document. type: string example: Installation kit priceListItemWarehouseCode: description: Warehouse code of the item when it is set on the item. type: - string - 'null' example: SKU-001 unitName: description: Unit name used on the document. type: - string - 'null' example: pcs quantity: description: Item quantity. type: number format: float example: 3 unitPrice: description: Unit price excluding VAT. type: number format: float example: 15 unitPriceWithVat: description: Unit price including VAT. type: number format: float example: 18 vatRate: description: VAT rate on the line item in percent. type: number format: float example: 20 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: ValidationError: description: Request payload or query parameters failed validation rules. 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: The given data was invalid. errors: type: object additionalProperties: type: array items: type: string 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. ````