Changelog

As part of the continued expansion of our API surface area, we've just released a series of endpoints that makes it easy to fetch records labelled with a given label.

We have added more webhook events that can trigger requests to your endpoints. You can subscribe to any of these events to receive a corresponding HTTP request, with a JSON payload, to a URL of your choosing when a user performs the action in Claimable.

You can now manage branches directly via the Claimable API. Branches are a great way to organise your claims into groups based on the organisational structure of your business, such as by office, location, site, region, department or even team.

We've just released an upgrade to the Claimable API that introduces new endpoints so you can easily fetch all claims for a given contact, company or user. Also, it's now possible to appoint suppliers directly via our API!

We have added new triggers to our Zapier integration to notify you when documents, notes or labels are added to a claim or when a claim is assigned to a user!

We have added a new action to our Zapier integration: update an existing claim! 🚀

We have added 3 new actions to our Zapier integration.

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.