Doximity · Authentication Profile

Doximity Authentication

Authentication

Doximity secures its APIs with oauth2 and openIdConnect across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode, refreshToken, and deviceCode flow(s).

CompanyHealthtechIdentityAuthenticationOpenID ConnectPhysician NetworkHealthcareSSOVerification
Methods: oauth2, openIdConnect Schemes: 2 OAuth flows: authorizationCode, refreshToken, deviceCode API key in:

Security Schemes

doximityOAuth oauth2
· flows: authorizationCode
openIdConnect openIdConnect

Source

Authentication Profile

Raw ↑
generated: '2026-07-18'
method: searched
source: https://www.doximity.com/developers/documentation
docs: https://www.doximity.com/developers/documentation
discovery: https://auth.doximity.com/.well-known/openid-configuration
summary:
  types: [oauth2, openIdConnect]
  oauth2_flows: [authorizationCode, refreshToken, deviceCode]
  pkce: required
  pkce_methods: [S256]
  token_endpoint_auth_methods: [client_secret_basic]
  id_token_signing_alg: [RS256]
  response_types: ["code", "code id_token", "id_token"]
schemes:
- name: doximityOAuth
  type: oauth2
  sources: [openapi/doximity-oauth-openapi.yml]
  flows:
  - flow: authorizationCode
    authorizationUrl: https://auth.doximity.com/oauth/authorize
    tokenUrl: https://auth.doximity.com/oauth/token
    refreshUrl: https://auth.doximity.com/oauth/token
    scope_count: 21
  grant_types:
  - authorization_code
  - refresh_token
  - urn:ietf:params:oauth:grant-type:device_code
  notes: >-
    Authorization Code grant with mandatory PKCE (S256). Client authentication at the token
    endpoint uses HTTP Basic (client_secret_basic). Access tokens are bearer tokens with a
    typical 1800s lifetime; refresh tokens rotate access. The device_code grant supports
    input-constrained clients.
- name: openIdConnect
  type: openIdConnect
  openIdConnectUrl: https://auth.doximity.com/.well-known/openid-configuration
  sources: [openapi/doximity-oauth-openapi.yml]
  id_token_signing_alg: RS256
  jwks_uri: https://auth.doximity.com/.well-known/jwks.json
  userinfo_endpoint: https://auth.doximity.com/oauth/userinfo

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact 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 security artifact
curl "https://apis.io/api/v1/security/doximity-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

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