Diligent Pharma · OAuth Scopes

Diligent Pharma OAuth Scopes

OAuth 2.0 probed

Diligent Pharma 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.

CompanyClinical TrialsLife SciencesPharmaceuticalsBiotechnologyVendor ManagementRisk ManagementQuality ManagementComplianceGxPAuditingSoftware-as-a-Service
Scopes: 0 Flows: Method: probed

Scopes (0)

Diligent Pharma 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.

Source

OAuth Scopes

diligent-pharma-scopes.yml Raw ↑
generated: '2026-08-12'
method: probed
source: https://clerk.diligentpharma.com/.well-known/oauth-authorization-server
description: >-
  OAuth 2.0 scopes advertised by the Diligent Pharma authorization server
  (clerk.diligentpharma.com), the Clerk-hosted identity provider behind the
  Diligent360 application. These are identity/profile scopes for application sign-in,
  not resource scopes over a published Diligent Pharma API — Diligent Pharma publishes
  no developer API and no scopes reference page. Recorded verbatim from the discovery
  document; nothing here is inferred.
authorization_server: https://clerk.diligentpharma.com
docs: https://clerk.com/docs/oauth/scoped-access
docs_note: >-
  service_documentation in the discovery document points at Clerk's own generic
  documentation, not at a Diligent Pharma scopes reference. No provider-authored
  scope documentation exists.
scope_type: identity
resource_scopes_published: false
scope_count: 6
scopes:
  - name: openid
    description: OpenID Connect sign-in; requests an ID token for the authenticated user.
    standard: true
  - name: profile
    description: >-
      Basic profile claims — name, given_name, family_name, preferred_username, picture.
    standard: true
  - name: email
    description: Email address and its verification state (email, email_verified claims).
    standard: true
  - name: offline_access
    description: Issues a refresh token so the client can renew access without re-prompting.
    standard: true
  - name: public_metadata
    description: >-
      Clerk public metadata attached to the user record — application-defined,
      readable by the client and the frontend.
    standard: false
  - name: private_metadata
    description: >-
      Clerk private metadata attached to the user record — application-defined,
      backend-only data.
    standard: false
claims_supported:
  - sub
  - iss
  - aud
  - exp
  - iat
  - email
  - email_verified
  - preferred_username
  - given_name
  - family_name
  - name
  - picture

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/diligent-pharma-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.