LIlight
v1 - Invoice Payables

List invoice payables

Deprecated. This route returns a front-end-shaped row and will be removed in a future release. Use GET /v1/invoice-payables instead. It is not a drop-in replacement: it returns a smaller, bill-shaped record and a narrower query vocabulary, so compare the two before migrating. The differences a schema comparison will not show: createdAt is named invoiceCreatedAt, the documentNumber filter is named invoiceNumber, and the embedded vendor details are reduced to vendorId and vendorName — resolve vendorId against GET /v1/vendors/{vendorId} for the rest.

get/v1/bff/invoice-payables

Request

  • Base URL
    https://light.inc (the document declares no server; this is the origin it was published from)
  • Auth
    • API key in header Authorization
    • or HTTP bearer

Query parameters

sortstring

Sort string in the format field:direction. To provide multiple sort fields, separate them with commas.

Available directions: asc, desc.

Available fields: amount, canceledAt, companyEntityName, description, dueDate, fromAccountName, createdAt, invoiceNumber, issuedDate, ocrCompletedAt, paymentAt, senderEmail, state, totalDue, vendorName, businessPartnerName, nextApproverName.

Example:amount:desc,createdAt:asc
filterstring

Filter string in the format field:operator:value. To provide multiple filters, separate them with commas.

Available operators: eq, ne, in, not_in, gt, gte, lt, lte.

  • For in and not_in operators, provide multiple values separated by the pipe character (|).

Available fields: approverUserId, id, vendorId, userId, companyEntityId, senderBankAccountId, amount, description, documentNumber, documentStatus, dueDate, hasWithholding, issuedDate, paymentAt, createdAt, updatedAt, state, vendorName, userFirstName, userLastName, type, selfBilledEinvoiceDeadline, selfBilledEinvoiceStatus.

These fields accept only a subset of the operators: hasWithholding (eq, ne).

Example:state:in:IN_DRAFT|SCHEDULED|PAID,amount:gte:500,vendorId:ne:null
limitinteger

Maximum number of items to return. Default is 50, maximum is 200.

offsetinteger

Number of items to skip before starting to collect the result set. Deprecated, use 'cursor' instead.

cursorstring

The cursor position to start returning results from. To opt-in into cursor-based pagination, provide 0 for the initial request. For subsequent requests, use nextCursor and prevCursor from the previous response to navigate. Cursor values are opaque and should not be constructed manually.

includestring[]

Response

default response

hasMoreboolean

Boolean flag indicating if there are more records available

totalinteger nullable

Total number of records (only for offset pagination). This field is not guaranteed to be returned and only available for offset pagination, please do not rely on it and migrate to cursor pagination.

nextCursorstring nullable

Cursor for fetching the next page (only for cursor pagination)

prevCursorstring nullable

Cursor for fetching the previous page (only for cursor pagination)

Example response

{
  "records": [
    {
      "currency": "USD",
      "vendor": {
        "vendorCurrency": "USD"
      }
    }
  ]
}

Changes

No recorded changes to this operation across all 1 revision of this API.