The actions API gives you programmatic control over every AI-recommended collection action Daylit schedules for your company. Each action represents a suggested outreach step — an email, call, or internal task — attached to an invoice and customer. You can filter the action inbox by category, approve or edit content before sending, and record the outcome after the fact.Documentation Index
Fetch the complete documentation index at: https://help.daylit.com/llms.txt
Use this file to discover all available pages before exploring further.
List actions
UUID of the company whose actions you want to list.
category query parameter to filter by inbox tab.
Query parameters
Preset filter combination. One of:
needs_action— proposed, action-required, AI-recommended actions waiting for your review.awaiting_customer— proposed actions where the AI’s top recommendation is to wait for the customer to respond.history— completed actions and recommended cancelled actions. Soft-deleted actions are included by default.alternatives— all action-required proposed actions for a specific invoice (requiresinvoice_id).
Comma-separated list of statuses to include (e.g.
proposed,scheduled). Applied on top of any category preset.Filter by invoice UUID.
Filter by customer UUID.
Free-text search across action description, recommendation label, trigger event label, customer name, and invoice number.
Include soft-deleted actions. Defaults to
true when category=history.ISO date (
YYYY-MM-DD). Only available when category=history. Filters by executed_at date, falling back to updated_at for actions that were cancelled before execution.ISO date (
YYYY-MM-DD). Only available when category=history.Page number.
Number of results per page.
Response
Total number of matching actions.
Current page number.
Number of results returned.
List of action objects.
Get action detail
UUID of the company.
UUID of the action.
Approve action
proposed or scheduled action, transitioning its status to processing. You can optionally supply edited content and record who approved it.
UUID of the company.
UUID of the action.
Edited content to use instead of the AI-generated draft. Stored in
metadata.final_content.UUID of the
CompanyContact who approved the action.Optional comment recorded in the approval log.
Returns
400 if the action status is not proposed or scheduled.Reject action
UUID of the company.
UUID of the action.
Reason for rejection. Stored in the approval log.
UUID of the
CompanyContact who rejected the action.Optional additional comment.
Returns
400 if the action status is completed.Send action
proposed or scheduled action as completed and records delivery details. Use this endpoint when you send the outreach yourself (e.g. outside Daylit) and want to log the outcome.
UUID of the company.
UUID of the action.
Final content that was sent. Stored in
metadata.final_content.Delivery channel identifier (e.g. email thread ID).
External reference ID for tracking.
ISO datetime after which the action is considered overdue for a response. Must be timezone-aware.
Returns
400 if the action status is not proposed or scheduled, or if response_deadline cannot be parsed.Cancel action
UUID of the company.
UUID of the action.
Reason for cancellation. Stored in the approval log.
UUID of the
CompanyContact who cancelled the action.Complete action
UUID of the company.
UUID of the action.