API v4 Release Notes — October 15, 2026

Changed

• ⚠ Breaking: sold leads' status is locked on PATCH /v4/customers/{id} — Once a lead is sold, lead_type_id can only be changed to Returned From Buyer. Any other value now returns 422 anchored to lead_type_id. Re-sending the current value still passes. If your integration moves sold leads to another status, return them first.
• customer_payments.check_number is now writable — Set check_number on POST /v4/customer_payments and PATCH /v4/customer_payments/{id} to record a check number, money order number, or wire confirmation (up to 255 characters). A value that looks like a card number returns 422. In SecurityTrax the field appears as Reference on manually recorded payments.
• Customer and lead text fields are trimmed on save — POST and PATCH /v4/customers now strip leading and trailing whitespace from fname, lname, spouse, address1, address2, city, zip, county, cross_street, email, lang, business_name, and business_contact. The response body shows the stored, trimmed values. Existing records are unchanged until they're saved again.