Support for new version of goto API

[valeksa]

Hi,

in email from goto support they said:

---

We want to inform you of two upcoming changes regarding GoTo APIs, which could affect your integrations.
They are:
API host deprecation (api.jive.com) – Replaced by new host (api.goto.com)
Authentication for API tokens -- API Token Migration Guide

GoTo Connect API Host Migration
We are deprecating the old API host api.jive.com and migrating to a new host: api.goto.com. This transition is crucial to ensure uninterrupted service for your end users. The adjustment is needed before our upcoming deprecation timeline of August 28th, 2024, at which point those legacy endpoints will no longer function. Although there is ample time before the deprecation deadline the changes are vital to uninterrupted service for your customers and we encourage you to implement them quickly. After August 28th, 2024, the old host will be officially decommissioned and any integrations utilizing the old host will no longer function. We have a migration guide for the needed host change here.

GoTo API Token Authentication Migration
For increased security and stability, GoTo is deprecating one of the available token authentication services (api.getgo.com) and migrating current users to authenticate with (authentication.logmeininc.com). To achieve uninterrupted service this change is vital, the authorization process using api.getgo.com will be decommissioned August 28th, 2024. The migration needs to be done before that date for authentication to continue to function correctly. We have comprehensive migration guide: Authentication API Token Migration Guide that has steps informing on how to migrate from api.getgo.com to authenticaion.logmeininc.com.

---

We have several project that use your library for accessing goto resources.
I'm intereseted in two things:

1. Do current version of library will have problem to access goto resources considering planned changes from goto?
2. If current version of library do not support new changes, do you plan to implement those changes in your library?

Thanks in advance,
Vladan Aleksic

[slakbal]

Thanks @valeksa I am in the process to re-write the package completely and will see how I can accommodate the new changes.

[slakbal]

Hi @valeksa am I reading it correctly that the date has changed to January 15th, 2025 ?

Also please note the v2 branch on this repo which is basically finished, still need to add tests etc. but it's functioning on my side already.