Century Communities OAuth Scopes

OAuth 2.0 probed

Century Communities publishes 6 OAuth 2.0 scopes via the authorization_code, client_credentials, and refresh_token flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Century Communities API on a user’s behalf.

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 EstateHomebuildingConstructionContent ManagementConsumerMortgage

Scopes: 6 Flows: authorization_code, client_credentials, refresh_token Method: probed

Scopes (6)

Scope	Description	Flows
openid	Standard OpenID Connect scope requesting an ID token.
offline_access	Requests a refresh token so the client can obtain new access tokens without user interaction.
profile	Releases the end user's basic profile claims.
email	Releases the end user's email claim.
roles	Releases the end user's role claims; maps to the `role` claim advertised in claims_supported.
epi_service_api	Access to the Optimizely (Episerver) Service API — the authenticated content management surface. Vendor-defined scope, not an OpenID Connect standard scope.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-09-14'
method: probed
source: https://www.centurycommunities.com/.well-known/openid-configuration
provider: Century Communities
providerId: century-communities
description: >-
  The scopes below are the verbatim scopes_supported array from the OpenID Connect
  discovery document Century Communities' own host serves. There is no published scope
  reference page — the company has no developer portal — so the discovery document is the
  only authority, and the descriptions are the standard meanings of these identifiers in
  OpenID Connect and in Optimizely CMS, flagged as such.
docs: null
docs_note: >-
  No first-party scope/permission reference exists. Searched 2026-09-14; Century
  Communities publishes no developer documentation.
issuer: https://www.centurycommunities.com/
flows:
  - type: authorization_code
    pkce: S256
  - type: client_credentials
  - type: refresh_token
scopes:
  - name: openid
    description: Standard OpenID Connect scope requesting an ID token.
    standard: OpenID Connect Core 1.0
  - name: offline_access
    description: Requests a refresh token so the client can obtain new access tokens without user interaction.
    standard: OpenID Connect Core 1.0
  - name: profile
    description: Releases the end user's basic profile claims.
    standard: OpenID Connect Core 1.0
  - name: email
    description: Releases the end user's email claim.
    standard: OpenID Connect Core 1.0
  - name: roles
    description: Releases the end user's role claims; maps to the `role` claim advertised in claims_supported.
    standard: Optimizely CMS
  - name: epi_service_api
    description: >-
      Access to the Optimizely (Episerver) Service API — the authenticated content
      management surface. Vendor-defined scope, not an OpenID Connect standard scope.
    standard: Optimizely Service API
scope_count: 6
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com

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/century-communities-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.