Hub ID discarded in auth token response?

[gregblass]

Here's the response I'm getting using this gem:

(byebug) tokens #<Hubspot::OAuth::TokenResponseIF:0x000000016d78f028 @access_token="[FILTERED]", @refresh_token="[FILTERED]", @token_type="bearer", @expires_in=1800>

No hub id is being returned.

I didn't say it 😂 Was this just never implemented, or am I missing something here? I do see two mentions of it in the following code?

[gregblass]

Just in case anyone else comes here and has the same issue, I got around this by making a separate API call to the access token info endpoint - like this:

def get_hub_id(access_token)
  options = {
    method: "GET",
    path: "/oauth/v1/access-tokens/#{access_token}"
  }
  token_info = api_client.api_request(options)
  parsed_info = JSON.parse(token_info.body)
  parsed_info["hub_id"]
end

... where api_client is defined as Hubspot::Client.new(api_key: ...)

[rikkiprince]

What did you call on the client to get the auth token response?

I got as far as client.oauth.access_tokens_api.get acceds_token, but I just get an error.

[gregblass]

I couldn't get it to work like that (I have no idea if that endpoint is actually implemented...er, generated) - and this gem is kind of a nightmare to try to figure it out (no documentation)...hence why I went with my own 'direct' call to the endpoint string like I've shown above. ChatGPT told me about that as an option - and honestly I'll probably use that style of doing things moving forward rather then guessing at the generated endpoint wrappers and what the hubspot team decided implement or not. That way you can just look at the hubspot documentation and hit whatever API url you want - and not worry about finding that particular file in this codebase and deciphering how to call it - or whether or not this gem will actually return an object containing the entire response from the API.

Its worth pointing out (if I wasn't clear) that the solution I posted is a different API call from what I originally posted about... which was getting the hub ID from the response to the API call where you exchange the authorization code for an access token. The hub ID is returned from hubspot, but this gem takes the response from the API and returns a subset of information that does not include the hub id.

The solution I posted hits the endpoint (in a subsequent API call) to get info about the token (including the hub id) once you already have the token (after the exchange). I just used the path string directly instead of using the wrappers generated by whatever bootleg ruby API creator thing they used to avoid putting development resources into writing a proper gem.

It does add another unnecessary API call to the process, but I only need this done once per tenant in my application (and then save the hub ID to the database) - so it wasn't a big deal.

[Samsinite]

I couldn't get it to work like that (I have no idea if that endpoint is actually implemented...er, generated) - and this gem is kind of a nightmare to try to figure it out (no documentation)...hence why I went with my own 'direct' call to the endpoint string like I've shown above. ChatGPT told me about that as an option - and honestly I'll probably use that style of doing things moving forward rather then guessing at the generated endpoint wrappers and what the hubspot team decided implement or not. That way you can just look at the hubspot documentation and hit whatever API url you want - and not worry about finding that particular file in this codebase and deciphering how to call it - or whether or not this gem will actually return an object containing the entire response from the API.

Its worth pointing out (if I wasn't clear) that the solution I posted is a different API call from what I originally posted about... which was getting the hub ID from the response to the API call where you exchange the authorization code for an access token. The hub ID is returned from hubspot, but this gem takes the response from the API and returns a subset of information that does not include the hub id.

The solution I posted hits the endpoint (in a subsequent API call) to get info about the token (including the hub id) once you already have the token (after the exchange). I just used the path string directly instead of using the wrappers generated by whatever bootleg ruby API creator thing they used to avoid putting development resources into writing a proper gem.

It does add another unnecessary API call to the process, but I only need this done once per tenant in my application (and then save the hub ID to the database) - so it wasn't a big deal.

From what I can tell in the hubspot API docs, it does not return the hub id in the token response, I believe ChatGPT is wrong, see (https://developers.hubspot.com/docs/reference/api/app-management/oauth#initiate-an-integration-with-oauth-2.0). But you are correct that it can be fetched by looking up the token metadata (https://developers.hubspot.com/docs/reference/api/app-management/oauth#get-metadata-for-oauth-2.0-access-token).

I agree that this gem is a mess, I've debugged it too many times to count. If I hadn't inherited code using this gem I would have just wrote a wrapper from scratch, I don't use that many endpoints, and at some point it is what I'll probably decide to do in order to ditch this gem.

Anyways, when you call client.oauth.access_tokens_api.get, it looks up the get method from https://github.com/HubSpot/hubspot-api-ruby/blob/master/lib/hubspot/codegen/oauth/api/access_tokens_api.rb by looking under /codgen/ for the first path/method (oauth in this call), then tries to find the second name/path inside of the api folder, (which in this case it looks for access_tokens_api.rb) which it dynamically requres and loads. Finally in your example it calls get which takes a token param, so it expects you to call it like this:

client.oauth.access_tokens_api.get({ token: insert_your_access_token_here })

Hope that helps you learn how to navigate this dreadful gem.