You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey @taipeicoder we don't have a timeline on updating to API 2.0 for this SDK yet. However, if anybody wants to give it a shot and add support for version 2.0, feel free to jump in and leave a note here so we are all aligned and we don't do double work 😃
We'll let you know here when we start working on it.
Reacted by Nathan Yergler, James Billingham, pkpfr and Vingtoft
This is shockingly unacceptable. We pay over $2,000 a month for your services, and we have to write our own SDK? Please advise why you feel entitled to abandon your Go customers.
Activity
lloydliyu commentedon Jul 22, 2020
Hey @taipeicoder we don't have a timeline on updating to API 2.0 for this SDK yet. However, if anybody wants to give it a shot and add support for version 2.0, feel free to jump in and leave a note here so we are all aligned and we don't do double work 😃
We'll let you know here when we start working on it.
ruudk commentedon Feb 5, 2021
Any news on this? I tried to use the Go SDK today and it took me some time to realize
intercom-go.v2does not work with the V2.x API 🤦Maybe good to add a big warning on top that it's not usable for recent apps?
pkpfr commentedon Jun 19, 2023
This is shockingly unacceptable. We pay over $2,000 a month for your services, and we have to write our own SDK? Please advise why you feel entitled to abandon your Go customers.
uffejaeger commentedon Jul 30, 2026
The big mismatch here is that this client still revolves around the old Users API. Intercom moved that workflow to Contacts.
I’ve been working on a new Go client that targets API 2.15:
https://github.com/uffejaeger/intercom-go
It’s mine, unofficial, and not a drop-in replacement, but it should avoid the API-version problem described here.