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

Support for Intercom API 2.0 (2020-01-30)? #130

Open
taipeicoder opened this issue Mar 26, 2020 · 3 comments
Open

Support for Intercom API 2.0 (2020-01-30)? #130

taipeicoder opened this issue Mar 26, 2020 · 3 comments

Comments

@taipeicoder
Copy link

taipeicoder commented Mar 26, 2020

Using the endpoint users under Intercom API 2.0 (2020-01-30) gets a version invalid response. Downgrading the API version to 1.4 solves the issue.

Version info

  • intercom-go version: 2.0.0
  • Go version: 1.13.5

Expected behavior

User.FindByEmail should return an Intercom user by given email

Actual behavior

HTTP code 400 with the message: intercom_version_invalid, Requested resource is not available in current API version

Steps to reproduce

  1. Initiate a new Intercom client intercom.NewClient(token, "")
  2. Call ic.Users.FindByEmail(email)
  3. A 400 error is returned with the message intercom_version_invalid, Requested resource is not available in current API version

Logs

@lloydliyu
Copy link

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
Copy link

ruudk commented 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.v2 does 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
Copy link

pkpfr commented 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.

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

4 participants