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 Pharmacies API

Surescripts pharmacy search and patient pharmacy management.

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

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

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

Requests are made against 4 base URLs: https://my.dosespot.com/webapi/v2, https://my.staging.dosespot.com/webapi/v2, https://virtserver.swaggerhub.com/DoseSpot/dosespot-staging-rest-api-v2/Full_EPCSV2, https://virtserver.swaggerhub.com/DoseSpot/dosespot-staging-rest-api-v2/JumpStart_EPCSV2.

9 operations 7 paths 19 schemas 1 DELETE6 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://my.dosespot.com/webapi/v2
Authentication
HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 2

DoseSpot Pharmacies 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).

  • 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 9

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

Pharmacies 9

Surescripts pharmacy search and patient pharmacy management.

GET
/pharmacies/search
Search pharmacies
searchPharmacies 5 params → 200
GET
/patients/{patientId}/pharmacies
List a patient's pharmacies
getPatientPharmacies 1 param → 200
POST
/patients/{patientId}/pharmacies
Add a pharmacy to a patient
addPatientPharmacy 1 param body → 200
GET
/api/pharmacies/search
Search pharmacies
Pharmacies_PharmacySearchV2 9 params → 200
GET
/api/pharmacies/{pharmacyId}
Get pharmacy details
Pharmacies_GetPharmacyV2 1 param → 200
GET
/api/patients/{patientId}/pharmacies
Get patient's pharmacies
Pharmacies_GetPatientPharmaciesV2 1 param → 200
POST
/api/patients/{patientId}/pharmacies
Add Pharmacy to Patient
Pharmacies_AddPatientPharmacyV2 1 param body → 200
GET
/api/pharmacies/restrictions
Get Pharmacy Restrictions
Pharmacies_GetPharmacyRestrictionsV2 2 params → 200
DELETE
/api/patients/{patientId}/pharmacies/{pharmacyId}
Delete Pharmacy from Patient
Pharmacies_RemovePatientPharmacyV2 2 params → 200

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are PatientPharmacy (22 properties), Pharmacy_3 (21 properties), Pharmacy_2 (21 properties), Pharmacy (10 properties). Each schema is shown below with its type and property counts.

ResultStatus
object
2 properties
AddPharmacyRequest
object
2 properties
Pharmacy
object
10 properties
ApiResult
object
1 property
PharmacySearchResult
PageResult
object
5 properties
Result
object
Represents the result of a service operation.
2 properties 1 required
ListResponse_PatientPharmacy
object
Represents a generic response containing a list of objects.
2 properties
Response
object
The result of the operation.
1 property
Pharmacy_2
object
Represents a pharmacy entity.
21 properties
PatientPharmacy
object
Represents a pharmacy entity in relation to a patient.
22 properties
AddEditPatientPharmacyRequest
object
2 properties
ItemResponse_Pharmacy
object
Represents a generic response containing a single object.
2 properties
PageResult_2
object
6 properties
PagedListResponse_Pharmacy
object
3 properties
Pharmacy_3
object
Represents a pharmacy entity.
21 properties
ItemResponse_Pharmacy_2
object
Represents a generic response containing a single object.
2 properties
PageResult_3
object
6 properties
PagedListResponse_Pharmacy_2
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

dosespot-pharmacies-api-openapi.yml Raw ↑

Other APIs DoseSpot publishes across the network.

DoseSpot Medications API
DoseSpot Notifications API
DoseSpot Patients API
DoseSpot Prescribers 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 Pharmacies 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.