-
Notifications
You must be signed in to change notification settings - Fork 79
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
When will support for new Personal Access Tokens instead of API Keys begin? #61
Comments
Hi @briemarie - this should work right now by passing the PAT where you would normally pass the appID, and send an empty string where the API key would normally be. |
The API documentation for Personal Access Tokens is explicit about using the @josler I can't find any documentation for the overloading. Is that a stable API feature I can depend on? |
Hey @timhudson |
Just to note that we did update the README here to clarify how to use access tokens to authorize access |
This also needs to be updated in the GoDoc (https://godoc.org/gopkg.in/intercom/intercom-go.v2#NewClient). It just misled me and resulted in a fair bit of time debugging. |
According to the Intercom docs, API Keys are deprecated and will be fully replaced with a Personal Access Token in January 2017. I was expecting NewClient to support this change already ie.
ic := intercom.NewClient("appID", "apiKey") would be ic := intercom.NewClient("pat")
When can we expect the package to update to support this change?
The text was updated successfully, but these errors were encountered: