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

Prescription creation, transmission, status, and medication history.

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

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

This API exposes 28 operations across 26 paths, and defines 55 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.

28 operations 26 paths 55 schemas 1 DELETE8 GET1 PATCH14 POST4 PUT

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 Prescriptions 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 28

Across 26 paths, the API surfaces 28 operations — 1 DELETE, 8 GET, 1 PATCH, 14 POST, 4 PUT. Each is listed below with its method, path, parameters, and response codes.

Prescriptions 28

Prescription creation, transmission, status, and medication history.

GET
/patients/{patientId}/prescriptions
List a patient's prescriptions
getPatientPrescriptions 1 param → 200
POST
/patients/{patientId}/prescriptions
Create a prescription
createPatientPrescription 1 param body → 200
GET
/patients/{patientId}/prescriptions/{prescriptionId}
Get a prescription
getPatientPrescription 2 params → 200
GET
/patients/{patientId}/medicationHistory
Get aggregated medication history
getMedicationHistory 1 param → 200
GET
/api/patients/{patientId}/prescriptions/{prescriptionId}
Get Prescriptions
Prescriptions_GetPatientPrescriptionV2 2 params → 200
GET
/api/patients/{patientId}/prescriptions/{prescriptionId}/log
Get Prescription Logs
Prescriptions_GetPrescriptionLogDetailsV2 2 params → 200
GET
/api/patients/{patientId}/prescriptions/{prescriptionId}/snapshot
Get Precription snapshot
Prescriptions_GetPrescriptionSnapshotV2 2 params → 200
GET
/api/patients/{patientId}/prescriptions/{prescriptionId}/epcsSuggestions
Get EPCS Suggested Prescription Schedule
Prescriptions_GetEPCSSuggestionsV2 2 params → 200
GET
/api/patients/{patientId}/prescriptions
Get patient's prescriptions
Prescriptions_GetPatientPrescriptionsV2 8 params → 200
DELETE
/api/patients/{patientId}/prescriptions
Delete Prescriptions
Prescriptions_DeletePrescriptionsV2 1 param body → 200
PUT
/api/patients/{patientId}/prescriptions/coded/{prescriptionId}
Edit Coded Prescription
Prescriptions_EditCodedPrescriptionV2 2 params body → 200
PUT
/api/patients/{patientId}/prescriptions/supply/{prescriptionId}
Edit Coded Supply Prescription
Prescriptions_EditCodedSupplyV2 2 params body → 200
PUT
/api/patients/{patientId}/prescriptions/supply/freetext/{prescriptionId}
Edit Free Text supply Prescription
Prescriptions_EditFreeTextSupplyPrescriptionV2 2 params body → 200
PUT
/api/patients/{patientId}/prescriptions/compiledcompound/{prescriptionId}
Edit Compiled Compound
Prescriptions_EditCompiledCompoundV2 2 params body → 200
POST
/api/patients/{patientId}/prescriptions/send
Send Prescriptions
Prescriptions_SendPrescriptionsV2 1 param body → 200
POST
/api/patients/{patientId}/prescriptions/coded
Add Coded Prescription
Prescriptions_AddCodedPrescriptionV2 1 param body → 200
POST
/api/patients/{patientId}/prescriptions/supply
Add Coded Supply Prescription
Prescriptions_AddCodedSupplyV2 1 param body → 200
POST
/api/patients/{patientId}/prescriptions/sendEpcs
Send EPCS Prescriptions
Prescriptions_SendEpcsPrescriptionsV2 1 param body → 200
POST
/api/patients/{patientId}/prescriptions/setPrinted
Set Prescriptions Printed
Prescriptions_SetPrescriptionsPrintedV2 1 param body → 200
POST
/api/patients/{patientId}/prescriptions/readyToSign
Set Prescriptions Ready To Sign
Prescriptions_SetPrescriptionsReadyToSignV2 1 param body → 200
POST
/api/patients/{patientId}/prescriptions/sendToAddress
Send Prescriptions With Address
Prescriptions_SendToAddressPrescriptionsV2 1 param body → 200
POST
/api/patients/{patientId}/prescriptions/supply/freetext
Add Free Text Supply Prescription
Prescriptions_AddFreeTextSupplyPrescriptionV2 1 param body → 200
POST
/api/patients/{patientId}/prescriptions/compiledcompound
Add Compiled Compound
Prescriptions_AddCompiledCompoundV2 1 param body → 200
POST
/api/patients/{patientId}/prescriptions/{prescriptionId}/copy
Copy Prescription For Patient
Prescriptions_CopyPatientPrescriptionV2 2 params body → 200
POST
/api/patients/{patientId}/prescriptions/{prescriptionId}/cancel
Cancel Prescription
Prescriptions_CancelPrescriptionV2 2 params body → 200
POST
/api/patients/{patientId}/prescriptions/{prescriptionId}/ignoreError
Ignore Error For Prescription
Prescriptions_IgnoreAlertV2 2 params body → 200
POST
/api/patients/{patientId}/prescriptions/{prescriptionId}/medicationStatus
Update Prescription's medication Status
Prescriptions_UpdatePrescriptionStatusV2 2 params body → 200
PATCH
/api/patients/{patientId}/prescriptions/{prescriptionId}/pharmacy
Change Prescription Pharmacy
Prescriptions_ChangePrescriptionPharmacyV2 2 params body → 200

Schemas 55

The contract defines 55 schemas that model the data the API accepts and returns. The most detailed are Prescription_2 (40 properties), Prescription_3 (40 properties), CompoundPrescriptionRequest (25 properties), CodedPrescriptionRequest (25 properties). Each schema is shown below with its type and property counts.

PrescriptionListResult
ResultStatus
object
2 properties
PrescriptionResult
Prescription
object
12 properties
Medication
object
9 properties
MedicationHistoryResult
ApiResult
object
1 property
PageResult
object
5 properties
Diagnosis
object
3 properties
Result
object
Represents the result of a service operation.
2 properties 1 required
PrescriptionWithClinicianReferenceNumberOverrides
object
2 properties
PrescriptionResponse
object
2 properties
CompoundPrescriptionRequest
object
25 properties 7 required
ChangePrescriptionPharmacyRequest
object
1 property 1 required
SendEpcsPrescriptionsRequest
object
4 properties 2 required
PrescriptionSnapshotResponse
object
2 properties
FreeTextSupplyPrescriptionRequest
object
25 properties 7 required
PageResult_2
object
6 properties
AgentSnapshot
object
2 properties
ClinicianReferenceNumberOverrides
object
2 properties
ListResponse_PrescriptionLog
object
Represents a generic response containing a list of objects.
2 properties
PagedListResponse_Prescription
object
3 properties
CodedSupplyRequest
object
24 properties 6 required
CodedPrescriptionRequest
object
25 properties 6 required
PrescriptionIdListRequest
object
1 property
RTPSCoupon
object
4 properties
PrescriptionsReadyToSignRequest
object
1 property 1 required
PrescriptionDiagnosis
object
2 properties
PrescriptionLog
object
7 properties
EpcsSuggestions
object
3 properties
PrescriptionSnapshot
object
6 properties
DeaNumber
object
3 properties 1 required
PrescriberSnapshot
object
5 properties
PatientSnapshot
object
4 properties
EpcsSuggestionsResponse
object
2 properties
PharmacySnapshot
object
4 properties
SupervisorSnapshot
object
5 properties
Response
object
The result of the operation.
1 property
Prescription_2
object
40 properties
UpdatePrescriptionMedicationStatusRequest
object
3 properties 1 required
CancelPrescriptionRequest
object
1 property
IdentifierResponse
object
Represents a generic response containing an entity identifier.
2 properties
MedicationSnapshot
object
10 properties
CompoundIngredient
object
5 properties 1 required
PrescriptionDiagnosisIds
object
2 properties
SendPrescriptionsRequest
object
3 properties 1 required
SendPrescriptionsWithAddressRequest
object
8 properties 5 required
AddressSnapshot
object
5 properties
IgnoreAlertRequest
object
1 property
ScheduleInfo
object
3 properties
CopyPrescriptionRequest
object
1 property
PrescriptionResponse_2
object
2 properties
PageResult_3
object
6 properties
PagedListResponse_Prescription_2
object
3 properties
Prescription_3
object
40 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

dosespot-prescriptions-api-openapi.yml Raw ↑

Other APIs DoseSpot publishes across the network.

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