Pređi na sadržaj
API dokumentacija

Create a fiscal sale receipt (async)

POST
/receipt/{invoiceType}/sale/async
Code sample: curl
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.

invoiceType
required
string
Allowed values: normal training advance proforma copy
Media typeapplication/json
object
orderNumber
required

Order number (REQUIRED, cannot be empty). Unique identifier for the transaction within your system. Maps to your internal POS transaction IDs.

string

Example

1234567890
buyerId
required

Buyer ID

string

Example

10:1234567890
referentDocumentNumber

Referent document number

string
nullable

Example

AAAAA-BBBBB-123
referentDocumentDt

Referent document date

string format: date-time
nullable

Example

2026-11-18T17:30:29.633Z
buyerCostCenterId

Buyer cost center ID

string
nullable

Example

10:123456789
cashier

Cashier name

string
nullable

Example

cashier
dateTimeOfIssue

Date time of issue

string format: date-time
nullable

Example

2026-11-18T17:30:29.633Z
items
required
Array<object>
object
name
required
string

Example

Producto 1
gtin
string

Example

1234567890
quantity
required
number

Example

1
unitPrice
required
number

Example

100
totalAmount
required
number

Example

100
labels
required
Array<string>

Example

[
"F"
]
metaFields

Optional. Your own key/values echoed onto the archived receipt (not required).

object

Example

{
"customer_name": "John Doe",
"order_id": "12345"
}
payments
Array<object>
object
type
required

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

cash
amount
required
number

Example

100
advanceAmount

Amount paid in advance (optional, mainly for finalize advance flows)

number

Example

100
settings

Settings for the receipt

object
skipOrderNumberValidation

Skip order number validation. Useful for systems that cannot enforce order number uniqueness. Default: false.

boolean
skipInvoiceNumberValidation

Skip invoice number validation. Useful for special scenarios where fiscal system needs manual invoice number handling. Default: false.

boolean
skipAmountValidation

Skip items totalAmount and payment amount validation. Allows for rounding differences or manual calculation handling. Default: false.

boolean
skipAdvanceChainDerivation

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.

boolean
sendToEmail

Email address to send the receipt PDF. If provided, receipt will be automatically emailed to this address.

string

Example

customer@example.com
orderNumberUnderReceipt

Display 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.

boolean
textHeader

Optional per-receipt header text rendered in PDF. Overrides shop default header for this receipt.

string
""
textFooter

Optional per-receipt footer text rendered in PDF. Overrides shop default footer for this receipt.

string
""
skipBuyerIdValidation

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.

boolean
isFinal

Marks a NORMAL/SALE receipt as finalization of an advance-payment chain. When true, referent document must be an ADVANCE/REFUND receipt.

boolean
returnIfOrderNumberExists

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.

boolean
webhook
object
url
required

Webhook URL to send data to

string

Example

https://api.example.com/webhooks/receipts
headers

Additional headers to include in webhook request

object

Example

{
"Custom-Header": "Value"
}
successStatusCodes

HTTP status kodovi koji se smatraju uspehom. Ako je prazno/izostavljeno, prihvata se svaki 2xx.

Array<number>

Example

[
200,
201,
202
]
Media typeapplication/json
object
correlationId
required
string
receipt
required
object
id
required
number
invoiceNumber
required
string
invoiceCounter
required
string
buyerId
string
nullable
invoiceNumberPos
string
nullable
referentDocumentNumber
string
nullable
referentDocumentDt
string format: date-time
nullable
invoiceCounterExtension
string
nullable
address
required
string
buyerCostCenterId
string
nullable
businessName
required
string
locationName
required
string
sdcDateTime
required
string format: date-time
qrCodeFileUrl
required
string
invoicePdfUrl
required
string
verificationUrl
required
string
totalAmount
required
number
invoiceType
required
string
transactionType
required
string
orderNumber
string
nullable
cashier
string
nullable
items
required
Array<object>
object
name
required
string
gtin
string
quantity
required
number
unitPrice
required
number
totalAmount
required
number
labels
required
Array<string>
metaFields
required
object
emailSentTo
required
string
payments
required
Array<object>
object
type
required

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
required
number
advanceAmount

Amount paid in advance (optional, mainly for finalize advance flows)

number
taxItems
required
Array<object>
object
categoryType
required

PURS tax category type code (0 standard, 1/2 special).

number
label
required

Tax label as printed on the receipt (e.g. “Ђ”, “Е”, “F”). Pull valid labels from GET /receipt/tax-rates.

string
amount
required

Tax amount for this label.

number
rate
required

Tax rate in percent (e.g. 20 for Ђ, 10 for Е).

number
categoryName
required

Tax category name (e.g. “VAT”, “ECAL”).

string
additional
required
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).

Media typeapplication/json
object
status
required

HTTP status code.

number
code
required

Machine-readable Fiscomm error code. Examples: ERR_00202 (validation), ERR_00701 (item total does not match payment total), ERR_00002 (internal error).

string
message
required

Technical message describing the error.

string
userMessage

Human-friendly message safe to surface to an end user.

string
details

Additional structured detail. For validation errors this includes validationErrors: [{ field, message }].

object
key
additional properties
any
path

Request path.

string
correlationId

Correlation id of the request, for support/log lookups.

string

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.

Media typeapplication/json
object
status
required

HTTP status code.

number
code
required

Machine-readable Fiscomm error code. Examples: ERR_00202 (validation), ERR_00701 (item total does not match payment total), ERR_00002 (internal error).

string
message
required

Technical message describing the error.

string
userMessage

Human-friendly message safe to surface to an end user.

string
details

Additional structured detail. For validation errors this includes validationErrors: [{ field, message }].

object
key
additional properties
any
path

Request path.

string
correlationId

Correlation id of the request, for support/log lookups.

string

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.

Media typeapplication/json
object
status
required

HTTP status code.

number
code
required

Machine-readable Fiscomm error code. Examples: ERR_00202 (validation), ERR_00701 (item total does not match payment total), ERR_00002 (internal error).

string
message
required

Technical message describing the error.

string
userMessage

Human-friendly message safe to surface to an end user.

string
details

Additional structured detail. For validation errors this includes validationErrors: [{ field, message }].

object
key
additional properties
any
path

Request path.

string
correlationId

Correlation id of the request, for support/log lookups.

string

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.

Media typeapplication/json
object
status
required

HTTP status code.

number
code
required

Machine-readable Fiscomm error code. Examples: ERR_00202 (validation), ERR_00701 (item total does not match payment total), ERR_00002 (internal error).

string
message
required

Technical message describing the error.

string
userMessage

Human-friendly message safe to surface to an end user.

string
details

Additional structured detail. For validation errors this includes validationErrors: [{ field, message }].

object
key
additional properties
any
path

Request path.

string
correlationId

Correlation id of the request, for support/log lookups.

string

Example

{
"status": 404,
"code": "NOT_FOUND",
"message": "Resource not found",
"correlationId": "5cbf3d9f-bd38-4375-89ab-34ed6be68d97"
}

Internal error. Safe to retry later.

Media typeapplication/json
object
status
required

HTTP status code.

number
code
required

Machine-readable Fiscomm error code. Examples: ERR_00202 (validation), ERR_00701 (item total does not match payment total), ERR_00002 (internal error).

string
message
required

Technical message describing the error.

string
userMessage

Human-friendly message safe to surface to an end user.

string
details

Additional structured detail. For validation errors this includes validationErrors: [{ field, message }].

object
key
additional properties
any
path

Request path.

string
correlationId

Correlation id of the request, for support/log lookups.

string

Example

{
"status": 500,
"code": "ERR_00002",
"userMessage": "Server error. Please try again later.",
"correlationId": "5cbf3d9f-bd38-4375-89ab-34ed6be68d97"
}