Create a fiscal sale receipt (async)
curl -X POST https://api.fiscomm.rs/receipt/normal/sale/async \ -H "Authorization: Bearer $FISCOMM_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "orderNumber": "ORDER-1001", "items": [{ "name": "Item", "quantity": 1, "unitPrice": 6000, "totalAmount": 6000, "labels": ["A"] }], "payments": [{ "type": "cash", "amount": 6000 }], "metaFields": {} }'Enqueues a fiscal sale receipt creation request for asynchronous processing. Use this endpoint when you want fire-and-forget behaviour — the receipt is queued and processed in the background. NOTE: the async endpoints may be unavailable on some accounts and can return 500 (ERR_00002); prefer the synchronous endpoints and reconcile with /archive/receipts/fiscalization-lookup. Ideal for high-throughput integrations. buyerId is optional for sale receipts. Requires shop-level access via Bearer token or API key.
Authorizations
Odeljak „Authorizations“Parameters
Odeljak „Parameters“Path Parameters
Odeljak „Path Parameters“Request Bodyrequired
Odeljak „Request Bodyrequired“object
Order number (REQUIRED, cannot be empty). Unique identifier for the transaction within your system. Maps to your internal POS transaction IDs.
Example
1234567890Buyer ID
Example
10:1234567890Referent document number
Example
AAAAA-BBBBB-123Referent document date
Example
2026-11-18T17:30:29.633ZBuyer cost center ID
Example
10:123456789Cashier name
Example
cashierDate time of issue
Example
2026-11-18T17:30:29.633Zobject
Example
Producto 1Example
1234567890Example
1Example
100Example
100Example
[ "F"]Optional. Your own key/values echoed onto the archived receipt (not required).
object
Example
{ "customer_name": "John Doe", "order_id": "12345"}object
Payment type. Accepts both original enum values (Cash, WireTransfer, Card, Check, Voucher, MobileMoney, Virman, Mobile, Factoring, Account, Other) and lowercase alternatives (cash, card, wire_transfer, wiretransfer, check, voucher, mobile_money, mobilemoney, virman, mobile, factoring, account, other)
object
Example
cashExample
100Amount paid in advance (optional, mainly for finalize advance flows)
Example
100Settings for the receipt
object
Skip order number validation. Useful for systems that cannot enforce order number uniqueness. Default: false.
Skip invoice number validation. Useful for special scenarios where fiscal system needs manual invoice number handling. Default: false.
Skip items totalAmount and payment amount validation. Allows for rounding differences or manual calculation handling. Default: false.
Advance finalize only: issue the Avans-Refundacija and the final receipt EXACTLY as provided in the payload, without deriving or adjusting amounts from the advance chain. This also bypasses the chain snapshot (“No advance items … in the chain” guard), so finalization can proceed on historically over-refunded advance chains (Σrefund ≥ Σsale). The caller is fully responsible for the issued amounts. Default: false.
Email address to send the receipt PDF. If provided, receipt will be automatically emailed to this address.
Example
customer@example.comDisplay order number as a barcode block under the receipt. Overrides the shop-level setting for this receipt only. If not provided, falls back to shop receiptSettings.
Optional per-receipt header text rendered in PDF. Overrides shop default header for this receipt.
Optional per-receipt footer text rendered in PDF. Overrides shop default footer for this receipt.
Skip buyer ID validation for refunds. Use this flag only if you cannot provide buyerId for refund transactions (rarely recommended, may violate local regulations). Default: false.
Marks a NORMAL/SALE receipt as finalization of an advance-payment chain. When true, referent document must be an ADVANCE/REFUND receipt.
When true and a receipt with the same orderNumber already exists, the existing receipt is returned (idempotent) instead of throwing ReceiptOrderExistsException. Useful for integrations that retry after a lost response. Default: false.
object
Webhook URL to send data to
Example
https://api.example.com/webhooks/receiptsAdditional headers to include in webhook request
object
Example
{ "Custom-Header": "Value"}HTTP status kodovi koji se smatraju uspehom. Ako je prazno/izostavljeno, prihvata se svaki 2xx.
Example
[ 200, 201, 202]Responses
Odeljak „Responses“object
object
object
object
object
Payment type. Accepts both original enum values (Cash, WireTransfer, Card, Check, Voucher, MobileMoney, Virman, Mobile, Factoring, Account, Other) and lowercase alternatives (cash, card, wire_transfer, wiretransfer, check, voucher, mobile_money, mobilemoney, virman, mobile, factoring, account, other)
object
Amount paid in advance (optional, mainly for finalize advance flows)
object
PURS tax category type code (0 standard, 1/2 special).
Tax label as printed on the receipt (e.g. “Ђ”, “Е”, “F”). Pull valid labels from GET /receipt/tax-rates.
Tax amount for this label.
Tax rate in percent (e.g. 20 for Ђ, 10 for Е).
Tax category name (e.g. “VAT”, “ECAL”).
object
Example
{ "receipt": { "items": [ { "name": "Producto 1", "gtin": "1234567890", "quantity": 1, "unitPrice": 100, "totalAmount": 100, "labels": [ "F" ] } ], "payments": [ { "type": "cash", "amount": 100, "advanceAmount": 100 } ] }}Validation or business-rule error. Branch on code: ERR_00202 (input validation), ERR_00701 (items total ≠ payments total), ERR_01010 (rejected by the Tax Administration).
object
HTTP status code.
Machine-readable Fiscomm error code. Examples: ERR_00202 (validation), ERR_00701 (item total does not match payment total), ERR_00002 (internal error).
Technical message describing the error.
Human-friendly message safe to surface to an end user.
Additional structured detail. For validation errors this includes validationErrors: [{ field, message }].
object
Request path.
Correlation id of the request, for support/log lookups.
Example
{ "status": 400, "code": "ERR_00202", "message": "Validation failed", "details": { "validationErrors": [ { "field": "orderNumber", "message": "should not be empty" } ] }, "path": "/receipt/normal/sale", "correlationId": "5cbf3d9f-bd38-4375-89ab-34ed6be68d97"}Missing or invalid API key.
object
HTTP status code.
Machine-readable Fiscomm error code. Examples: ERR_00202 (validation), ERR_00701 (item total does not match payment total), ERR_00002 (internal error).
Technical message describing the error.
Human-friendly message safe to surface to an end user.
Additional structured detail. For validation errors this includes validationErrors: [{ field, message }].
object
Request path.
Correlation id of the request, for support/log lookups.
Example
{ "status": 401, "code": "ERR_00101", "message": "Failed to validate API token", "correlationId": "5cbf3d9f-bd38-4375-89ab-34ed6be68d97"}The API key is valid but has no access to this shop or resource.
object
HTTP status code.
Machine-readable Fiscomm error code. Examples: ERR_00202 (validation), ERR_00701 (item total does not match payment total), ERR_00002 (internal error).
Technical message describing the error.
Human-friendly message safe to surface to an end user.
Additional structured detail. For validation errors this includes validationErrors: [{ field, message }].
object
Request path.
Correlation id of the request, for support/log lookups.
Example
{ "status": 403, "message": "Forbidden — API key has no access to this shop", "correlationId": "5cbf3d9f-bd38-4375-89ab-34ed6be68d97"}The requested resource does not exist.
object
HTTP status code.
Machine-readable Fiscomm error code. Examples: ERR_00202 (validation), ERR_00701 (item total does not match payment total), ERR_00002 (internal error).
Technical message describing the error.
Human-friendly message safe to surface to an end user.
Additional structured detail. For validation errors this includes validationErrors: [{ field, message }].
object
Request path.
Correlation id of the request, for support/log lookups.
Example
{ "status": 404, "code": "NOT_FOUND", "message": "Resource not found", "correlationId": "5cbf3d9f-bd38-4375-89ab-34ed6be68d97"}Internal error. Safe to retry later.
object
HTTP status code.
Machine-readable Fiscomm error code. Examples: ERR_00202 (validation), ERR_00701 (item total does not match payment total), ERR_00002 (internal error).
Technical message describing the error.
Human-friendly message safe to surface to an end user.
Additional structured detail. For validation errors this includes validationErrors: [{ field, message }].
object
Request path.
Correlation id of the request, for support/log lookups.
Example
{ "status": 500, "code": "ERR_00002", "userMessage": "Server error. Please try again later.", "correlationId": "5cbf3d9f-bd38-4375-89ab-34ed6be68d97"}