Statuses

The seven public statuses

                      ┌───────────► rejected  (terminal)
                      │
queued ──► sent ──────┼───────────► reparo    (terminal-ish; válido pero observado)
   │                  │
   │                  └───────────► accepted ──► annulled (una NC lo anuló)
   │
   └──► failed ──(retry)──► queued

The last column is membership in the consumption ledger, not price: it says whether the document gets recorded there. On a flat plan that is a count, not a charge.

How the SII's signals map

Two SII layers produce these statuses: the envelope status (per upload, by track_id) and the per-document status (getEstDte, by RUT + type + folio + date + amount). We read both and publish a single status.

A document's events

Every transition writes an event you can read and, if you have an endpoint, a webhook.

curl https://api.facturia.cl/v1/documents/doc_01K2R7.../events \
  -H "Authorization: Bearer $FACTURIA_KEY" -H "Facturia-Empresa: $EMPRESA"

{
  "object": "list",
  "data": [
    { "type": "document.created",  "at": "2026-08-14T13:04:11Z", "detail": { "folio": 412 } },
    { "type": "document.sent",     "at": "2026-08-14T13:04:19Z", "detail": { "track_id": "0252083112" } },
    { "type": "document.accepted", "at": "2026-08-14T13:06:55Z", "detail": { "estado": "DOK", "num_atencion": "8812394" } }
  ]
}

Rejection reasons

Rejections come with a structured list, each entry carrying a stable Facturia code, the raw SII code and whether retrying might help.

"rejection_reasons": [
  {
    "code": "ted_signature_invalid",
    "sii_code": "TED-2-510",
    "message": "Firma del timbre electrónico incorrecta",
    "hint": "El DD del timbre fue alterado entre la firma y el envío.",
    "retriable": false
  }
]

The codes you will run into most:

The full dictionary is in Errors · Codes, with a machine-readable copy at GET /v1/error_codes (no authentication).

Polling vs. webhooks

Webhooks are the intended integration. If you have to poll anyway:

• Do not call GET /v1/documents/{document_id} more often than every 10 seconds for the first 2 minutes, then every 60 seconds. Typical time to a terminal status is 30 seconds to a few minutes; the SII can take hours during peaks or maintenance.
• Better: query the list with status=sent&created_at[gte]=… once a minute and reconcile in bulk.
• The Facturia-Poll-After header on the document response tells you the next useful moment, derived from our own scheduler.