Numbering series in the API

Without an active series of kind fiscale, issuance returns 409 no_series_configured.

Without an active series of kind fiscale, issuance returns 409 no_series_configured.

← Back to the API documentation

Your first invoice in 6 steps

  1. GET /v1/series lists the numbering series configured for the tenant.
  2. Issuance needs at least one ACTIVE series of kind fiscale.
  3. Without one, POST /v1/invoices returns 409 no_series_configured.
  4. Series are created and activated in the panel, not through the API.

Every endpoint

MethodEndpointScopeIdempotency-KeyRequests / minute
GET/series
List numbering series
invoices:read—120

What the 4invoices API is

bash
curl -sS https://api.4invoices.net/v1/series \
  -H "Authorization: Bearer $ACCESS_TOKEN"

# At least one ACTIVE series of kind "fiscale" must exist, otherwise
# POST /invoices returns 409 no_series_configured.

https://api.4invoices.net/v1 · https://api.4invoices.net/v1/openapi.json

Errors

StatusTypeCode
409conflict_errorno_series_configured

Common mistakes

  • The POST /v1/invoices response carries series and number — log both for reconciliation.
  • A storno consumes a fresh number from the series; the original invoice's number is never reused.
  • Proformas use numbering separate from the fiscal series, so they consume no fiscal numbers.
  • Do not assume a number format: treat number as an opaque string, not an integer.

Developer questions and answers

Can I create a series through the API?

No. The API only reads series. Creating and activating them happens in the panel, because fiscal numbering is a compliance decision.

What if I have several active series?

The default series configured in the panel is used. Issuance does not pick between ambiguous series on its own.

Why is no_series_configured a 409 and not a 422?

It is an account-state conflict, not a problem with the data you sent. Your payload is valid; the configuration is missing.