Welcome to the Coperniq API release notes. This section highlights noteworthy changes across endpoints, schemas, and docs.
Recent highlights
- New: Object naming aligned with Coperniq UI — clients are now accounts, requests are now opportunities, and comments are now notes.
- New: Retrieve archived records by passing
include_archived=trueon any GET list or get-by-ID endpoint for projects, opportunities, accounts, and workflows. - New: Form template endpoints —
GET /form-templatesandGET /form-templates/{formTemplateId}— let you retrieve workflow templates and their structure. - New:
PATCH /form-templates/{formTemplateId}— update a form template’s name, layout, assignee, collaborators, labels, and due date configuration. - New: Streamed file uploads for projects and opportunities with binary-safe handling
Documentation updates
- Clarified file upload usage, binary limits, and recommended large-file approach
- Documented full
TradeGroup,ProductCategory, andServiceCategoryenums for catalog items and wired them into the public schemas.
Looking for a specific date? See the entries below.
Naming updates & new features
Object renames
Coperniq’s API terminology now matches the UI:
Existing /{resource}/{id}/comments paths are unchanged — no updates to existing integrations are required. A new unified PATCH /notes/{noteId} endpoint is also available. The renamed terms appear in operation names, tags, and SDK method names going forward.
Retrieve archived records
All GET list and get-by-ID endpoints for projects, opportunities, accounts, and workflows now support an include_archived query parameter.
By default (include_archived=false) only active records are returned — existing behavior is unchanged. Set include_archived=true to include archived records in the response.
Form template endpoints
Two new read-only endpoints let you retrieve form templates and their structure:
GET /form-templates— List all workflow form templates for your company.GET /form-templates/{formTemplateId}— Get a specific form template by ID, including its field definitions.
These are useful for dynamically building form submissions or inspecting available form structures before creating a form instance.
