The invoices endpoints give you full programmatic access to your AR invoice data in Daylit. You can list and filter invoices across multiple dimensions — status, aging bucket, due date, customer, and more — create new invoice records, update individual or bulk sets of invoices, and trigger payment reminder notifications. All endpoints are scoped to aDocumentation Index
Fetch the complete documentation index at: https://help.daylit.com/llms.txt
Use this file to discover all available pages before exploring further.
company_id.
List invoices
cursor), the response includes a count of matching records and a facets breakdown by status. Pass the returned next_cursor to fetch subsequent pages.
Path parameters
UUID of the company whose invoices you want to list.
Query parameters
Filter by invoice status. Supports comma-separated values for multi-select (e.g.,
current,overdue). Accepted values: current, overdue, past_due_1_30, past_due_31_60, past_due_61_90, past_due_90p, closed_paid, closed_overpaid, closed_credit_memo, closed_written_off. Pass any or omit to return all.Filter by AR aging bucket. Supports comma-separated values (e.g.,
1_30,31_60). Accepted values: current, 1_30, 31_60, 61_90, 91_over. Status is calculated dynamically from the current date — not from a stored field.UUID of a specific customer. Returns only that customer’s invoices.
ISO 8601 date (YYYY-MM-DD). Returns invoices with
due_date on or after this date.ISO 8601 date (YYYY-MM-DD). Returns invoices with
due_date on or before this date.Pass
true to return only invoices with a positive balance whose due_date is in the past.Case-insensitive partial match against invoice number or customer name.
UUID of a team member. Filters invoices belonging to customers assigned to that AR owner.
UUID of a team member. Filters invoices belonging to customers assigned to that sales owner.
Pass
true to return invoices for individual person contacts only. Pass false for company accounts.Comma-separated list of label UUIDs. Returns invoices matching any of the given labels (OR semantics).
Pass
true to exclude invoices with a zero balance.Pass
customer to return aggregated parent rows grouped by customer instead of individual invoice rows.Pass
children together with group_by=customer and a customer_id to fetch the individual invoice rows within a grouped parent. Requires customer_id.Field to sort by. Accepted values:
due_date, balance, amount, customer_name. Combine with order or append _asc / _desc (e.g., balance_desc).Sort direction:
asc or desc.Maximum number of invoices to return per page. Capped at
500.Opaque cursor returned as
next_cursor from a previous response. Omit on the first request.Response fields
Total invoices matching the applied filters. Only present on the first page (no
cursor).Counts of invoices broken down by status bucket. Only present on the first page. Useful for rendering filter badges.
The page size used for this response.
true when additional pages are available.Pass this value as
cursor on your next request. null when you have reached the last page.Echo of all filters active for this request.
Array of invoice objects for the current page.
Example
Create an invoice
HTTP 201 with the created invoice. When paid_amount or balance is omitted, the API initializes both from total_amount.
Path parameters
UUID of the company.
Request body
UUID of the customer this invoice belongs to.
Original invoice amount.
Payment due date in
YYYY-MM-DD format.Invoice issue date in
YYYY-MM-DD format.Invoice number as shown to customers.
URL to the payment portal for this invoice.
Date (
YYYY-MM-DD) for the next scheduled follow-up on this invoice.Example
Get an invoice
Path parameters
UUID of the company.
UUID of the invoice to retrieve.
Response fields
The detail response includes all fields from the list response, plus:The scheduled dunning plan for this invoice. Each entry describes a planned or completed touchpoint with its step, scheduled date, channel, and status. Only present when a collection program is active on this invoice.
true when this invoice is a progress billing invoice linked to a parent invoice.UUID of the parent invoice for progress billing, or
null.Percentage of the parent contract billed by this progress invoice, or
null.Transaction type as classified by the accounting system.
UUID of the customer location associated with this invoice, or
null.Example
Update an invoice
PATCH to update individual fields. Use PUT to replace the full record. You can atomically update label assignments by including label_ids in the PATCH body.
Path parameters
UUID of the company.
UUID of the invoice to update.
Request body (PATCH)
Updated due date in
YYYY-MM-DD format.Updated pay link URL.
Updated follow-up date in
YYYY-MM-DD format.Array of label UUIDs to assign. Replaces the invoice’s current label set entirely.
Example
Invoice AR summary
Path parameters
UUID of the company.
Example
Bulk update invoices
Path parameters
UUID of the company.
Request body
Array of invoice UUIDs to update.
Object of field-value pairs to apply to all invoices in
invoice_ids. Supports any writable invoice field (e.g., next_follow_up_date, payment_link).Array of label UUIDs to add to all invoices in
invoice_ids. Existing labels are preserved.Array of label UUIDs to remove from all invoices in
invoice_ids.Response fields
Number of invoice records updated.
Example
Bulk send payment reminders
queued status once the job is accepted.
Path parameters
UUID of the company.
Request body
Array of invoice UUIDs to send reminders for.
Response fields
Always
queued when the request is accepted.Echo of the invoice UUIDs that were queued.
Human-readable confirmation message.
Example
List payments on an invoice
Path parameters
UUID of the company.
UUID of the invoice.
Response fields
Total number of payments for this invoice.
Array of payment objects. See Get a payment for the full field list.