johnnyq
1a0c984242
API stage 1, the missing operations on the existing resources: invoices can be created with their lines, updated, sent or reminded, marked sent, cancelled and deleted, and invoice lines updated and deleted; quotes created with their lines, updated, sent, marked sent, accepted, declined, invoiced as Invoice does on the quote page and deleted, with new quote_items read, create, update and delete; recurring invoices updated, paused or resumed and deleted, with new recurring_invoice_items read, create, update and delete including lines that count users or devices; expenses created, refunded, updated and deleted; services created, updated, archived, unarchived and deleted; licenses created, updated and deleted; certificates updated, archived, unarchived and deleted; products created, archived, unarchived and deleted; tickets reopened and deleted, ticket replies edited and archived, assets archived and unarchived, documents, domains, networks, vendors and tags deleted, and client portal invites listed and cancelled; each endpoint calls the same functions as its page handler, the line endpoints share billing_lines.php and the new billingLineFromApi() which recurring_invoices/create now uses too, enforce_api_rbac.php maps quote_items and recurring_invoice_items to the Sales module and puts the state changes at Modify, and every delete needs Full; 26.11.9 changelog entries
2026-11-13 22:51:49 -05:00
..
API stage 1, the missing operations on the existing resources: invoices can be created with their lines, updated, sent or reminded, marked sent, cancelled and deleted, and invoice lines updated and deleted; quotes created with their lines, updated, sent, marked sent, accepted, declined, invoiced as Invoice does on the quote page and deleted, with new quote_items read, create, update and delete; recurring invoices updated, paused or resumed and deleted, with new recurring_invoice_items read, create, update and delete including lines that count users or devices; expenses created, refunded, updated and deleted; services created, updated, archived, unarchived and deleted; licenses created, updated and deleted; certificates updated, archived, unarchived and deleted; products created, archived, unarchived and deleted; tickets reopened and deleted, ticket replies edited and archived, assets archived and unarchived, documents, domains, networks, vendors and tags deleted, and client portal invites listed and cancelled; each endpoint calls the same functions as its page handler, the line endpoints share billing_lines.php and the new billingLineFromApi() which recurring_invoices/create now uses too, enforce_api_rbac.php maps quote_items and recurring_invoice_items to the Sales module and puts the state changes at Modify, and every delete needs Full; 26.11.9 changelog entries
2026-11-13 22:51:49 -05:00
Bill sign-ups through the API and follow up when an invoice is paid - a lead that pays an invoice in full becomes a client however it is paid (online, autopay, a recorded payment or a batch), with the new A lead that pays an invoice becomes a client switch in Admin > Settings > Invoices and billing, on by default; a non-billable open ticket tied to an invoice (one raised through the API with ticket_invoice_id, or a quote's tickets once it becomes the invoice) gets an internal note when the invoice is paid in full, goes from On Hold back to Open, and its assigned agent is notified in the app and by email, while billable tickets whose time is on an invoice are left alone; new API endpoints recurring_invoices/create (lines from products or spelled out, the client's currency, frequency, start date, optional first invoice made at once and emailed to the primary and billing contacts, or marked Sent so its link can be paid, the answer including the invoice reference, amount, due date and pay link), recurring_invoices/read and portal_invites/create (sent from the company rather than the key's agent); tickets/create takes ticket_status (an active status other than Resolved and Closed), ticket_invoice_id (one of the client's own invoices) and ticket_notify agents to tell only the team; database 3.5.9 adds settings.config_invoice_paid_lead_to_client; invoicePaidFollowUp() runs from triggerCustomAction() on invoice_pay, with recurringInvoiceCreate(), billingInvoiceIssue() and the paid kind of ticketAgentEmailContent() in support; the Clients list reads each contract's term, so Renews soon shows again and its PHP warning is gone; changelog updated
2026-11-05 19:00:16 -05:00
API stage 1, the missing operations on the existing resources: invoices can be created with their lines, updated, sent or reminded, marked sent, cancelled and deleted, and invoice lines updated and deleted; quotes created with their lines, updated, sent, marked sent, accepted, declined, invoiced as Invoice does on the quote page and deleted, with new quote_items read, create, update and delete; recurring invoices updated, paused or resumed and deleted, with new recurring_invoice_items read, create, update and delete including lines that count users or devices; expenses created, refunded, updated and deleted; services created, updated, archived, unarchived and deleted; licenses created, updated and deleted; certificates updated, archived, unarchived and deleted; products created, archived, unarchived and deleted; tickets reopened and deleted, ticket replies edited and archived, assets archived and unarchived, documents, domains, networks, vendors and tags deleted, and client portal invites listed and cancelled; each endpoint calls the same functions as its page handler, the line endpoints share billing_lines.php and the new billingLineFromApi() which recurring_invoices/create now uses too, enforce_api_rbac.php maps quote_items and recurring_invoice_items to the Sales module and puts the state changes at Modify, and every delete needs Full; 26.11.9 changelog entries
2026-11-13 22:51:49 -05:00