API changelog β August 13, 2024
Updates for this release.
ePrescription
API Endpoint: {api_url}/v1/eprescription/practices
Scenario: This API is used to sync data from Scriptsure to Zenotiβs platform for an already onboarded center.
API method: POST
Earlier behavior: New API. No earlier behavior.
New behavior: Updates data from ScriptSure to Zenotiβs onboarded center.
ePrescription
API Endpoint: {api_url}/v1/eprescription/prescriptions
Scenario: This API upserts ePrescription data into the system when received via a webhook from ScriptSure, ensuring data is synchronized when prescriptions are issued or modified.
API method: POST
Earlier behavior: New API. No earlier behavior.
New behavior: Upserts data of ePrescription into Zenoti DB.
ePrescription
API Endpoint: {api_url}/v1/eprescription/{guest_id}/patient_dashboard_url/generate
Scenario: This API returns a URL to open the ePrescription provider portal.
API method: PUT
Earlier behavior: New API. No earlier behavior.
New behavior: Generates ePrescription provider portal URL
Appointments
API Endpoint: {api_url}/api/Appointments/{InvoiceItemId}/GetMacrosForMembershipHTMLForm/{FormId}
Scenario: This API gets all the membership form macros for a membership being sold.
API method: GET
Earlier behavior: The cross-org API key, Token, and Webstore anonymous token are not restricted.
New behavior: The cross-org API key, Token, and Webstore anonymous token are now restricted
Appointments
API Endpoint: {api_url}/api/Appointments/{InvoiceItemId}/{AppointmentId}/CustomFormManualExpiry
Scenario: This API sets the manual expiry date for the custom form.
API method: POST
Earlier behavior: Does not validate appointment ID or form ID and allows anonymous users.
New behavior: Validates appointment ID or form ID and does not allow anonymous users.