Announcing Developer Identity for Unlisted HubSpot Apps

[mwelch]

Trust is a core part of the HubSpot platform and identity plays a key role. Users want to verify whether they can trust each app developer with their business data.

Starting today, developers will be able to identify themselves and their apps to users by adding a verified domain. Once verified, this domain will appear to users during install.

Starting January 25, 2021 users will be notified of the status of each app during install. We will warn users installing off-marketplace apps without verified domains. We will inform users installing off-marketplace apps with verified domains that HubSpot has not reviewed them.

Note that apps listed on our marketplace don’t need to verify their domains, and will not feature the developer identity warning banner.

If you have any questions or comments, please leave a note here in the forum thread.

[gorjerpale]

You can find the ID of any list in HubSpot by navigating to the list in your portal and inspecting the URL. ... The HubSpot Companies API allows developers to integrate the Hubspot ... Python HubSpot API v3 SDK(Client) files and sample apps. ... 

I have also a hug problem in this can anyone guide me please

[Dave_]

Hi @mwelch 

We use HubSpot's CMS to host our website (and AWS for our DNS).  We use a CNAME to point to the HubSpot CMS servers.  This means we cannot add a TXT record.

Are there any alternative methods for validating our domain?  (though as it's already with HubSpot it seems a litte redundant 🙂 )

If a CNAME RR is present at a node, no other data should be
present; this ensures that the data for a canonical name and its aliases
cannot be different. This rule also insures that a cached CNAME can be
used without checking with an authoritative server for other RR types.

Dave

[mwelch]

Hi Dave,

A root domain cannot contain a CNAME record. See: https://ns1.com/resources/cname#:~:text=A%20CNAME%20cannot%20be%20placed,never%20to%20an%20IP%20addr....
You should create a new subdomain to hold the TXT record, or simply place it on the root domain.

[Mike_Eastwood]

Hi @mwelch 

We use a subdomain for all of our webhooks, OAuth, etc. 

Do you recommend registering the root domain? Or the Subdomain?

Thanks in advance

Mike

[mwelch]

Hi Mike,

We are verifying that you own the domain, which includes all subdomains, so you can setup a new subdomain to hold the TXT record, use an existing subdomain, or you can use the root domain to hold that record. Typically for this type of thing you just add the TXT record to the root domain, but it’s up to you.