EHR IntegrationHealthcare Interoperability

DoseSpot API Integration Guide: e-Prescribing (2026)

November 18, 202616 min readUpdated Nov 18, 2026
Written by
Jitendra Choudhary
Jitendra Choudhary

CTO & Co-Founder

CTO & Co-Founder at Nirmitee.io. Architects healthcare integrations across FHIR, SMART on FHIR, ABDM and NHCX, writing from production experience taking hospital software from sandbox to go-live.

DoseSpot API Integration Guide: e-Prescribing (2026)

DoseSpot is an e-prescribing platform that EHRs, telehealth apps and dental systems embed so their clinicians can send prescriptions to pharmacies. With the DoseSpot API, your product can create patients, send prescriptions, search pharmacies and handle refill requests. You can use DoseSpot's own embedded screen or build your own screens. [D1] [D2] [D3]

This guide is for a product lead or buyer who has to add prescribing through DoseSpot, and for the engineer who will build it. It covers the three integration routes and every endpoint group on DoseSpot's public API help page. It also covers EPCS, identity proofing, onboarding, certification and what DoseSpot leaves unpublished. If prescribing is one part of a wider EHR build, see our EHR integration services. Last checked: Nov 18, 2026.

DoseSpot API at a glance

Question Short answer
Who grants access? DoseSpot. You start with a demo request, then a dedicated Integration and Implementation Specialist runs the project plan. [D40] [D48]
Who signs? Your company signs DoseSpot's legal agreements and attestations for identity proofing, EPCS audit and reselling. Each prescriber completes identity proofing personally. [D42] [D65]
Are there public documents? Partly. An API help page on the staging host lists every operation with sample bodies, but the descriptions are blank. Partners get API guides, Postman and Swagger. [D6] [D7] [D13]
Which routes exist? Jumpstart (embedded iFrame), Full Integration (API under your screens) and TreatRx (standalone). [D1] [D3]
What does it cost? DoseSpot publishes no price. Sales gives a custom quote, and the API guide comes at no extra cost. [D82] [D14]
How long does it take? As little as 30 days for Jumpstart, 3 to 6 months for Full Integration, both including certification. [D86] [D87]
What is the biggest limit? Surescripts certification for API-only builds, and no published rate limits or webhook format. [D46] [D80] [D62]

What can you build with the DoseSpot API?

Eight use cases follow. Each points to a row in the read and write table in section 6 (rows R1 to R10). DoseSpot publishes build-time ranges by route, which section 10 covers, so the use cases carry no separate estimate. Build complexity is our own rating.

Eight use cases. Complexity is our own rating. Open a use case below for the detail.
1. Add e-prescribing to a telehealth visit
  • Who it is for: telehealth and virtual care platforms.
  • The value: the clinician prescribes at the end of the video visit, and the prescription goes to the patient's chosen pharmacy without leaving your app.
  • Build complexity: low with Jumpstart, medium with Full Integration.
  • How well it works: well. Jumpstart embeds DoseSpot's prescribing screen as an iFrame. With Full Integration you create the patient, pick the pharmacy and send the prescription by API. [D3] [D20] [D21] [D22] See rows R1, R2 and R3.
2. Build prescribing screens inside your own EHR
  • Who it is for: EHR and practice management vendors that want prescribing to look like the rest of the product.
  • The value: one workflow in your design, with DoseSpot doing drug data, routing and certification behind it.
  • Build complexity: high.
  • How well it works: well, though it takes the most build effort. Full Integration exposes coded, NDC, free text, compound and supply prescriptions, plus status, copy, cancel and change pharmacy. [D2] [D21] See row R2.
3. Let patients pick a pharmacy before the visit
  • Who it is for: patient intake and booking apps.
  • The value: the pharmacy is set on the patient before the clinician opens the chart, which saves a step at the end of the visit.
  • Build complexity: low.
  • How well it works: well. Pharmacy search takes name, city, state, ZIP, address, phone or fax, specialty and NCPDP ID, and a pharmacy can be attached to the patient. [D22] See row R3.
4. Handle pharmacy refill and change requests in your inbox
  • Who it is for: EHRs and care teams that run a task queue.
  • The value: refill and RxChange requests from pharmacies show up next to other tasks, and the clinician approves or denies in one place.
  • Build complexity: medium.
  • How well it works: well. The API lists refill and RxChange requests by clinician, clinic or patient, and has approve, deny, replace and reconcile calls. [D24] See row R5.
5. Enroll and identity-proof prescribers from your admin screens
  • Who it is for: platforms that onboard many clinicians, such as telehealth networks.
  • The value: a new clinician is set up, proofed and ready for controlled substances without a separate DoseSpot login step.
  • Build complexity: medium.
  • How well it works: fair. The API has calls to create clinicians, run identity proofing questions and one-time codes, check registration status, start Duo activation and set a PIN. Failed proofing still goes through your support team, since DoseSpot does not help prescribers directly. [D26] [D68] See row R7.
6. Prescribe controlled substances (EPCS)
  • Who it is for: behavioral health, pain, ADHD and addiction treatment platforms.
  • The value: Schedule II to V prescriptions go electronically, which many states require.
  • Build complexity: medium to high.
  • How well it works: well, after each prescriber passes identity proofing and sets up two-factor. There is a separate sendEpcs call and an EPCS suggestions call, and the PDMP check is in the clinician group. [D21] [D26] [D69] [D72] See rows R2 and R7.
7. Show the patient's drug price and coverage at the point of prescribing
  • Who it is for: EHRs and telehealth apps where patients pay out of pocket or through a pharmacy benefit.
  • The value: the clinician sees formulary status, alternatives and price before sending, so fewer prescriptions are abandoned at the pharmacy.
  • Build complexity: medium.
  • How well it works: well for insured patients. The API has eligibility, formulary, therapeutic alternatives and prescription benefit calls. [D28] [D44] See row R8.
8. Start and track prior authorizations from the chart
  • Who it is for: specialty practices and platforms that prescribe drugs with frequent prior auth, such as GLP-1 and specialty biologics.
  • The value: the prior auth starts with the prescription. The status shows in the chart.
  • Build complexity: medium to high.
  • How well it works: well. The API covers initiate, answer questions, attach, submit, appeal, cancel and history. DoseSpot states it runs ePA through CoverMyMeds and Surescripts. [D29] [D73] See row R9.

The eight DoseSpot use cases compared

# Use case Who it is for Complexity Row
1. Telehealth e-prescribing Telehealth platforms Low R1 to R3
2. Own prescribing screens EHR vendors High R2
3. Pharmacy picked at intake Intake and booking apps Low R3
4. Refill and RxChange inbox EHRs and care teams Medium R5
5. Prescriber enrollment Telehealth networks Medium R7
6. Controlled substances Behavioral health, pain Medium to high R2, R7
7. Price and coverage check EHRs and telehealth Medium R8
8. Prior authorization Specialty practices Medium to high R9

How do you get access to the DoseSpot API?

You get access by contracting with DoseSpot. There is no public self-serve developer signup. You request a demo, sign the agreements, and a DoseSpot specialist runs the project with you. [D40] [D48]

Paperwork, Surescripts review, then identity proofing per prescriber.

The DoseSpot onboarding steps

  1. Kickoff. DoseSpot assigns a dedicated Integration and Implementation Specialist and builds a project plan "including implementation timing, training, and documentation". [D40]
  2. Paperwork. DoseSpot lists legal agreements and identity proofing, with a vendor and provider verification attestation. For controlled substances, you also sign an EPCS audit attestation. A reseller attestation and a screen demo certification attestation complete the list. [D42]
  3. Surescripts review. It starts during the paperwork. Surescripts asks for its questionnaire, reviews your website, and requires four NCPDP SCRIPT message types: NewRx, RxCancel, RxRenewals and RxChange. [D43]
  4. Build and test in DoseSpot's staging environment. [D50]
  5. Go-live, after which you get an Account Manager and a Technical Resource. [D41]

Who signs on the customer side

Your company signs the DoseSpot agreements. Each prescriber who sends or prints e-prescriptions must complete personal identity proofing, which DoseSpot states DEA rules require. [D42] [D65]

Who supports prescribers

Your team supports them. DoseSpot states it is a B2B provider that "does not train users directly". Its FAQ sends prescribers to their EHR for help with login, launch and identity proofing. [D47] [D68] Plan a support process for your clinicians before go-live.

What does DoseSpot API access give you?

DoseSpot access gives you a staging environment for building and testing, then production. DoseSpot states that clients that move to API v2 get "a new client in our Staging environment". The public API help pages are on the staging host. [D50] [D51]

Stage What you get
Before contract The public API help page: operation list, sample JSON and XML bodies, field rules. [D6] [D8]
Staging A staging client, API guides, Postman, Swagger and the API change list. [D13] [D50]
Production Live prescribing for enrolled clinicians, after certification and a coordinated go-live. [D52]

Medplum, a platform that offers a DoseSpot integration, documents https://my.dosespot.com/webapi/v2/ as the production base path in its own set-up guide. [D53]

What are the ways to integrate with DoseSpot?

DoseSpot offers three routes. The choice decides how much you build and how long certification takes. [D1]

The three routes DoseSpot offers, with its stated times.
Route What it is Fits when Stated time
Jumpstart DoseSpot's prescribing screen, embedded "as an iFrame, object, or web control", styled with DoseSpot's CSS file. Up to about 70 API calls. [D3] [D4] [D5] You want e-prescribing live fast and accept DoseSpot's screens. As little as 30 days. [D86]
Full Integration Your own screens over the DoseSpot API. DoseSpot cites 140+ to 250+ API calls. [D2] [D5] You are an EHR that wants prescribing in its own design. 3 to 6 months. [D87]
TreatRx Standalone DoseSpot prescribing, no EHR needed, for practices with 10 prescribers or fewer. [D1] A small practice that does not need prescribing inside another system. Non-controlled in 24 hours. [D89]

Both Jumpstart and Full Integration use push notifications for events. [D60] Neither route uses FHIR or HL7 on the API help page. [D100]

What can you read and write with the DoseSpot API?

The DoseSpot API help page lists 166 operations in 19 groups. Paths below are relative to the API base, as the help page shows them. [D6]

Ten areas, with example paths from the API help page.
Row Area Main operations
R1 Patients POST api/patients, GET/POST api/patients/{patientId}, GET api/patients/search, patient prescriptions by date range, POST api/patients/merge, /transfer, /insurance [D20]
R2 Prescriptions POST .../prescriptions/coded, /ndc, /freetext, /compound, /supply; /send, /send/{pin}, /sendEpcs, /sendOnBehalfOf; /cancel, /changePharmacy, /updateStatus, /log, /copy [D21]
R3 Pharmacies GET api/pharmacies/search (name, city, state, zip, address, phone or fax, specialty, NCPDP ID), GET api/pharmacies/{pharmacyId}, add or remove a patient pharmacy [D22]
R4 Drugs, allergies, history medication search and select by RxCUI, interactions, medication history, allergies, compounds, supplies [D23]
R5 Refills and RxChange list by clinician, clinic or patient; approve, deny, replace, change patient, reconcile [D24]
R6 Notifications counts, batch counts, errors, errors by client [D25]
R7 Clinicians and identity proofing create and update clinician, identity proofing questions and one-time code, registration status, Duo activation, PIN, legal agreements, PDMP, lookup by NPI and DEA [D26]
R8 Eligibility and benefits eligibilities, formulary, therapeutic alternatives, prescription benefits [D28]
R9 Prior authorization initiate, answer, attach, submit, appeal, cancel, history [D29]
R10 Clinics and diagnosis clinics and clinic groups; ICD and CDT diagnosis search [D27] [D30]

Required fields on a coded prescription

POST api/patients/{patientId}/prescriptions/coded requires the drug ids, Refills (0 to 99), DispenseUnitId, Quantity, Directions (up to 1,000 characters) and Status. DaysSupply runs 0 to 365, and NonDoseSpotPrescriptionId (up to 35 characters) holds your own id. [D15]

What is not possible with the DoseSpot API?

The DoseSpot API covers prescribing only. The gaps below come from the public help page as read on Nov 18, 2026.

The gaps to plan around.
  • No FHIR or HL7. The help page has no FHIR or HL7 operation. You map your data to DoseSpot's own JSON or XML, the same gap our NCPDP SCRIPT to FHIR MedicationRequest post covers. [D100] [D8]
  • No webhook registration in the API. DoseSpot states it offers push notifications, but the payload format and set-up are not public, and the help page has no subscription call. The workaround is to ask for the push guide, or poll the notification counts. [D60] [D62] [D101] Medplum documents that its integration polls DoseSpot notifications. [D63]
  • No labs. There are no lab order or result operations. [D102]
  • No hard delete of patients. Patients can be merged or transferred. Delete exists only for prescriptions, patient pharmacies and prior auth attachments. [D103]
  • No endpoint descriptions in public. Each operation says "No documentation available". The meaning of each call is in the partner API guide. [D104]
  • No alternative to credit-based identity proofing. A prescriber with no credit history has no other route in DoseSpot. [D67]

What are the DoseSpot API limits?

DoseSpot states that "All endpoints will enforce reasonable rate limits" and that going over returns HTTP 429. It publishes no numbers. [D80] Ask for the per-endpoint limits in writing.

Limit Value
Rate limit Enforced, HTTP 429 when exceeded, numbers not published [D80]
Refills per prescription 0 to 99 [D15]
Days supply 0 to 365 [D15]
Directions up to 1,000 characters [D15]
Pharmacy notes up to 210 characters [D15]
Your own prescription id up to 35 characters [D15]
Identity proofing personal cell phone for the one-time code; US photo ID only for the facial route [D66] [D71]
Formats JSON or XML [D8]

How much does DoseSpot integration cost?

DoseSpot publishes no price. Its own pricing article says to "contact our sales team for a customized pricing consultation". [D82] Two cost facts are public:

What to get in writing from DoseSpot.
  • The API guide for your integration type comes "at no additional cost". [D14]
  • DoseSpot's ONC disclosure states "No additional costs over the standard license fee" for the certified capabilities it lists. [D84]

Ask DoseSpot for: the license model (per prescriber, per month or annual), the implementation fee, any EPCS or identity proofing fee per prescriber, and the fee for prior auth and price check features.

How long does a DoseSpot integration take?

DoseSpot publishes its own time ranges by route. [D86] [D87] [D88] [D89]

Route Build only With testing and certification
Jumpstart 1 to 2 weeks on average as little as 30 days
Full Integration 6 to 12 weeks 3 to 6 months
TreatRx not applicable non-controlled in 24 hours

Identity proofing adds time per prescriber. If the one-time code does not arrive, Experian sends a certified letter, which "usually takes 3-5 business days". [D66]

How do you build a DoseSpot API integration, step by step?

A DoseSpot build runs in five stages: contract and certification paperwork, clinician set-up, patient and pharmacy, the prescription itself, and the follow-up events.

Stage 1. Contract, paperwork and Surescripts

Sign the agreements and attestations, and start the Surescripts review. If you are an API-only build, DoseSpot's ONC page states you need separate Surescripts certifications for routing, for formulary, eligibility and medication history, and for EPCS. [D42] [D43] [D46]

Stage 2. Set up clinics and clinicians

Create the clinic, then each clinician. Run identity proofing (POST api/clinicians/idp, idpAnswers, idpOtp) and check GET api/clinicians/{clinicianId}/registrationStatus. For controlled substances, start Duo activation and set the PIN. [D26] [D27] [D69]

Stage 3. Create the patient and pharmacy

Create the patient with POST api/patients, keep DoseSpot's patient id, and store your own record number in NonDoseSpotMedicalRecordNumber. Search the pharmacy and attach it. [D17] [D20] [D22]

Stage 4. Write and send the prescription

Search the drug, write a coded prescription, then send it. Controlled substances go through sendEpcs. Here is a coded prescription request in the shape DoseSpot's help page shows. The values are a synthetic example of ours.

The calls for one prescription, in order.
POST api/patients/{patientId}/prescriptions/coded
Content-Type: application/json

{
  "LexiGenProductId": 12345,
  "LexiDrugSynId": 67890,
  "LexiSynonymTypeId": 1,
  "Refills": 2,
  "DaysSupply": 30,
  "DispenseUnitId": 26,
  "Quantity": 30,
  "Directions": "Take 1 tablet by mouth once daily",
  "PharmacyId": 1001,
  "NoSubstitutions": false,
  "NonDoseSpotPrescriptionId": "ORDER-0001",
  "Status": 1
}

The response carries the new prescription id and a result code:

{
  "Id": 555001,
  "Result": {
    "ResultCode": "OK",
    "ResultDescription": ""
  }
}

Then send it with POST api/patients/{patientId}/prescriptions/{prescriptionId}/send. [D15] [D21]

Stage 5. Track status, refills and changes

Read the prescription log and status, watch notification counts and errors, and work the refill and RxChange queues. DoseSpot states push notifications "reduce the need to poll for data through the API". [D21] [D24] [D25] [D61]

Which DoseSpot API quirks should you know?

These come from DoseSpot's own pages and API help, as read on Nov 18, 2026.

API call counts disagree

The Full Integration page says over 250 API calls, the integrations page and EHR page say 140+, Jumpstart says up to 70, and the public help page lists 166 operations. Ask DoseSpot which list applies to your contract. [D5] [D6]

Lexicomp ids in the v2 samples

DoseSpot announced its move from Lexicomp to Medi-Span, yet the staging sample for a coded prescription still uses LexiGenProductId and other Lexi fields. Confirm the drug id fields for your build. [D9] [D16]

Not every record migrates

DoseSpot states it "will not be able to migrate 100% of these records" from Lexicomp, and unmigrated items ask the user to create a new one. [D12]

Token endpoint changed in v2

DoseSpot asks v2 clients to update their token endpoint integration. [D11]

Every endpoint description is blank

The help page reads "No documentation available" for all 166 operations, so field rules and samples are the only public guide. [D7]

XML and JSON both accepted

Each operation shows samples in both formats. [D8]

Identity proofing help goes through you

DoseSpot "cannot assist directly with IDP issues", so failed proofing lands on your support desk. [D68]

Medi-Span updates weekly

Lexicomp updated monthly. Drug search results can change week to week. [D10]

What should you check before you sign with DoseSpot?

Security and compliance, as DoseSpot states them

DoseSpot states it is HITRUST and SOC2 Type II certified, that its Jumpstart and Full Integration platforms are Surescripts and EPCS certified, and that it pursued EPCS certification with Drummond Group. [D90] [D64] Its ONC listing is DoseSpot 8.0, certified Jun 22, 2022. [D85] It stores only the identity proofing pass date and the two-factor reference number. [D70]

Rules for your side

Every prescriber who can send or print e-prescriptions must pass identity proofing. Controlled substances need a PIN and a Duo code on each send. [D65] [D69] Your website goes through Surescripts review. [D43]

Testing

Build in staging, run regression tests with DoseSpot, and coordinate go-live with them. [D50] [D52]

Questions to ask DoseSpot before you sign

  1. Which route and API call list does the contract cover?
  2. What is the license model, the implementation fee and any per-prescriber EPCS or identity proofing fee?
  3. What are the rate limits per endpoint?
  4. Which events send push notifications, in what format, and how are retries handled?
  5. How does the Jumpstart launch work: single sign-on parameters, session length and embedding rules?
  6. Which Surescripts certifications does our route need us to complete ourselves?
  7. Which drug id fields apply after the Medi-Span move?
  8. What support do you give our support team when a prescriber fails identity proofing?

What is the next step for a DoseSpot integration?

If your product needs prescribing, the first decision is the route: DoseSpot's embedded screen or your own. Bring that and your controlled-substance needs to a scoping call. If your clinicians already prescribe inside Veradigm EHR, our Allscripts and Veradigm integration guide shows what its APIs expose for prescriptions. See our EHR integration services.

Ready to scale?

Talk to our healthcare engineering team about building, integrating, and shipping faster.

Frequently Asked Questions

Does DoseSpot have a public API?

DoseSpot publishes an API help page on its staging host that lists 166 operations with sample bodies. The full API guides, Postman and Swagger files come with a partner contract.

What is the difference between DoseSpot Jumpstart and Full Integration?

Jumpstart embeds DoseSpot's prescribing screen in your app as an iFrame and can go live in as little as 30 days. Full Integration means your own screens on the API and takes 3 to 6 months, as DoseSpot states.

How much does DoseSpot cost?

DoseSpot publishes no price. Its sales team gives a custom quote. The API guide comes at no extra cost.

Does DoseSpot support EPCS?

Yes. DoseSpot states Jumpstart and Full Integration are EPCS certified, and the API has a separate call to send controlled substance prescriptions.

How does DoseSpot identity proofing work?

Each prescriber answers identity questions through Experian and confirms a one-time code sent to a personal cell phone. A facial recognition route with US photo ID also exists. Controlled substances then need Duo two-factor and a 4-digit PIN.

Does DoseSpot have webhooks?

DoseSpot states it offers push notifications for many events, but does not publish the format. The API also has notification count and error calls you can poll.

Does DoseSpot support FHIR?

The DoseSpot API help page has no FHIR or HL7 operations. Requests and responses are JSON or XML.

Can I search pharmacies through the DoseSpot API?

Yes. Pharmacy search takes name, city, state, ZIP, address, phone or fax, specialty and NCPDP ID.

Is there a DoseSpot sandbox?

Yes. DoseSpot gives clients a staging environment for development and testing before go-live.

Do I need Surescripts certification to use DoseSpot?

For API-only builds, DoseSpot's ONC page states you must complete separate Surescripts certifications for routing, for formulary and medication history, and for EPCS. Surescripts also reviews your website.
Share