Prescriber licenses / qualifications now have dedicated endpoints for creation and management. Previously these were required to be sent as part of a comprehensive prescriber update. These include a convenience endpoint for updating a qualification by a state’s two-letter abbreviation.
We have renamed “Stuck Items” to “Stuck Orders” and updated the dashboard commensurately; the dedicated notification event has also been updated to
order.stuck. Stuck Orders will include any orders whose underlying prescriptions need clarification.Blend prescription labels can now be printed in “portrait” orientation, allowing for improved brand presentation and patient readability on certain bottle/package sizes. Blend will work with customers during onboarding (and in any subsequent product development) to determine appropriate label orientation for each product.
We have added two additional notification events:
prescription.cancelled and order.stuck. (Note: this was originally item.stuck but was renamed on September 28, 2025.) Cancelled prescription notifications will be sent for any prescription that must be rejected by Blend. Stuck order notifications will be sent whenever an order is unable to be filled. For more on Stuck Orders, read the below changelog item.“Stuck Orders” is a new featured widget and standalone page in the Blend Dashboard. Stuck Orders are any orders require attention or are otherwise unable to be processed. The reasons for an order becoming “stuck”:
- Order Too Early to Fill: A refill order has been created, but insufficient time has elapsed from the prior fill. This will automatically resolve at the specified time.
- Order Missing Active Prescription: An order has been created but no prescription has been sent. (This will present as stuck after 24 hours have elapsed.) Will resolve when a prescription is sent.
- No Refills Remaining and Prescription Expired: A refill order has been created but the prior prescription has been exhausted. Will resolve when a new prescription is sent.
- Order Missing: A prescription has been created but no order has arrived for the prescribed product. This will present as stuck only after 72 hours have elapsed. Will resolve when an order has been created or when the prescription is cancelled.
- Clinical Issue: Our pharmacy staff needs clarification or has concerns about the treatment prescribed. Customers will have an opportunity to respond within the Stuck Items interface.
- Incomplete Patient Information: Specified patient information is required to fill the prescription. Customers can mark as resolved once the patient profile has been updated.
- Incomplete Prescriber Information: Specified prescriber information is required to fill the prescription. Customers can mark as resolved once the prescriber profile has been created or updated.
Email notification subscriptions can now be managed in the “Account” section of the Blend dashboard.
The Notifications endpoints have been updated to allow more fine-grained control over email v. webhook management, with dedicated endpoints for each. Email notifications are configured for the current user’s email address; webhooks are specific to the URL provided. Please note that the prior webhook endpoints will be deprecated in time.
You may now return Orders filtered by multiple
status values, by separating values with a comma (e.g., ?status=shipped,delivered).Blend system status is now available at status.byblend.com.
We have released a single Composite Creation endpoint that allows for the creation of an Electronic Prescription and Order — and, optionally, creation of a Patient and/or Prescriber — in a single request. This does not obviate any existing endpoints and is merely a convenience function for certain customer types.
If sending Electronic Prescriptions via the direct endpoint, you may now optionally create a new patient in the same request. Previously a patient would need to be created in advance. (This mirrors the capability in the Create an Order endpoint.) All required fields apply when creating a patient within the Electronic Prescription workflow (and all optional fields are available); errors will result in the entire transaction failing.New patients can now be created:
- …independently using the Create a Patient endpoint (or within the Blend Dashboard);
- …in the same request as Create an Order
- …in the same request as Create an Electronic Prescription
Blend now prevents the creation of duplicate patients. The API error message will indicate the pre-existing
id of a patient already in the system.When creating an order you may now reference products using your own
sku (all product types) or product_code (prescription products only) values. Previously only the Blend product id was supported.We have added an external_id field to the order entity, should you wish to store your own system’s identifier for orders.You can now update some meta product details, including name, description, sku and (prescription products only) product_code. Products and inventory will continue to be created and managed by Blend.Orders can now be modified within the Dashboard. In addition to Address, an External ID can also be edited for an existing order.You can now subscribe to notifications for delivered orders. When Blend is notified of a successful delivery, we will send both an
order.updated webhook and a specific order.delivered webhook, if you wish to subscribe only to delivery updates.Delivery updates will be provided for native shipments and for any shipments using custom_shipping.You can now subscribe to notifications for new electronic prescriptions. Notifications will be sent for prescriptions that arrive directly via the Electronic Prescriptions endpoint or from Surescripts. For Surescripts prescriptions, notifications will be sent for NewRx, RxChangeResponse, or RxRenewalResponse only.
We have made updates to the behavior of Prescriber management.
- When sending or updating state licenses (qualifications), you no longer need to send all existing qualifications. Only those with updates (e.g., expiration date) need to be sent.
- An update of a license number for an existing state will deactivate any prior state license and replace with the new number.
- If you attempt to create a prescriber who already exists (as determined by prescriber NPI), the existing prescriber will be returned. If the prescriber is not associated with your customer, the prescriber will be associated. To update prescriber data please use the update/edit capabilities.
The
price field has been removed from prescription and non-prescription products. Previously it was a required field.If your customer account allows, you may send a
custom_shipping object during new order creation or order update, providing a prepaid label and other shipping details.You may choose to include
We have improved patient handling logic within the new order creation endpoint. When creating a new order, you may now send:
electronic_prescription_ids (an array of IDs) in the creation of a new order. This is an optional convenience field and is not required; however if you are using the Electronic Prescriptions endpoint to create prescriptions, for your own record-keeping or to optimize prescription matching, you may send your resulting electronic prescription ID values along with a new order.Electronic Prescription IDs will also be returned in any single order GET request (as electronic_prescription_ids). They will not be returned in Get Orders.We have improved patient handling logic within the new order creation endpoint. When creating a new order, you may now send:
patient_idto match an existing patient;patient: {"id": "{UUID}"}to match an existing patient;patient: {"external_id": "{external_id_value}"}to match an existing patient (by your own ID); orpatient: {new patient data}to create a new patient within the new order workflow
patient or patient_id is required.Multiple
medication entities can now be sent (as a medications array) in a single Electronic Prescription request, if all other aspects of the prescription (patient, prescriber, order) are the same across medications. A single medication can still be sent as a standalone object.Blend webhooks can now be optionally authenticated via an
Authorization: Bearer header. Once you generate a secret, it will be sent in all webhook events.For easier testing and integration, you can now manually send sample webhooks to any webhook endpoint, or preview any event webhook payloads.
You can now update an order’s address so long as it is not already shipped (or if shipping is not in process). In the same request you can also choose to update the patient’s address on-file, if the change is permanent.
Added support for creating a New Patient within the
POST body of a New Order. (Previously a Patient would need to be created in a separate request, and referenced in the New Order creation.)You can now direct-submit an electronic prescription in JSON format. Previously the
<SCRIPT> format was required for direct submission of electronic prescriptions.Orders can be paused, unpaused, or cancelled from within the customer dashboard or via API. Only orders that are in a
received state can be paused or cancelled. For orders already in processing, you must contact Blend for special exception handling.