Cleveland-Cliffs · OAuth Scopes

Cleveland-Cliffs OAuth Scopes

OAuth 2.0 probed

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

Tokens are issued from https://login.clevelandcliffs.com/oauth2/v1/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.

AutomotiveIron OreManufacturingMiningSteelSteelmakingSupply Chain

Scopes: 7 Flows: authorizationCode Method: probed

OAuth endpoints

Authorization URL
https://login.clevelandcliffs.com/oauth2/v1/authorize

Token URL
https://login.clevelandcliffs.com/oauth2/v1/token

Flows
authorizationCode

Scopes (7)

Scope	Description	Flows
openid	OIDC authentication; issue an ID token for the authenticated subject.	authorizationCode, implicit
profile	Standard OIDC profile claims (name, preferred_username, locale, updated_at).	authorizationCode, implicit
email	Email address and email_verified claim.	authorizationCode, implicit
address	Postal address claim.	authorizationCode, implicit
phone	Phone number and phone_number_verified claims.	authorizationCode, implicit
offline_access	Issue a refresh token so the client can renew access without user presence.	authorizationCode
groups	Group membership claim for the authenticated subject.	authorizationCode, implicit

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-09-05'
method: probed
source: https://login.clevelandcliffs.com/.well-known/openid-configuration
note: >-
  Read from the anonymous discovery documents on Cleveland-Cliffs' own Okta tenant. The seven
  scopes below are the standard OIDC/OAuth 2.0 set the org authorization server advertises.
  The RFC 8414 document additionally advertises the full Okta org-management scope family
  (okta.users.*, okta.groups.*, okta.apps.* and ~40 more); those are the Okta product's own
  administrative scopes, not scopes Cleveland-Cliffs defined for a business API, so they are
  recorded as vendor_platform_scopes rather than as the company's scope surface. Cleveland-Cliffs
  publishes no public API and therefore no business-domain scope reference page.
docs: null
schemes:
  - name: cleveland-cliffs-okta-oidc
    source: well-known/cleveland-cliffs-openid-configuration.json
    issuer: https://login.clevelandcliffs.com
    flows:
      - flow: authorizationCode
        authorizationUrl: https://login.clevelandcliffs.com/oauth2/v1/authorize
        tokenUrl: https://login.clevelandcliffs.com/oauth2/v1/token
scopes:
  - scope: openid
    description: OIDC authentication; issue an ID token for the authenticated subject.
    flows: [authorizationCode, implicit]
    sources: [well-known/cleveland-cliffs-openid-configuration.json]
  - scope: profile
    description: Standard OIDC profile claims (name, preferred_username, locale, updated_at).
    flows: [authorizationCode, implicit]
    sources: [well-known/cleveland-cliffs-openid-configuration.json]
  - scope: email
    description: Email address and email_verified claim.
    flows: [authorizationCode, implicit]
    sources: [well-known/cleveland-cliffs-openid-configuration.json]
  - scope: address
    description: Postal address claim.
    flows: [authorizationCode, implicit]
    sources: [well-known/cleveland-cliffs-openid-configuration.json]
  - scope: phone
    description: Phone number and phone_number_verified claims.
    flows: [authorizationCode, implicit]
    sources: [well-known/cleveland-cliffs-openid-configuration.json]
  - scope: offline_access
    description: Issue a refresh token so the client can renew access without user presence.
    flows: [authorizationCode]
    sources: [well-known/cleveland-cliffs-openid-configuration.json]
  - scope: groups
    description: Group membership claim for the authenticated subject.
    flows: [authorizationCode, implicit]
    sources: [well-known/cleveland-cliffs-openid-configuration.json]
vendor_platform_scopes:
  count: 76
  source: well-known/cleveland-cliffs-oauth-authorization-server.json
  note: >-
    Okta org-management scopes (okta.*) advertised by the tenant's RFC 8414 metadata. These
    belong to the Okta platform, not to a Cleveland-Cliffs business API, and are listed here
    only so the discovery document is faithfully represented.

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/cleveland-cliffs-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.