Skip to content

The Special Operations Event (Evento de Operaciones Especiales, 17) reports to the MH, per period, documents that are not DTEs:

  • Simplified sales invoices (tipoDocumento: "02"): always by ranges docDel–docAl.
  • Internal control receipts (tipoDocumento: "97"): one by one (numDocumento + fechaEmision) or by ranges. The two forms can’t be mixed.

It requires dte:emit and supports Idempotency-Key. Prices go without VAT, on simplified invoices too.

{
"tipoDocumento": "02",
"fecha": "2026-10-31",
"items": [
{ "descripcion": "Facturas simplificadas", "docDel": "1", "docAl": "25", "precioUni": 10 }
]
}
  • fecha (YYYY-MM-DD) defines the reported period. Defaults to today; never a future date.
  • Each item: descripcion, precioUni and, depending on the case, cantidad, numDocumento, docDel, docAl, fechaEmision, tipoVenta, codigoGeneracionRef. Up to 2000 items.
  • Voided documents go in a separate event, all with codigoGeneracionRef: the code of the event where they were reported as active.
Ventana de terminal
curl https://app.openfactura.co/api/v1/eventos/operaciones-especiales \
-H "Authorization: Bearer $OPENFACTURA_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: simplificadas-2026-10" \
-d @simplificadas.json

Response: 201 with the Evento (tipo: "operaciones_especiales", tipoEvento: "17"). If the MH rejects it: 422 evento_rechazado. List the ones you sent with GET /eventos?tipo=operaciones_especiales.

If it can’t be confirmed whether the MH received the event (the connection dropped while transmitting it, or the MH stamped it but it couldn’t be saved): 502 evento_incierto with details.codigoGeneracion and, if it was stamped, details.selloRecibido. It’s stored as the final response for the Idempotency-Key. Don’t send it again without checking with the MH first; resend with another key only if it didn’t arrive.

For AI assistants: llms.txt ·llms-full.txt ·every page as Markdown by adding .md to its path.