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

MedAdvisor Booking Service API

The BookingService API from MedAdvisor — 34 operation(s) for bookingservice.

MedAdvisor Booking Service API is one of 14 APIs that MedAdvisor publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 34 operations across 34 paths, and defines 41 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://pharmacy-unified.api.medadvisor.com.au.

34 operations 34 paths 41 schemas 2 DELETE14 GET18 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://pharmacy-unified.api.medadvisor.com.au
Authentication
API Key
Resource Areas
1

Authentication & Security 1

MedAdvisor Booking Service API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Bearer).

  • Bearer — JWT Authorization header using the Bearer scheme. Example: "Authorization: Bearer {token}"

Paths & Operations 34

Across 34 paths, the API surfaces 34 operations — 2 DELETE, 14 GET, 18 POST. Each is listed below with its method, path, parameters, and response codes.

BookingService 34
GET
/api/v1/bookingservice/pharmacy/gettime
Get Pharmacy Time
BookingService_GetPharmacyTime → 200
GET
/api/v1/bookingservice/pharmacy/allservices
Alls the services.
BookingService_AllServices → 200
GET
/api/v1/bookingservice/pharmacy/eventresource
Retrieve Event Resources
BookingService_RetrieveEventResources → 200
GET
/api/v1/bookingservice/pharmacy/services/dynamic
Retrieve Dynamic Services.
BookingService_RetrieveDynamicServices → 200
GET
/api/v1/bookingservice/pharmacy/services/available
Retrieve Available Services
BookingService_RetrieveAvailableServices → 200
GET
/api/v1/bookingservice/pharmacy/eventresource/{resourceId}
Retrieve Event Resources
BookingService_RetrieveEventResource 1 param → 200
GET
/api/v1/bookingservice/pharmacy/services/booking/{bookingId}
Retrieve Booking
BookingService_RetrieveBooking 1 param → 200
GET
/api/v1/bookingservice/pharmacy/calendartoken/{resetStaffUrl}
BookingService_RetrieveCalendarAccessTokens 1 param → 200
GET
/api/v1/bookingservice/pharmacy/services/dynamic/{capabilityId}
Retrieve Dynamic Services by Capability Id.
BookingService_RetrieveDynamicServices 1 param → 200
GET
/api/v1/bookingservice/pharmacy/services/available/{capabilityId}
Retrieve Available Services by Capability Id
BookingService_RetrieveAvailableServices 1 param → 200
GET
/api/v1/bookingservice/pharmacy/calendartokendetails/{calendarToken}/{staffToken}
BookingService_RetrieveCalendarTokenDetails 2 params → 200
GET
/api/v1/bookingservice/pharmacy/retrieveavailabletimeslots
Retrieve available times slots
BookingService_RetrieveAvailableTimeslots 2 params → 200
GET
/api/v1/bookingservice/pharmacy/availabletimeslotnewbooking
Retrieves the available time slot new booking.
BookingService_RetrieveAvailableTimeSlotNewBooking 3 params → 200
GET
/api/v1/bookingservice/pharmacy/retrieveeventbookings
Retrieves the event bookings.
BookingService_RetrieveEventBookings 4 params → 200
POST
/api/v1/bookingservice/patientsearch
Searches the patients.
BookingService_SearchPatients body → 200
POST
/api/v1/bookingservice/services/update
Update services
BookingService_UpdateEventService body → 200
POST
/api/v1/bookingservice/services/historic
Retrieve Historic Bookings
BookingService_RetrieveHistoricBookings body → 200
POST
/api/v1/bookingservice/createeventbooking
Creates the event booking.
BookingService_CreateEventBooking body → 200
POST
/api/v1/bookingservice/services/suggested
Retrieve Suggested Services
BookingService_RetrieveSuggestedServices body → 200
POST
/api/v1/bookingservice/eventbooking/update
Updates the event booking.
BookingService_UpdateEventBooking body → 200
POST
/api/v1/bookingservice/eventresource/update
Updates the event resource.
BookingService_UpdateEventResource body → 200
POST
/api/v1/bookingservice/eventpreferences/update
Updates the event preferences.
BookingService_UpdateEventPreferences body → 200
POST
/api/v1/bookingservice/pharmacy/services/generate
Generate Service Booking
BookingService_GenerateServiceBooking body → 200
POST
/api/v1/bookingservice/pharmacy/print/{bookingCode}
Prints the specified booking code.
BookingService_Print 1 param → 200
POST
/api/v1/bookingservice/pharmacy/services/bookingedit
Event booking edit
BookingService_EditBookingWithCheck body → 200
POST
/api/v1/bookingservice/pharmacy/eventresource/create/{name}
Creates the event resource.
BookingService_CreateEventResource 1 param → 200
POST
/api/v1/bookingservice/pharmacy/services/delete/{serviceId}
Deletes the event service.
BookingService_DeleteEventService 1 param → 200
POST
/api/v1/bookingservice/pharmacy/eventbooking/{bookingId}/delete
Deletes the event booking.
BookingService_DeleteEventBooking 1 param → 200
POST
/api/v1/bookingservice/pharmacy/eventresource/update/{resourceId}
Update Event Resource Associate Service
BookingService_UpdateEventResourceAssociateService 1 param body → 200
POST
/api/v1/bookingservice/pharmacy/eventresource/{resourceId}/delete
Deletes the event resource.
BookingService_DeleteEventResource 1 param → 200
POST
/api/v1/bookingservice/pharmacy/bookingsearch
Booking search.
BookingService_BookingSearch 1 param → 200
POST
/api/v1/bookingservice/pharmacy/services/availableresource/{capabilityId}
Retrieve Available Services Resource For Capability
BookingService_RetrieveAvailableResourceForCapability 2 params → 200
DELETE
/api/v1/bookingservice/pharmacy/services/deletebooking/{bookingId}
Delete an event (calendar) booking
BookingService_DeleteServiceBooking 1 param → 200
DELETE
/api/v1/bookingservice/deletebookingrequest/{patientId}/{bookingId}
Deletes the booking request.
BookingService_DeleteBookingRequest 2 params → 200

Schemas 41

The contract defines 41 schemas that model the data the API accepts and returns. The most detailed are MedAdvisor.Framework.Interface.Store (108 properties), MedAdvisor.PharmacyUnifiedAPI.v1.Models.EventBookingModel (78 properties), MedAdvisor.Framework.Interface.EventBookingWrapper (72 properties), MedAdvisor.Framework.Interface.UserSearch (61 properties). Each schema is shown below with its type and property counts.

MedAdvisor.Framework.Interface.PharmacyLoyaltyProvider
object
3 properties
MedAdvisor.Framework.Interface.BookingTokenKey
object
5 properties
MedAdvisor.Framework.Interface.Results.BookingStatusResult
object
4 properties
MedAdvisor.PharmacyUnifiedAPI.v1.Models.BookingRequestModel
object
5 properties
MedAdvisor.PharmacyUnifiedAPI.v1.Models.EventServiceModel
object
8 properties
MedAdvisor.Framework.Interface.ElectronicPrescribingSettings
object
2 properties
MedAdvisor.Framework.Interface.DateTimeResult
object
3 properties
MedAdvisor.Framework.Interface.CalendarAccessTokenResult
object
5 properties
MedAdvisor.Framework.Interface.GPPractitioner
object
26 properties
MedAdvisor.Framework.Interface.Store
object
108 properties
MedAdvisor.PharmacyUnifiedAPI.v1.Models.BookingValidateModel
object
15 properties
MedAdvisor.Framework.Interface.BookingStatus
object
12 properties
MedAdvisor.Framework.Interface.BookingAvailabilityResult
object
8 properties
MedAdvisor.Framework.Interface.UserSearchResult
object
4 properties
MedAdvisor.Framework.Interface.PharmacyExternalSystem
object
8 properties
MedAdvisor.PharmacyUnifiedAPI.v1.Models.EventBookingModel
object
78 properties
MedAdvisor.Framework.Interface.Subscription
object
9 properties
MedAdvisor.PharmacyUnifiedAPI.v1.Models.PrescreenFormModel
object
22 properties
MedAdvisor.Framework.Interface.BookingAvailability
object
32 properties
MedAdvisor.Framework.Interface.EventBookingWrapper
object
72 properties
MedAdvisor.BLL.Recurrence.RecurrencePattern
object
17 properties
MedAdvisor.Framework.Interface.EventRecurrence
object
15 properties
MedAdvisor.Framework.Interface.WhiteLabelSettings
object
25 properties
MedAdvisor.PharmacyUnifiedAPI.v1.Models.EventPreferenceModel
object
6 properties
MedAdvisor.Framework.Interface.EventResourceResult
object
11 properties
MedAdvisor.PharmacyUnifiedAPI.v1.Models.UserSearchModel
object
22 properties
MedAdvisor.PharmacyUnifiedAPI.v1.Models.HistoricBookingModel
object
4 properties
MedAdvisor.PharmacyUnifiedAPI.v1.Models.EventResourceModel
object
12 properties
MedAdvisor.Framework.Finance.PharmacyTier
object
5 properties
MedAdvisor.Framework.Interface.HealthNotesPharmacyDetail
object
13 properties
MedAdvisor.Framework.Interface.OperatingHour
object
5 properties
MedAdvisor.Framework.Interface.UserSearch
object
61 properties
MedAdvisor.Framework.Interface.EventBookingResult
object
9 properties
MedAdvisor.Framework.Interface.GPPractice
object
31 properties
MedAdvisor.PharmacyUnifiedAPI.v1.Models.CalenderTokenModel
object
17 properties
MedAdvisor.Framework.Interface.ModuleActivation
object
59 properties
MedAdvisor.Framework.Interface.Location
object
19 properties
MedAdvisor.Framework.Interface.EventAvailability
object
4 properties
MedAdvisor.Framework.Interface.Owner
object
16 properties
MedAdvisor.Framework.Interface.EventResourceWrapper
object
11 properties
MedAdvisor.PharmacyUnifiedAPI.v1.Models.SuggestedSearchModel
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

medadvisor-bookingservice-api-openapi.yml Raw ↑

Other APIs MedAdvisor publishes across the network.

MedAdvisor 3rd-Party Integration API
MedAdvisor Account API
MedAdvisor Booking API
MedAdvisor Calendar Setting API
MedAdvisor Clinic API
MedAdvisor Communication API
MedAdvisor Config API
MedAdvisor Head Office API
MedAdvisor Inbox API
MedAdvisor Logging API
MedAdvisor Pharmacist API
MedAdvisor Pharmacy API
Where this information came from

This is an independent, third-party profile of MedAdvisor Booking Service 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.