Troy Medicare · OAuth Scopes

Troy Medicare OAuth Scopes

OAuth 2.0 probed

Troy Medicare 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.

Health InsuranceMedicareMedicare AdvantageHealth PlansHealthcarePharmacyCare ManagementInsuranceIdentityOpenID Connect
Scopes: 0 Flows: Method: probed

Scopes (0)

Troy Medicare 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.

📄 Provider scope reference: none

Source

OAuth Scopes

troy-medicare-scopes.yml Raw ↑ 
name: Troy Medicare OAuth Scopes
generated: '2026-08-30'
method: probed
source: https://provider.troymedicare.com/.well-known/openid-configuration (HTTP 200, fetched 2026-08-30)
description: >-
  The 35 scopes advertised by the Troy Medicare provider-portal authorization server's OpenID
  Connect discovery document. Troy Medicare publishes no scope reference page, so descriptions
  below are left empty rather than invented; only the six standard OIDC scopes and offline_access
  carry their specification-defined meaning. The remainder are resource scopes of the underlying
  health-plan administration platform and their semantics are not publicly documented.
authorization_server: https://provider.troymedicare.com
docs: none
scope_count: 35
scopes:
- name: openid
  standard: OIDC Core 1.0
  description: Request an ID token (OpenID Connect authentication).
- name: profile
  standard: OIDC Core 1.0
  description: End-user profile claims (name, family_name, given_name, picture, preferred_username, and similar).
- name: email
  standard: OIDC Core 1.0
  description: email and email_verified claims.
- name: address
  standard: OIDC Core 1.0
  description: address claim.
- name: phone
  standard: OIDC Core 1.0
  description: phone_number and phone_number_verified claims.
- name: offline_access
  standard: OIDC Core 1.0
  description: Issue a refresh token for access when the end user is not present.
- name: role
  description: ''
- name: McAppUserProfile
  description: ''
- name: BenefitAdminResource
  description: ''
- name: NhCommercial
  description: ''
- name: IdentityManager
  description: ''
- name: nh_web_resource
  description: ''
- name: nh_pcmweb_resource
  description: ''
- name: CustomerService
  description: ''
- name: BrokerPortal
  description: ''
- name: MemberPortal
  description: ''
- name: BrokerComm
  description: ''
- name: Correspondence
  description: ''
- name: EnrFileProcess
  description: ''
- name: Enrollment
  description: ''
- name: BillingAndPayments
  description: ''
- name: PriorAuth
  description: ''
- name: AdminPortal
  description: ''
- name: AdministrationService
  description: ''
- name: AuthServer
  description: ''
- name: SaasService
  description: ''
- name: NirvanaHealth
  description: ''
- name: IdentityService
  description: ''
- name: FaxQueue
  description: ''
- name: NhCore
  description: ''
- name: DMR
  description: ''
- name: M3P
  description: ''
- name: ClaimCore
  description: ''
- name: ProductService
  description: ''
- name: MedicalPayment
  description: ''
claims_supported:
- sub
- ChildBusinessWithLob
- MemberAuth
- PasswordPolicy
- birthdate
- family_name
- gender
- given_name
- locale
- middle_name
- ChildBusiness
- name
- zoneinfo
- website
- updated_at
- profile
- nickname
- picture
- preferred_username
- email
- email_verified
- address
- phone_number
- phone_number_verified
- BusinessId
- ApplicationId
- BusinessName
- validation_rule
- role
- UserId
- LOB
- CapitationAdminRights
- BusinessTrackerCode
- CommunicationPrefrence
- MemberId
- PayerId
- FaxCategories
notes:
- >-
  The FHIR authorization surface at https://fhir.troymedicare.com omits scopes_supported from its
  discovery document, so no SMART on FHIR scope vocabulary (patient/*.read and similar) could be
  observed. It is not recorded here rather than being assumed.
evidence:
- url: https://provider.troymedicare.com/.well-known/openid-configuration
  status: 200
- url: https://fhir.troymedicare.com/.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/troy-medicare-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.

GitHub Google LinkedIn

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