Houm · OAuth Scopes
Houm OAuth Scopes
OAuth 2.0
probed
Houm uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.
This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.
CompanyReal-EstatePropTechProperty ManagementRentalsMarketplaceLatin AmericaChileMexicoColombia
Scopes: 0
Flows:
Method: probed
Scopes (0)
Houm implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.
Read verbatim from scopes_supported in the OpenID Connect discovery document Houm's Auth0 custom domain serves at auth.houm.com. These are the standard OIDC scopes an Auth0 tenant advertises — Houm publishes no API-specific or product-specific scope reference, because it publishes no public API. No scope descriptions are provided by the issuer; the descriptions below are the OpenID Connect Core 1.0 / Auth0 standard meanings of each claim scope, not Houm's own text.
Read verbatim from scopes_supported in the OpenID Connect discovery document Houm's Auth0 custom domain serves at auth.houm.com. These are the standard OIDC scopes an Auth0 tenant advertises — Houm publishes no API-specific or product-specific scope reference, because it publishes no public API. No scope descriptions are provided by the issuer; the descriptions below are the OpenID Connect Core 1.0 / Auth0 standard meanings of each claim scope, not Houm's own text.
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.