GET /factura — List the Latest Electronic Invoices

This endpoint retrieves the most recently created electronic invoices registered in the Factus platform. Each item in the returned array is a summary-level bill object containing the invoice number, customer identification, document type, current validation status, and payment form. No query parameters are required — the Factus API returns a default page of the latest invoices.

Endpoint

GET /factura

Request

No request body or query parameters are required. The backend attaches the Bearer token from the server environment automatically — callers do not need to include any Authorization header.

Response

200 — Success

Returns a JSON object with a data array, where each element is a bill summary object.

status

number

HTTP-like status code. Always 200 on success.

message

string

Human-readable result label. Always "OK" on success.

data

array

Array of invoice summary objects. Each element has the following fields:

Show Invoice object fields

number

Internal Factus bill identifier.

document

object

Document type descriptor.

Show document fields

code

string

Document type code (e.g., "01" for Factura electrónica de Venta).

name

string

Human-readable document type name (e.g., "Factura electrónica de Venta").

number

string

Full invoice number including prefix (e.g., "SETP990008805").

api_client_name

string

Email address of the API client that created the invoice.

reference_code

string

Auto-generated unique reference code for this invoice (e.g., "F7G5X8Y9Q9R").

identification

string

Customer identification number.

graphic_representation_name

string

Display name of the customer as it appears on the invoice graphic representation.

company

string

Customer company name (may be empty for natural persons).

trade_name

string

Customer trade name (may be empty).

names

string

Customer full name.

string

Customer email address.

total

string

Invoice grand total as a decimal string (e.g., "50000.00").

status

number

Validation status flag. 0 = unvalidated (not yet sent to DIAN); 1 = validated and sent to DIAN.

errors

array

Array of DIAN validation warning/error strings. Empty when there are no issues.

send_email

number

Whether the invoice was emailed to the customer. 0 = no, 1 = yes.

has_claim

number

Claim indicator. 0 = no claim attached.

is_negotiable_instrument

number

Negotiable instrument flag. 0 = not a negotiable instrument.

payment_form

object

Payment form descriptor.

Show payment_form fields

code

string

Payment form code (e.g., "1").

name

string

Payment form name (e.g., "Pago de contado").

created_at

string

Invoice creation timestamp in the format "DD-MM-YYYY hh:mm:ss AM/PM" (e.g., "23-01-2025 09:16:27 PM").

credit_notes

array

Array of associated credit notes. Empty if none exist.

debit_notes

array

Array of associated debit notes. Empty if none exist.

409 — Conflict

Returned when the Factus API responds but with a status value that does not match the expected "OK" string — for example, if the upstream API returns an unexpected status code or payload shape.

{
  "status": 409,
  "message": "CONFLICT",
  "data": {}
}

500 — Internal Server Error

Returned when an unhandled exception occurs. Two distinct shapes are possible: Shape A — upstream call failure (from request_fact internal catch):

{
  "status": 500,
  "error": "ERROR INTERNO",
  "data": {}
}

Optional extra fields: message (Axios error message), code (Axios error code), error_name (error class name). Shape B — controller-level exception:

{
  "status": 500,
  "messaje": "Hubo un error al intentar realizar la solicitud",
  "error": {}
}

The messaje key (with a j) in Shape B is a known typo in the backend source — handle it as-is when parsing error objects. Shape A uses error as a plain string ("ERROR INTERNO"), not an object.

Example Response (200)

{
  "status": 200,
  "message": "OK",
  "data": [
    {
      "id": 9401,
      "document": {
        "code": "01",
        "name": "Factura electrónica de Venta"
      },
      "number": "SETP990008805",
      "api_client_name": "santiagoriveramarin83 @ gmail.com",
      "reference_code": "F7G5X8Y9Q9R",
      "identification": "123456789",
      "graphic_representation_name": "Tutos Rive",
      "company": "",
      "trade_name": "",
      "names": "Tutos Rive",
      "email": "[email protected]",
      "total": "50000.00",
      "status": 1,
      "errors": [],
      "send_email": 0,
      "has_claim": 0,
      "is_negotiable_instrument": 0,
      "payment_form": {
        "code": "1",
        "name": "Pago de contado"
      },
      "created_at": "23-01-2025 09:16:27 PM",
      "credit_notes": [],
      "debit_notes": []
    },
    {
      "id": 9399,
      "document": {
        "code": "01",
        "name": "Factura electrónica de Venta"
      },
      "number": "SETP990008803",
      "api_client_name": "[email protected]",
      "reference_code": "652342342",
      "identification": "123456789",
      "graphic_representation_name": "alan turing",
      "company": "",
      "trade_name": "",
      "names": "alan turing",
      "email": "[email protected]",
      "total": "6435.00",
      "status": 1,
      "errors": [
        "Regla: FAX14, Notificación: Reporta una tarifa diferente para uno de los tributos enunciados en la tabla 13.3.9",
        "Regla: FAS14, Notificación: No corresponde a un valor valido de la lista"
      ],
      "send_email": 0,
      "has_claim": 0,
      "is_negotiable_instrument": 0,
      "payment_form": {
        "code": "1",
        "name": "Pago de contado"
      },
      "created_at": "23-01-2025 08:45:54 PM",
      "credit_notes": [],
      "debit_notes": []
    }
  ]
}

Code Examples

curl -X GET http://localhost:3000/factura \
  -H "Accept: application/json"

Invoice Endpoints

Database Endpoints

GET /factura — List the Latest Electronic Invoices

Endpoint

Request

Response

200 — Success

409 — Conflict

500 — Internal Server Error

Example Response (200)

Code Examples

Build docs developers (and LLMs) love

Invoice Endpoints

Database Endpoints

Documentation Index

​Endpoint

​Request

​Response

​200 — Success

​409 — Conflict

​500 — Internal Server Error

​Example Response (200)

​Code Examples

Build docs developers (and LLMs) love

Endpoint

Request

Response

200 — Success

409 — Conflict

500 — Internal Server Error

Example Response (200)

Code Examples