How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Doximity OAuth API

OAuth 2.0 authorization and token endpoints

Doximity OAuth API is one of 2 APIs that Doximity publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Authentication. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.

This API exposes 5 operations across 5 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://auth.doximity.com.

5 operations 5 paths 2 schemas 3 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://auth.doximity.com
Authentication
OAuth 2.0, OpenID Connect, HTTP Basic, HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 4

Doximity OAuth API declares 4 security schemes for authenticating requests. It supports OAuth 2.0 (doximityOAuth) using the authorizationCode flow, exposing 21 scopes. It supports OpenID Connect (openIdConnect) discovered at https://auth.doximity.com/.well-known/openid-configuration. It accepts HTTP basic authentication (clientBasic). It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

  • clientBasic — HTTP Basic with clientid:clientsecret (clientsecretbasic)

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 3 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

OAuth 5

OAuth 2.0 authorization and token endpoints

GET
/oauth/authorize
Start the Authorization Code flow
authorize 12 params → 302
POST
/oauth/token
Exchange an authorization code or refresh token for tokens
token body → 200400401429
POST
/oauth/revoke
Revoke an access or refresh token
revoke body → 200
GET
/api/v1/rate_limit
Inspect current rate-limit status
getRateLimit → 200429
GET
/.well-known/oauth-authorization-server
OAuth 2.0 Authorization Server Metadata (RFC 8414)
oauthAuthorizationServer → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are TokenResponse (6 properties), OAuthError (2 properties). Each schema is shown below with its type and property counts.

OAuthError
object
2 properties
TokenResponse
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

doximity-oauth-api-openapi.yml Raw ↑

Other APIs Doximity publishes across the network.

Doximity OpenID Connect API
Where this information came from

This is an independent, third-party profile of Doximity OAuth API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.