Release Notes

Work order update endpoints now accept isActive in the request body. Set isActive: false to archive a work order, or isActive: true to unarchive it — handled independently of any other fields in the same request.

Work order response payloads now also return isActive. The existing isArchived field is deprecated but still returned for backward compatibility — no breaking change.

updated_after/updated_before on GET /projects (v1 and v2), GET /projects/search, and the other v1 list endpoints (requests/deals, clients/accounts, vendors) now also match records whose custom property values changed within the window. This is always on; there is no new query param.

The updatedAt field on a returned record now reflects the most recent change to that record, including changes to its custom property values.

New: Account file endpoints

Manage files on an account, mirroring the existing project/opportunity file endpoints.

Improved: Phase instance timestamps on GET /opportunities/{opportunity_id}

Each entry in phaseInstances now includes startedAt and completedAt, matching the projects endpoint. Use these to compute time-in-stage or close dates without a separate lookup.

• Only populated on GET /opportunities/{opportunity_id}; the list and search endpoints do not return phaseInstances and are unaffected.
• completedAt is null for the phase the opportunity currently occupies and any that have not been started.

New: Utility endpoints

Read and update the global utility list, mirroring the existing AHJ endpoints — utilities are seeded globally with no per-company scoping except for the custom properties.

New: isPrimary and full contact detail

contacts[] on accounts, projects, and opportunities now returns id, name, title, description, emails, phones, and isPrimary for every contact (previously just id/emails/phones on accounts, and nothing at all on projects/opportunities).

• isPrimary is true for exactly one contact — the one at the lowest position (the first element you send on create/update). At most one contact is ever primary.
• Projects and opportunities now return contacts too — their own contacts, independent of and not inherited from the parent account’s. Set them on create/update via the contacts request field, same as accounts. Pass include_contacts=true on GET /projects, GET /projects/search, GET /projects/{project_id}, and the equivalent /opportunities endpoints to include it — same as accounts.
• POST/PATCH responses always include contacts for accounts, projects, and opportunities — not gated behind include_contacts like GET is.

New: Timesheet (time entry) endpoints

Create, read, update, and delete timesheets — time entries logged by a worker against a project, account, or opportunity (and optionally a work order).

New: Bill payment endpoints

Record and retrieve payments against a bill, mirroring the existing invoice payment endpoints.

New: AHJ (Authorities Having Jurisdiction) endpoints

Look up jurisdictions and manage their custom property values through the public API.

Line items can now be grouped into named sections — the same grouping you see on quotes and in the Coperniq UI — across project line items, invoices, and bills.

Envelope product categories

17 new ProductCategory values are now available when creating or updating a catalog item with type=PRODUCT:

ROOF_COVERING, ROOF_UNDERLAYMENT, ROOF_MEMBRANE, ROOF_FLASHING, ROOF_VENT, WALL_CLADDING, WALL_TRIM, WEATHER_BARRIER, WINDOW, EXTERIOR_DOOR, SKYLIGHT, OPENING_FLASHING, GUTTER, DOWNSPOUT, INSULATION, SEALANT, SHEATHING.

Manage labels that can be applied to work orders and assets.

Manage physical assets tied to a site and account. Reads use project-service GraphQL; creates and updates call fleet-service.

You can now create, read, update, delete, send, and download PDF quotes through the public API.

When a project or opportunity has no title of its own (empty string or whitespace-only), the API now returns the parent account’s title in the title field instead of the blank value.

This applies to all read endpoints that return project or opportunity records:

• GET /projects, GET /projects/search, GET /projects/{projectId}
• GET /opportunities, GET /opportunities/search, GET /opportunities/{opportunityId}

New: Bills endpoints

You can now create, read, update, and delete bills on projects via the public API.

New: Work order notes endpoints

You can now create and list notes directly on work orders.

Create a note

Full CRUD support for site records via the public API.

Sites are address/location records that belong to an account. A single account may have multiple sites.

GET /properties — new account and opportunity keys

The /properties response now includes account and opportunity keys in addition to the existing client and request keys:

The record_type query parameter now accepts account and opportunity as values:

Update a form template

A new endpoint lets you update an existing form template:

• PATCH /form-templates/{formTemplateId} — Update a form template’s name, property layout, assignee, collaborators, labels, and due date configuration.

All fields are optional — only provided fields are updated. formLayouts is optional — when provided, it fully replaces all layout groups and their fields; omit it to leave the existing layout untouched. Include existing groups with their id to preserve them, or omit the id for new groups. Groups not included are removed. Array order determines position on the form.