Release Notes

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=true on any GET list or get-by-ID endpoint for projects, opportunities, accounts, and workflows.
  • New: Form template endpoints — GET /form-templates and GET /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, and ServiceCategory enums for catalog items and wired them into the public schemas.

Looking for a specific date? See the entries below.

January 13, 2026

Forms: update & attach files by URL

What’s new?

  • New PATCH /forms/{formId} endpoint lets you update a form’s core fields and responses in one call (status, due dates, collaborators, and individual field values).
  • New POST /forms/{formId}/fields/file-from-url endpoint uploads a file from a public URL and attaches it to a specific FILE-type form field.

Impact

  • Form updates can now be performed via the public API.
  • Integrations can push external documents (e.g. generated PDFs, reports, photos) directly into form fields using a simple URL-based workflow.