Venn · OAuth Scopes

Venn OAuth Scopes

OAuth 2.0 probed

Venn 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.

Real EstateProperty ManagementMultifamilyResident ExperienceProptechLeasingCommunityPaymentsGraphQLMobile Apps
Scopes: 0 Flows: Method: probed

Scopes (0)

Venn 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.

Venn publishes no scopes or permissions reference. The scopes below are the standard OpenID Connect scopes advertised by the AWS Cognito user pool that Venn's own operator dashboard names as its identity provider — they are identity scopes, not API authorization scopes. Venn's tenant GraphQL API does not use OAuth scopes to authorize data access; the schema models authorization as role rows (`Role`) scoped to a community (`hood`), so there is nothing scope-like in the contract to enumerate. Nothing here is invented: no custom resource server scopes were advertised, and none are asserted.

Source

OAuth Scopes

venn-scopes.yml Raw ↑
generated: '2026-09-02'
method: probed
source: https://cognito-idp.eu-central-1.amazonaws.com/eu-central-1_cH7XNjcIx/.well-known/openid-configuration
note: >-
  Venn publishes no scopes or permissions reference. The scopes below are the
  standard OpenID Connect scopes advertised by the AWS Cognito user pool that
  Venn's own operator dashboard names as its identity provider — they are identity
  scopes, not API authorization scopes. Venn's tenant GraphQL API does not use
  OAuth scopes to authorize data access; the schema models authorization as
  role rows (`Role`) scoped to a community (`hood`), so there is nothing scope-like
  in the contract to enumerate. Nothing here is invented: no custom resource
  server scopes were advertised, and none are asserted.
authorization_model: role-based (Role rows scoped to hood/community), not scope-based
oauth:
  issuer: https://cognito-idp.eu-central-1.amazonaws.com/eu-central-1_cH7XNjcIx
  authorization_endpoint: https://admin-tool.auth.eu-central-1.amazoncognito.com/oauth2/authorize
  token_endpoint: https://admin-tool.auth.eu-central-1.amazoncognito.com/oauth2/token
  userinfo_endpoint: https://admin-tool.auth.eu-central-1.amazoncognito.com/oauth2/userInfo
  revocation_endpoint: https://admin-tool.auth.eu-central-1.amazoncognito.com/oauth2/revoke
scopes:
  - name: openid
    description: Standard OIDC scope. Requests an ID token identifying the end user.
    source: cognito-openid-configuration
  - name: email
    description: Standard OIDC scope. Releases the email and email_verified claims.
    source: cognito-openid-configuration
  - name: phone
    description: Standard OIDC scope. Releases the phone_number and phone_number_verified claims.
    source: cognito-openid-configuration
  - name: profile
    description: Standard OIDC scope. Releases the basic profile claims.
    source: cognito-openid-configuration
custom_scopes: []
custom_scopes_note: >-
  No custom (resource-server) scopes are advertised by the pool's discovery
  document. If Venn defines any, they are not publicly discoverable.
scope_count: 4
docs: null
docs_note: No public scopes/permissions reference page exists on any Venn host.
x-evidence:
  checked: '2026-09-02'
  evidence:
    - url: https://cognito-idp.eu-central-1.amazonaws.com/eu-central-1_cH7XNjcIx/.well-known/openid-configuration
      status: 200

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this
  • find_scopesBrowse and filter every scope set in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This scope set
curl "https://apis.io/api/v1/scopes/venn-scopes"
All oauth scopes
curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.