topic Re: Error scim private app in APIs & Integrations

Error scim private app

RayanDigi — Thu, 04 Dec 2025 15:10:29 GMT

Hi HubSpot Community,

I’ve created a SCIM app on both my HubSpot account and sandbox, but I keep encountering the same issue when accessing the SCIM interface. The error message is:

"Something went wrong fetching your SCIM domains. Please try again or contact support."

I’m not sure what’s causing this error, as I’ve double-checked my setup and can’t find any misconfiguration. Has anyone experienced this before or could provide guidance on what might be causing it?

Thanks in advance for your help!

Re: Error scim private app

SealaB — Thu, 04 Dec 2025 23:27:52 GMT

Hi there, @RayanDigi - and a warm welcome to the HubSpot Community!

Since this involves custom app configuration and potential API/permissions hurdles, I'm going to tag in a few of our top developer experts who often work with custom integrations: @Teun-SB, @mangelet , and @ChrisoKlepke - have any of you seen this specific "fetching domains" error when initializing a SCIM app?

Ensure the domain you intend to use for user provisioning (e.g., company.com) is connected and fully verified via DNS.

You should also confirm that the user account you are using to access the SCIM interface is a Super Admin.

If the domain is definitely verified and you are a Super Admin, this might be a temporary service glitch or a bug - thus filing a Support Ticket so our engineering team can look at the backend logs would be ideal.

I'll keep an eye on this thread to see if our champions have a specific workaround!

Re: Error scim private app

TG6 — Fri, 05 Dec 2025 13:19:44 GMT

@RayanDigi wrote:
Hi HubSpot Community,

I’ve created a SCIM app on both my HubSpot account and sandbox, but I keep encountering the same issue when accessing the SCIM interface. The error message is:

"Something went wrong fetching your SCIM domains. Please try again or contact support."

I’m not sure what’s causing this error, as I’ve double-checked my setup and can’t find any misconfiguration. Has anyone experienced this before or could provide guidance on what might be causing it?

Thanks in advance for your help!

Hey SCIM only works on Professional or Enterprise plans, so if the account or sandbox is on a lower plan, the SCIM interface will always fail. Next, make sure the TXT DNS record HubSpot gave you is added exactly as-is in your domain host and that DNS has fully propagated if the domain isn’t verified, HubSpot cannot fetch any SCIM domains, causing this exact error. Also confirm that SSO is enabled and correctly configured, because SCIM depends on SSO being active. Finally, remember that HubSpot only allows one SCIM app per account, so if another SCIM app already exists (even a leftover one), it can block the new one from loading domains.

Re: Error scim private app

RayanDigi — Wed, 10 Dec 2025 09:12:54 GMT

Hello @SealaB,

Thank you for your response. The problem was that I was not a super admin, so the interface was showing me an error.

Re: Error scim private app

SealaB — Wed, 10 Dec 2025 21:38:02 GMT

@RayanDigi - thanks for reporting back - glad we were able to get to the bottom of it!
Have a wonderful rest of your week.

Re: Error scim private app

RubenBurdin — Mon, 15 Dec 2025 19:45:11 GMT

Hey @RayanDigi , this behavior is actually pretty typical for SCIM in HubSpot, and the error message is unfortunately much less explicit than it should be.

For anyone else running into this, the SCIM UI depends on permissions that are only available to Super Admins. If you’re not a Super Admin, HubSpot doesn’t gracefully block access. Instead, it fails when trying to fetch verified domains and throws the generic “Something went wrong fetching your SCIM domains” error.

There’s no indication in the UI that this is a permissions issue, which makes it feel like a config or API bug.

With how HubSpot works now in 2025, there are a few hard requirements that all have to be true at the same time for the SCIM screen to load correctly.

The user accessing the SCIM app must be a Super Admin. The account or sandbox must be on Professional or Enterprise. The domain used for provisioning must be fully verified via DNS. SSO must be enabled, since SCIM is tied to SSO enforcement. And only one SCIM app can exist per account, even a leftover one can cause conflicts.

If any one of those is missing, the UI tends to fail silently like this. So your finding about Super Admin access is spot on, and it explains why everything looked correct but still broke.

Appreciate you closing the loop here. This will definitely save someone else a support ticket.