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
{{ message }}
Repository navigation
Client does not support bearer token authentication #147
README example has NewClient(ApiKey, ""). Code wants NewClient(AppID, ApiKey). The former is the only think that "worked" for me. This still doesn't return anything despite "successful" calls.
As it stands, it seems I need to implement my own intercom interfaces.HTTPClient interface to refactor Get, Post, Patch, Delete functions. Or get a change into this repo or some fork to properly use Bearer authorization. This repo doesn't seem maintainer but this does seem important for basic functionality. (Removing my star :( )
Full disclosure: it’s my project, not an official Intercom SDK. It’s still pre-v1, so I’d pin v0.2.1. If you try it and run into migration problems, open an issue and I’ll help.
Activity
uffejaeger commentedon Jul 30, 2026
You’re right — this client still uses Basic auth, so it won’t work cleanly with current Intercom tokens without replacing the HTTP client.
I’ve been working on a new Go client that uses a single bearer token:
It’s here: https://github.com/uffejaeger/intercom-go
Full disclosure: it’s my project, not an official Intercom SDK. It’s still pre-v1, so I’d pin
v0.2.1. If you try it and run into migration problems, open an issue and I’ll help.