Public resource relationships
Connect public customers, products, documents, expenses, and inventory without assuming access to internal records.
Use the public resource IDs returned by Daily. Every related ID must belong to the business bound to the key; changing an ID cannot change business scope.
| Public resource | Relationship and supported workflow |
|---|---|
/business | Read the current business. /business/bank-accounts and /sales-agents provide selectable IDs with business:read; they have no public create or edit routes. |
/customers | Create or update a customer, then use its ID as counterparty_id for a supported sales document. /suppliers provides the equivalent purchasing relationship. |
/leads | POST /leads creates a registration draft. Complete registration in Daily before it appears in lead lists. Converting an existing lead requires leads:write and customers:write. |
/products | Catalog items provide product_id for document lines. Prices in list responses use integer minor units; expanded details and writes use decimal strings in major units. Raw materials are a separate catalog path. |
/document-drafts | Store reviewable draft data. A draft is not an issued document or a numbered accounting record. Issuing through /documents can reference source_draft_id. |
/documents | Read documents, lines, and links, or create a supported document type. Receipt payments are nested in document creation. Issued amounts and numbering cannot be rewritten. |
/payments | Read recorded receipts and their document links. There is no standalone payment creation or card-charge operation on this path. |
/inventory | Read quantities, or set absolute quantities and tracking settings. /inventory/movements lists document-backed movements; it has no direct write or historical delete route. |
/expenses | Expense lines belong to an expense. Approval, voiding, credit allocation, and payment recording use their documented actions and revision checks. |
/expense-payments | Record or reverse expense payments and allocations; this records bookkeeping data and does not initiate a bank transfer. |
/tasks | Create follow-up work and link supported business objects. A task is not a public outbound notification or messaging API. |
/tags | Manage tags and use their IDs in the parent resource fields specified by the reference. |
/imported-documents/morning, /imported-documents/maven | Read imported historical documents separately from newly issued Daily documents. /imported-expenses/morning exposes the supported expense archive. |
The resource map shows lifecycle boundaries. The OpenAPI reference defines exact fields and permissions. The recipes show how to combine these public operations.
The public contract does not expose user administration, API-key management, subscription billing, internal audit storage, arbitrary database access, or a general webhook subscription endpoint. Manage keys in the Daily application and build only against documented public operations.