API v4 Release Notes — November 4, 2026

Changed

• ⚠ Breaking: customer_id not found is now 404 on action endpoints — POST /v4/calendar_events/schedule (tech and sales appointments), POST /v4/customer_credit_checks/run, POST /v4/customer_credit_checks/record, POST /v4/customer_payables/generate, and POST /v4/object_udfs/set (customer fields) now return 404 not_found when the customer_id doesn't exist or you can't view that customer or lead. These used to return 422 for a missing customer. A missing or zero customer_id is still 422. If your integration looks for a 422 on an unknown customer, check for 404 as well.
• Customer-owned lists follow your customer visibility — Lists of a customer's records (for example customer_notes, customer_invoices, customer_payments, object_files, object_udfs, lead_contacts) now return only records for customers and leads you can view. Totals and pages match the rows returned. Filtering by a customer_id you can't view returns an empty list.
• beacon_score accepts any score SecurityTrax accepts — On POST and PATCH /v4/customers, beacon_score now takes up to 5 digits with no range check. The old range was 100–1000. Send 0 when no credit was pulled (for example on new construction).
• eDocs Equipment Table values — In electronic_document_field_value, an Equipment Table field's value is JSON, not text: {"columns": [...], "rows": [[...], ...], "overflow": 0}. overflow counts the equipment rows that were summarized on the table's +N more items line instead of printed. Every other field type is still plain text.