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

DoseSpot Prescribers API

Clinician (prescriber) and clinic staff management.

DoseSpot Prescribers API is one of 27 APIs that DoseSpot publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Prescribers. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

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

Requests are made against 2 base URLs: https://my.dosespot.com/webapi/v2, https://my.staging.dosespot.com/webapi/v2.

3 operations 2 paths 6 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://my.dosespot.com/webapi/v2
Authentication
HTTP Bearer, API Key
Terms of Service
Resource Areas
1

Authentication & Security 2

DoseSpot Prescribers API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). An API key is passed in the header as Subscription-Key (subscriptionKey). By default, every request must be authenticated.

  • bearerAuth — OAuth2 access token obtained from the DoseSpot token endpoint (POST /webapi/v2/connect/token) using your clinic and clinician credentials, sent as an Authoriza…
  • subscriptionKey — Per-application subscription key issued by DoseSpot.

Paths & Operations 3

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

Prescribers 3

Clinician (prescriber) and clinic staff management.

GET
/clinicians
Search clinicians
searchClinicians 1 param → 200
POST
/clinicians
Create a clinician
createClinician body → 200
GET
/clinicians/{clinicianId}
Get a clinician
getClinician 1 param → 200

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are Clinician (17 properties), PageResult (5 properties), ResultStatus (2 properties), ApiResult (1 property). Each schema is shown below with its type and property counts.

ResultStatus
object
2 properties
ClinicianResult
Clinician
object
17 properties
ClinicianListResult
ApiResult
object
1 property
PageResult
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

dosespot-prescribers-api-openapi.yml Raw ↑

Other APIs DoseSpot publishes across the network.

DoseSpot Medications API
DoseSpot Notifications API
DoseSpot Patients API
DoseSpot Pharmacies API
DoseSpot Prescriptions API
DoseSpot Allergens API
DoseSpot Allergies API
DoseSpot Clinic Favorites API
DoseSpot Clinic Groups API
DoseSpot Clinician Favorites API
DoseSpot Clinician Order Sets API
DoseSpot Clinicians API
Where this information came from

This is an independent, third-party profile of DoseSpot Prescribers 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.