Sydney Airport · OAuth Scopes

Sydney Airport OAuth Scopes

OAuth 2.0 derived

Sydney Airport publishes 8 OAuth 2.0 scopes via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Sydney Airport API on a user’s behalf.

Tokens are issued from https://id.syd.com.au:443/am/oauth2/access_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.

TravelAustraliaAirportsAviationAirport InfrastructureTransportationFlight InformationPassenger Experience

Scopes: 8 Flows: authorizationCode Method: derived

OAuth endpoints

Authorization URL
https://id.syd.com.au:443/am/oauth2/authorize

Token URL
https://id.syd.com.au:443/am/oauth2/access_token

Flows
authorizationCode

Scopes (8)

Scope	Description	Flows
openid	OpenID Connect authentication; requests an ID token.	authorizationCode
profile	Standard OpenID Connect profile claims for the authenticated partner user.	authorizationCode
email	Standard OpenID Connect email claims.	authorizationCode
address	Standard OpenID Connect address claim.	authorizationCode
phone	Standard OpenID Connect phone_number claims.	authorizationCode
fr:idm:*	ForgeRock Identity Management platform scope advertised by the realm. Vendor-default, not a Sydney Airport product scope.	authorizationCode, clientCredentials
am-introspect-all-tokens	ForgeRock Access Management scope permitting introspection of all tokens. Vendor-default administrative scope.	clientCredentials
infosyd	Application scope for the InfoSYD airline / ground-handler / on-airport-tenant portal. Not present in scopes_supported; observed on the live authorize request issued by client_id INFOSYD_APP_Client.	authorizationCode

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-07-28'
method: derived
source: authentication/sydney-airport-openid-configuration.json
docs: null
note: >-
  Derived from the scopes_supported array of the ForgeRock Access Management
  OpenID Connect Discovery document at https://id.syd.com.au/am/oauth2/.well-known/openid-configuration
  (HTTP 200, harvested 2026-07-28), plus the scope string observed on the live
  InfoSYD authorize redirect. Sydney Airport publishes no scope or permission
  reference page - these are the values the identity provider itself advertises,
  not documented product scopes.
schemes:
- name: SYDOAuth2
  source: authentication/sydney-airport-openid-configuration.json
  issuer: https://id.syd.com.au:443/am/oauth2
  flows:
  - flow: authorizationCode
    authorizationUrl: https://id.syd.com.au:443/am/oauth2/authorize
    tokenUrl: https://id.syd.com.au:443/am/oauth2/access_token
scopes:
- scope: openid
  description: OpenID Connect authentication; requests an ID token.
  standard: OpenID Connect Core 1.0
  flows: [authorizationCode]
  sources: [authentication/sydney-airport-openid-configuration.json]
  observed_in_infosyd_request: true
- scope: profile
  description: Standard OpenID Connect profile claims for the authenticated partner
    user.
  standard: OpenID Connect Core 1.0
  flows: [authorizationCode]
  sources: [authentication/sydney-airport-openid-configuration.json]
  observed_in_infosyd_request: true
- scope: email
  description: Standard OpenID Connect email claims.
  standard: OpenID Connect Core 1.0
  flows: [authorizationCode]
  sources: [authentication/sydney-airport-openid-configuration.json]
  observed_in_infosyd_request: true
- scope: address
  description: Standard OpenID Connect address claim.
  standard: OpenID Connect Core 1.0
  flows: [authorizationCode]
  sources: [authentication/sydney-airport-openid-configuration.json]
  observed_in_infosyd_request: false
- scope: phone
  description: Standard OpenID Connect phone_number claims.
  standard: OpenID Connect Core 1.0
  flows: [authorizationCode]
  sources: [authentication/sydney-airport-openid-configuration.json]
  observed_in_infosyd_request: false
- scope: fr:idm:*
  description: ForgeRock Identity Management platform scope advertised by the realm.
    Vendor-default, not a Sydney Airport product scope.
  standard: ForgeRock platform
  flows: [authorizationCode, clientCredentials]
  sources: [authentication/sydney-airport-openid-configuration.json]
  observed_in_infosyd_request: false
- scope: am-introspect-all-tokens
  description: ForgeRock Access Management scope permitting introspection of all tokens.
    Vendor-default administrative scope.
  standard: ForgeRock platform
  flows: [clientCredentials]
  sources: [authentication/sydney-airport-openid-configuration.json]
  observed_in_infosyd_request: false
- scope: infosyd
  description: Application scope for the InfoSYD airline / ground-handler / on-airport-tenant
    portal. Not present in scopes_supported; observed on the live authorize request
    issued by client_id INFOSYD_APP_Client.
  standard: null
  flows: [authorizationCode]
  sources: ['observed: https://www.sydneyairport.com.au/infosyd authorize redirect,
      2026-07-28']
  observed_in_infosyd_request: true

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/sydney-airport-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.

GitHub Google LinkedIn

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