Known Limitations

There are some known limitations. We will only do minor modifications to the current v2 API, these can be found in our changelog. We'll try to provide you with workarounds when possible in the following list:

Types of Project Services (invoicing methods) (/api/v2/projects/service)

You're only able to create and modify project services where the invoice_method is of type FixedFee or Hours.

Installments

There's currently no support for creating or modifying installments or installment plans.

Webhooks

Webhooks are available but may not cover every change. See the Webhooks documentation for what's supported. If you need to track changes not covered by webhooks, see the use case Tracking Creates and Updates

Tracking Deletions

The only way to see what items have been deleted, is to do a full comparison with data you've stored yourself. When calling the API repeatedly, please keep the Rate Limiting into account, and please limit your selection of fields. Example: use only /api/v2/crm/organization?select=id,name,created_at to make the requests as lightweight as possible.

For very large datasets (like /api/v2/hours/hours), it's more performant to query the id's you've stored directly:

/api/v2/hours/hours
  ?limit=100
  &offset=0
  &select=id,updated_at
  &q[id][in]=hours:abc,hours:xyz

Invoice Services

There's currently no support for Services with regard to invoicing. Invoices created through the API are of the composition type 'lines', meaning you're only able to interact with the invoice lines directly. There's no link between the project services on a project, and the invoice lines. Invoices created through the API will not have a tab for 'Services'.