PSC Insurance · OAuth Scopes

PSC Insurance OAuth Scopes

OAuth 2.0 searched

PSC Insurance publishes 14 OAuth 2.0 scopes via the authorizationCode, clientCredentials, and deviceCode flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the PSC Insurance API on a user’s behalf.

Tokens are issued from https://login.pscinsurance.com.au/oauth/token.

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.

InsuranceAustraliaBrokersInsurance BrokerageProperty and CasualtyCommercial InsuranceCyber InsuranceIntermediaryPartner GatedNo Public API
Scopes: 14 Flows: authorizationCode, clientCredentials, deviceCode Method: searched

OAuth endpoints

Authorization URL
https://login.pscinsurance.com.au/authorize
Token URL
https://login.pscinsurance.com.au/oauth/token
Flows
authorizationCodeclientCredentialsdeviceCode

Scopes (14)

ScopeDescriptionFlows
openid Request an ID token — the base OpenID Connect scope. authorizationCode, deviceCode
profile Basic profile claims (name, given_name, family_name, nickname, picture). authorizationCode, deviceCode
email Email address claim. authorizationCode, deviceCode
phone Phone number claim. authorizationCode, deviceCode
address Address claim. authorizationCode, deviceCode
offline_access Issue a refresh token so the session can be renewed without re-auth. authorizationCode, deviceCode
name Auth0 granular profile claim — full name.
given_name Auth0 granular profile claim — given name.
family_name Auth0 granular profile claim — family name.
nickname Auth0 granular profile claim — nickname.
email_verified Auth0 granular profile claim — whether the email address is verified.
picture Auth0 granular profile claim — profile picture URL.
created_at Auth0 granular profile claim — account creation timestamp.
identities Auth0 granular profile claim — linked identity providers.

Source

OAuth Scopes

psc-insurance-scopes.yml Raw ↑
generated: '2026-07-25'
method: searched
source: https://login.pscinsurance.com.au/.well-known/openid-configuration
docs: null
issuer: https://login.pscinsurance.com.au/
caveat: |
  IMPORTANT — these are NOT documented PSC Insurance API scopes. They are the
  standard OpenID Connect scopes and Auth0 profile-claim scopes advertised by the
  tenant discovery document at login.pscinsurance.com.au. PSC publishes no API, no
  resource server, no audience and no product permission model. This file records
  the scope surface that is machine-readable and anonymously fetchable, and nothing
  more. Treat every entry as identity-only.
schemes:
- name: PSCIdentity
  source: well-known/psc-insurance-openid-configuration.json
  flows:
  - flow: authorizationCode
    authorizationUrl: https://login.pscinsurance.com.au/authorize
    tokenUrl: https://login.pscinsurance.com.au/oauth/token
  - flow: clientCredentials
    tokenUrl: https://login.pscinsurance.com.au/oauth/token
  - flow: deviceCode
    deviceAuthorizationUrl: https://login.pscinsurance.com.au/oauth/device/code
    tokenUrl: https://login.pscinsurance.com.au/oauth/token
scopes:
- scope: openid
  description: Request an ID token — the base OpenID Connect scope.
  kind: oidc-standard
  flows: [authorizationCode, deviceCode]
- scope: profile
  description: Basic profile claims (name, given_name, family_name, nickname, picture).
  kind: oidc-standard
  flows: [authorizationCode, deviceCode]
- scope: email
  description: Email address claim.
  kind: oidc-standard
  flows: [authorizationCode, deviceCode]
- scope: phone
  description: Phone number claim.
  kind: oidc-standard
  flows: [authorizationCode, deviceCode]
- scope: address
  description: Address claim.
  kind: oidc-standard
  flows: [authorizationCode, deviceCode]
- scope: offline_access
  description: Issue a refresh token so the session can be renewed without re-auth.
  kind: oidc-standard
  flows: [authorizationCode, deviceCode]
- scope: name
  description: Auth0 granular profile claim — full name.
  kind: auth0-profile-claim
- scope: given_name
  description: Auth0 granular profile claim — given name.
  kind: auth0-profile-claim
- scope: family_name
  description: Auth0 granular profile claim — family name.
  kind: auth0-profile-claim
- scope: nickname
  description: Auth0 granular profile claim — nickname.
  kind: auth0-profile-claim
- scope: email_verified
  description: Auth0 granular profile claim — whether the email address is verified.
  kind: auth0-profile-claim
- scope: picture
  description: Auth0 granular profile claim — profile picture URL.
  kind: auth0-profile-claim
- scope: created_at
  description: Auth0 granular profile claim — account creation timestamp.
  kind: auth0-profile-claim
- scope: identities
  description: Auth0 granular profile claim — linked identity providers.
  kind: auth0-profile-claim
product_scopes:
  documented: false
  note: |
    No PSC-specific scope (policy:read, claim:write, quote:create or anything of that
    shape) is documented or advertised. If broker/client portal APIs exist behind this
    tenant they are private and their audiences are not published.

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/psc-insurance-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

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