Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update to new API #65

Closed
ufeindt opened this issue Aug 1, 2023 · 5 comments
Closed

Update to new API #65

ufeindt opened this issue Aug 1, 2023 · 5 comments

Comments

@ufeindt
Copy link

ufeindt commented Aug 1, 2023

v1 / v2 legacy APIs are scheduled to be end-of-lifed on Jan 1, 2024 as per their documentation.

Here's a comparison chart for the new API. I have only just started looking at this tap, so I don't really know what it would take to update it.

@maryanngong
Copy link

Hello! Just wanted to check in on this issue -- it looks like v1/v2 legacy APIs will stop working on June 30, 2024 this year. Does anyone know if this migration is currently being worked on? Thanks!!

@NewAlexandria
Copy link

I wonder how many Stitch / Talend users are relying on this tap, which will fail when the v1 API stops.

@rawcreative
Copy link

@NewAlexandria we definitely are, our data stopped syncing Apr 20. I've personally sent two emails to Stitch's support regarding the issue and haven't received a single response.

@maryanngong
Copy link

@NewAlexandria we definitely are, our data stopped syncing Apr 20. I've personally sent two emails to Stitch's support regarding the issue and haven't received a single response.

I reached out to Stitch's support ~2 weeks ago (because we also use Stitch), and their support team said that they would be doing the upgrade. Specifically they said:

Thank you for your patience.
The Stitch R&D team is aware of the upcoming deprecation of the v1 Klaviyo APIs and they are planning to update the integration to use a newer version.
There is not an ETA on when this change will be implemented, but it will be completed before the deprecation.
Please let me know if there are any other questions or concerns.

So hopefully that means it should be resolved soon. I am planning to wait another ~2-3 weeks and then reach out again if there is still no upgrade live

@rdeshmukh15
Copy link
Contributor

This is the upgrade : #67
And, these changes have been merged to Master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants