Changelog for integrations API

Indholdsfortegnelse

Introduction

In this document you will find descriptions of changes to the Capturi integration API v. 2.0.

We strive to make descriptions of known changes available as soon as possible, but do not guarantee a minimum "response time" for changes.

In most cases we expect descriptions to be available a few weeks in advance of the change, not months.

If you have questions or need help, you can always reach out to our support on support@capturi.com and they will help you.

01.07.24 Removing pagination on fetching conversations

To optimize performance on our integration API’s we just released an update with a new and improved way of fetching data using a “cursor” rather than regular pagination.

This means that you will have to do a slight change in the way you fetch data from Capturi.

Please check out the documentation and examples here:
Doc. - List Full
Doc. - List delta

!!! Deadline !!!
Please note that the old pagination will actively be deprecated as of 1/7 2024, whereafter old request will stop working all together.

01.12.2023 Removal of "questions"

Hi 👋

We are contacting you as a user of the Capturi API endpoints. If you are not the technical go-to for your account, please forward this email to the appropriate IT team/person.

We’d like to inform you of an upcoming breaking change to our conversation model, as we are removing "questions" from our conversation models, which will affect responses from the following API's:

POST /integrations/conversations/list-full
POST /integrations/conversations/list-delta
GET /integrations/conversations/{uid}

The update will take affect December 1st, 2023.

What is changing?

Please view the changes in the attached PDF file.

Questions removal.pdf

46.3 KB

01.12.2023 Changes to Trackers

The following endpoints have breaking changes to their response model:
GET /integrations/trackers
GET /integrations/trackers/{uid}
words, speakerId, phrasesSettings and timeFilter will be removed from the response model.

These fields can instead be found on the new speech value.

Please note that the speech field maybe be null if the tracker is only configured for text.