Feature Requests

Currently the API only allows creating forms on a project with an optional phase input. In the UI a user can create a form on any task/work order, it would be very helpful if this was available via the API as well.

The API allows labelling a Form but not a WorkOrder. This would be very helpful and it would be great to have this parity between object and between API vs UI.

The API allows labelling a Form but not a project. This would be very helpful and it would be great to have this parity between object and between API vs UI.

Currently the API response for the createdByUser on a Task/WorkOrder is not exposed. This is available via UI currently and Forms createdByUser are returned via API. It would be great to have parity.

Expose archived work orders in the "List Work Orders" and in the "Get Work Order" endpoints.

We've had customers ask if there was a fee when using CC, and if we do ever enable CC it would be great to have the fee % clearly visible to the customer so they can make an informed choice.

Would like to have catalog items in Coperniq sync to QBO products.

Some kind of information to the customer that informs them that a payment has been initiated is much needed. We experience customers being unsure whether the payment has been initiated as the customer receives no text box or status change when initiating payment. Payment status does not change until 7 days later when we receive the money in our account. We had a customer overpay a total of six times with two different banks because of this.

It would be helpful to sync the customer's City and State to the QBO Sub-Contact record. Having these fields available directly on the Sub-Contact would make reporting workflows easier.

The ability to toggle Stripe payment methods on/off directly through our Company Settings would be very useful.