Release Notes

Welcome to the Coperniq API release notes. This section highlights noteworthy changes across endpoints, schemas, and docs.

Recent highlights

  • New: Streamed file uploads for projects/requests/clients with binary‑safe handling
  • New: Catalog items endpoints (CRUD) and forms retrieval
  • Improved: Files can be added to a specific phase in a project or request.
  • Improved: Project manager data is returned when getting a project.

Documentation updates

  • Clarified file upload usage, binary limits, and recommended large-file approach

Looking for a specific date? See the entries below.

September 23, 2025

Today’s release focuses on improving Work Orders creation, tightening schemas, and cleaning up the docs.

What’s new?

  • Create Work Order: You can now create a work order under a specific phase instance using templateId and phaseInstanceId. The response includes id, createdAt, updatedAt, description, position, phaseInstanceId, projectId, and createdById.
  • Full CRUD on Catalog Items: You can now, get, create, update, and delete catalog items in your company settings.
  • Form Retrieval: You can now get forms on a project and get form details.
  • Project Phase Instances: Getting a project by ID now includes the phase instances for that project.

Changes

  • Work Orders
    • POST /projects/{projectId}/work-orders requires templateId and phaseInstanceId.
  • Catalogs & Catalog Items
    • GET /catalog-items returns catalogs with their catalog items.
    • GET /catalog-items/{catalogItemId} returns a catalog item.
    • POST /catalog-items creates a catalog item.
    • PATCH /catalog-items/{catalogItemId} updates a catalog item.
  • Forms
    • GET /projects/{projectId}/forms returns a list of the forms on a project.
    • GET /forms/{formId} returns the form details, including field values.
  • Projects
    • GET /projects/{projectId} includes an array of phaseInstances.

Notes

  • The provided phaseInstanceId must belong to the project where the work order is created.