---
title: "Get one"
method: GET
path: "/v1/fiscal_invoices/{fiscal_invoice_id}"
tags: ["Fiscal Invoice"]
---

# Get one

`GET /v1/fiscal_invoices/{fiscal_invoice_id}`

## Request

- Base URL: `https://api.cardda.com`
- URL: `https://api.cardda.com/v1/fiscal_invoices/{fiscal_invoice_id}`
- Auth: HTTP bearer

Returns a single fiscal invoice (DTE) by its composite id. The response
includes the inline `issuer` and `receiver` projections (`id`, `name`,
`identifier`), the derived `tradable` and `due_date`, and the SII event fields
(`sii_event_state`, `sii_event_status`).

See the id format notes on `GET /v1/fiscal_invoices` — the id looks like
`76123456-7-33-1234` and is a string, not a UUID.

## Path parameters

- `fiscal_invoice_id` string, required

## Parameters

- `#/paths/~1v1~1sii~1keys/get/parameters/0` (unresolved $ref)

## Response `200`

Fiscal invoice

- FiscalInvoice
  - `id` string, required: Unique identifier of the fiscal invoice
  - `document_type` number, required: Type of document (e.g. 33 for invoice, 34 for exempt invoice, 39 for electronic receipt)
  - `company_id` string, uuid, required: ID of the company associated with this invoice
  - `number` string, required: Number of the invoice
  - `issuer_id` string: ID of the entity that issued the invoice, tax identification number for Chilean subjects
  - `receiver_id` string: ID of the entity receiving the invoice, tax identification number for Chilean subjects
  - `issue_type` 'received' | 'issued', required: Whether the invoice was received or issued by the company
  - `total_amount` number, required: Total amount of the invoice
  - `net_amount` number: Net amount of the invoice
  - `currency` string: Currency of the invoice (e.g., CLP)
  - `tax_period` string: Tax period (e.g., MM/YYYY)
  - `expiration_date` string, date-time, nullable: Expiration date of the invoice
  - `created_at` string, date-time: Date and time when the record was synced from IRS
  - `updated_at` string, date-time: Date and time when the record was last updated
  - `cancellation_date` string, date-time, nullable: Date and time when the invoice was cancelled (null if not cancelled)
  - `is_services_invoice` boolean, nullable: Whether the invoice corresponds to a services invoice
  - `service_invoice_status` 'VIG' | 'ANUL', nullable: SII service-invoice acceptance status synced from the upstream document. `VIG` (vigente) means the document is in force; `ANUL` (anulado) means it was annulled. Populated only for invoices in the `is_services_invoice=true` flow; `null` for other invoices or while the backfill has not yet run.
  - `payment_status` string, nullable: Status of payment (e.g., paid, non_paid)
  - `tradable` object, nullable: The ERP payout item (`Erp::Payouts::Tradable` — a payable, receivable, credit note, etc.) Cardda derives from this invoice, serialized inline via the `tradable` method. `null` until a tradable has been created for the invoice.
  - `due_date` string, date-time, nullable: Payment due date, taken from the linked `tradable` (`tradable&.due_date`). `null` when there is no tradable or it has no due date. Rendered via a serializer method, not a stored column.
  - `issuer` object, nullable: Compact projection of the issuer `Person` row (only `id`, `name`, `identifier`), included inline on list and detail responses.
    - `id` string, uuid
    - `name` string, nullable
    - `identifier` string: Tax id (RUT) of the issuer.
  - `receiver` object, nullable: Compact projection of the receiver `Person` row (only `id`, `name`, `identifier`), included inline on list and detail responses.
    - `id` string, uuid
    - `name` string, nullable
    - `identifier` string: Tax id (RUT) of the receiver.
  - `sii_event_status` string, nullable: The action the SII recorded for this document from an accept/reject event (e.g. `ACD`, `RCD`); `null` until an event is submitted. See `POST /v1/fiscal_invoices/{id}/accept_sii_event` and `/reject_sii_event`.
  - `sii_event_state` 'idle' | 'submitting' | 'submitted': Idempotency state of the SII acceptance/rejection lifecycle: `idle` (default), `submitting` (event in flight), `submitted` (recorded).
  - `items` object[]: Line items in the invoice
    - `id` number, required: ID of the item
    - `name` string, required: Name of the item
    - `unit` string, nullable: Unit of measurement
    - `price` number, required: Price per unit
    - `amount` number, required: Total amount for this item
    - `discount` number, nullable: Discount amount
    - `quantity` number, required: Quantity of items
    - `description` string, required: Description of the item
  - `issuer_name` string: Name of the entity that issued the invoice
  - `receiver_name` string: Name of the entity receiving the invoice
  - `referenced_documents` object[]: Referenced documents
    - `number` string, required: Reference document number
    - `document_type` integer, required: Type of referenced document (e.g., 33, 34, 61)
  - `raw_xml` string: Raw XML content of the invoice
  - `counterpart_id` string, uuid: UUID of the counterpart `Person` row Cardda associates with this invoice (the supplier for `received` invoices, the customer for `issued`).
  - `issue_date` string, date-time, required: Date when the invoice was issued
  - `reception_date` string, date-time: Date when the invoice was received in the system
  - `iva_amount` number: IVA (VAT) amount
  - `operation` string: Type of operation (e.g., purchase)

## Other responses

- `401`: Unauthorized — missing/invalid bearer token, `company-id` header not set, or the caller is not a member of the invoice's company. Authorization failures surface as 401 (not 403); Pundit renders `401` with an empty body.
- `404`: Fiscal invoice not found (or not visible to the caller). Body: `{ "message": "Resource not found" }`.

---

[API](https://skmtc.dev/cardda/apis/banking-api.md) - [All operations](https://skmtc.dev/cardda/apis/banking-api/llms.txt) - [OpenAPI document](https://skmtc.dev/cardda/apis/banking-api/revisions/ff1aeb3fda8b?raw)