Accept a received invoice (SII event)

Registers an acceptance event for a received invoice with the SII
(Registro de Aceptación/Reclamo). Cardda submits the event synchronously using
the company's own approved SII credential, then persists the outcome on the
fiscal invoice.

Action codes

action_code is optional; when omitted it defaults to ACD. If provided, it
must be one of the accept codes:

CodeMeaning
ACDAceptación del contenido del documento.
ERMOtorga recibo de mercaderías o servicios.
ERGRecibo de mercaderías / servicios (variante).

Idempotency

The event is reserved under a row lock: the invoice moves to
sii_event_state: submitting, then submitted on success. A second call while
an event is already in flight or recorded returns 409.

Requires the erp_tradables_manage permission on the invoice's own company
(checked against the invoice, not the company-id header).

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

Composite id of the fiscal invoice, "#{issuer_id}-#{document_type}-#{number}"
(e.g. 76123456-7-33-1234). This is a string, not a UUID.

Body Params
string
enum

Accept action code. Defaults to ACD when omitted.

Allowed:
Headers
uuid
required

UUID of the company on whose behalf the request is made. Fiscal-invoice endpoints
authorize the caller against this company (and read/write its data). SII-key
endpoints never filter their results by this header. On the SII-key list,
however, belonging to the header company is one of the ways a caller is authorized
to make the call (alongside being Cardda staff or passing their own user_id), so
the header is not merely ignored there. On the other SII-key endpoints the header
plays no part in authorization. See The company-id header
for details on how to obtain a value for this header and the error responses to
expect when it is missing or invalid.

Responses

400

The action_code is not valid for an accept event. Body:
{ "error": "Invalid action_code for accept. Allowed: ACD, ERM, ERG" }.
Upstream SII validation errors are also passed through with the SII's own
status (400/401/403) and body.

401

Unauthorized — missing/invalid token, company-id header not set, or the caller lacks erp_tradables_manage on the invoice's company.

404

Fiscal invoice not found. Body: { "message": "Resource not found" }.

409

The invoice already has an SII event in flight or recorded. Body:
{ "error": "Invoice already has SII event" }.

412

The invoice''s company has no approved SII credential whose RUT matches the
company identifier. Body:
{ "error": "No approved SII credentials for this company" }.

Language
Credentials
Bearer
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json