We are now available on Zapier enabling easier and quicker no-code integrations between Claimable and the 1,000's of third party tools and services available in the Zapier library.

Our latest release introduces new endpoints to fetch tasks via the Claimable API:

You can now modify closed_at on closed claims. The default value is a timestamp that gets set automatically upon setting status to "closed" (either via the API or as a user via the UI). However you can now override this with another value for closed_at, which will be given precedence if provided.

In addition to the existing GET and POST endpoints for labels, we've now added DELETE so you can remove one or more labels from a claim, contact or company in a single API request.

As part of our Webhooks feature, we've added more events that can trigger a webhook request to your endpoint. You can subscribe to any of these events to receive a HTTP request to a URL of your choosing, whenever the corresponding activity occurs in Claimable.

When fetching claims from our API we now return more metadata about the claim record in the JSON response.

We've just added /users and /users/:id endpoints to our API allowing you to fetch various metadata about the users on your Claimable account, for reporting or monitoring purposes.

We've added /payments and /payments/:id endpoints to make it easier to fetch all claim payments in your Claimable account, without needing to go through the nested payment endpoint (e.g. /claims/:claim_id/payments) to access payment information.

In addition to making requests to our API, you can receive webhook requests sent from Claimable to your own endpoints, as soon as an interesting event occurs. These "webhooks" allow you to build logic to respond immediately when something important happens in your Claimable account, such as a claim being created, assigned or closed.

Our Developer Hub recently got an upgrade, making it even easier explore and try out our API interactively.