docnow24 Integration
docnow24 is a telemedicine platform. These endpoints support the two integration points used by partners running on docnow24: a product feed that your Custom Sync service polls to mirror stock, availability and price, and prescription injection, used after a doctor completes the digital (QES) signature on a prescription.Authentication
Authenticate with your API key via theX-API-Key, X-RxScale-Authorization, or Authorization: Bearer <api-key> header. See Authentication for details.
Product Feed
Retrieve the catalogue of SKUs mapped to your provider account in a shop. Poll this endpoint from your Custom Sync service to mirror stock, availability and price.string
required
Unique identifier for the shop
integer
default:"1"
Page number (1-indexed)
integer
default:"500"
Results per page (max 5000)
string
Filter mapped products by name
read_sku_single_telemedicine_provider
Only SKUs mapped to your provider account and listed in the shop as
ACTIVE or UNLISTED are included. Draft or archived shop products, and SKUs that are deactivated or unmapped, simply stop appearing in the feed — they are never emitted with stock: 0.Example Request
Response
Response Fields
Backoffice Field Mapping
Configure your Custom Sync with this mapping:
We do not send an
active field. Derive availability on your side from stockCount > 0.
Error Responses
Prescription Injection
Submit a signed prescription and its order details after a doctor completes the QES signature. RxScale creates the checkout and, unlessprepaid is 1, sends the patient a Shopify checkout request.
string
required
Unique identifier for the shop
create_prescription_checkout
Request Body
The prescription PDF must be digitally signed (QES). Unsigned PDFs are rejected with
422 unless your provider account has been explicitly configured to allow them.products[].id is resolved against SKUs mapped to your provider account — the same mapping the product feed publishes as flowzUrl. An id that does not resolve is rejected; see Error Responses below.Example Request
Response
prescriptions[].id echoes your internalOrderId. Use prescription_uid to query order status via the Orders endpoint.
Warnings
A successful response can carry an optionalwarnings list. It is only present when there is something to report, so check for the key rather than for an empty list.
phone_not_forwarded means the prescription was accepted, but customer.phone was not set as the contact phone number of the order: either it could not be converted to E.164, or Shopify rejected it as invalid. Correct the number on your side; the request does not need to be repeated.
Error Responses
internalOrderId is only blocked once a submission with that id has been successfully accepted. If an earlier request failed (for example, it returned a 4xx/5xx before completing), resubmitting the same internalOrderId is not blocked and is processed normally — safe to retry after a failed or uncertain request.See Also
- Products — the generic multi-market product listing endpoint
- Prescriptions & Treatments — the generic checkout endpoint
- Orders — query order status by prescription UID