D4Web API

<html>
<h2>1. Overview</h2>
<p>
  The Dental4Web API provides secure, read-only access to dental practice management data stored in
the Dental4Web practice management system. This REST API enables third-party applications to
integrate with practice data while maintaining strict security and privacy controls.
</p>
<h2>2. Multi-tenant Architecture </h2>
<h3>2.1 Infrastructure Overview</h3>
<p>
    • Each Dental4Web customer maintains a dedicated Sybase SQL Anywhere database on AWS EC2 <br>
    • A central configuration database manages <br>
        - Organisation ID to Database Mappings: Links each unique Organisation ID to its  corresponding database.<br>
        - Database Connection Details: Stores connection parameters such as hostname and port for each customer database. <br>
    <i>(Please see Appendix 1 for Enterprise Architecture diagram)</i> <br>
</p>
<h3>2.2 Request Flow</h3>
<p>

1. Request Initiation- A third-party application sends a request to the API, including the
Organisation ID in the request headers.
2. Authentication and Authorization- The API Gateway validates the provided authentication
credentials and authorises the request based on the supplied token.
3. Configuration Lookup- The system queries the central configuration database to retrieve the
connection details associated with the Organisation ID.
4. Database Routing- The request is routed to the appropriate customer database based on the
retrieved connection details.
5. Query Execution- The required query is executed against the customer's database, fetching the
requested data.
6. Response Formation- A standardised response is constructed and returned to the client
application

    ........... <br>
</p>

</html>

Contact Support:
 Name: Support Team
 Email: support@example.com

Introduction

Getting Started

Find Your Use Case

API Response Formats

### **1\. Appointment Resources**

**Provides access to appointment data from the Dental4Web Practice Management System. Developers can fetch schedules, statuses, and details for patients, practitioners, and clinic locations**

**Supports FHIR-compliant Appointment resources when the fhir parameter is enabled for healthcare system interoperability.**

#### **1.1. Get Appointment List**

**End points:****GET /api/v1/appointments****FHIR: GET /api/v1/fhir/appointments**

**Use Cases:**

- **Display all upcoming appointments for a practitioner in a given week.**
    
- **Pulling appointment schedules for syncing with third-party scheduling tools.**
    
- **Filtering past appointments for attendance and cancellation reporting.**
    

**Parameters:**

| **Name** | **Type** | **Required** | **Description** |  
| **patient_id** | **int** | **No** | **Filter by patient** |  
| **practitioner_id** | **int** | **No** | **Filter by practitioner** |  
| **location_id** | **int** | **No** | **Filter by location** |  
| **appointment_id** | **int** | **No** | **Filter by appointment ID** |  
| **appt_book_id** | **int** | **No** | **Filter by appointment book** |  
| **from_date** | **date** | **No** | **Inclusive lower bound (YYYY-MM-DD)** |  
| **to_date** | **date** | **No** | **Inclusive upper bound (YYYY-MM-DD)** |  
| **page** | **int** | **No** | **Pagination, default 1** |  
| **per_page** | **int** | **No** | **Default 10, max 500** |

**Response Field Mapping**

**appointment_id, appointment_status, appointment_status_codes, cancelled, failed, attended, online, confirmed, appointment_type, appointment_date, start_time, end_time, appointment_arrival_time, actual_start_time, actual_end_time, duration, recall_set_linked, patient_id, practitioner_id, location_id, appt_book_id, created_date, updated_date**

**FHIR Mapping**

**Appointment Resource: resourceType: "Appointment", id: appointment_id, status: appointment_status, start: start_time, end: end_time, participant: \[{actor:{reference:"Patient/{patient_id}"}, status:"accepted"}, {actor:{reference:"Practitioner/{practitioner_id}"}, status:"accepted"}, {actor:{reference:"Location/{location_id}"}, status:"accepted"}\]**

**Rules:**

- **At least one filter parameter is required.**
    
- **Date format: YYYY-MM-DD.**
    

#### **1.2. Get Appointment By Id**

**Overview:****Fetches detailed information for a specific appointment using its unique ID. This is particularly useful when displaying appointment details on patient portals, updating an existing booking, or confirming details before a consultation.**

**END Points:****GET /api/v1/appointments/{appointment_id}****FHIR: GET /api/v1/fhir/appointments/{appointment_id}**

**Use Cases:**

- **Displaying appointment details to a patient through an online portal.**
    
- **Retrieving a single appointment to confirm timing and location before sending reminders.**
    
- **Reviewing details before modifying or cancelling a booking.**
    

**Parameters:**

| **Name** | **Type** | **Required** | **Description** |
| --- | --- | --- | --- |
| **appointment_id** | **int** | **No** | **Filter by appointment ID** |

**  
Response Field Mapping**

**appointment_id, appointment_status, appointment_status_codes, cancelled, failed, attended, online, confirmed, appointment_type, appointment_date, start_time, end_time, appointment_arrival_time, actual_start_time, actual_end_time, duration, recall_set_linked, patient_id, practitioner_id, location_id, appt_book_id, created_date, updated_date**

**FHIR Mapping**

**Appointment Resource: resourceType: "Appointment", id: appointment_id, status: appointment_status, start: start_time, end: end_time, participant: \[{actor:{reference:"Patient/{patient_id}"}, status:"accepted"}, {actor:{reference:"Practitioner/{practitioner_id}"}, status:"accepted"}, {actor:{reference:"Location/{location_id}"}, status:"accepted"}\]**

**Rules:**

- **Single record response**
    
- **404 if not found**
    

#### **1.3. Get Cancelled Appointments**

**Overview:****Retrieves a list of cancelled appointments within a given date range and optional filters. This helps track patient no-shows, cancellations, and related operational impact. It can also support follow-up actions such as rescheduling or analysing cancellation trends.**

**End Points:****GET /api/v1/appointments/cancelled**

**Use Cases:**

- **Generating a monthly report of cancelled appointments for operational review.**
    
- **Identifying patients who frequently cancel to address retention or policy issues.**
    
- **Automatically triggering rescheduling workflows when an appointment is cancelled.**
    

**Parameters**

| **Name** | **Type** | **Required** | **Description** |  
| **patient_id** | **int** | **No** | |  
| **practitioner_id** | **int** | **No** | |  
| **location_id** | **int** | **No** | |  
| **appt_book_id** | **int** | **No** | |  
| **from_date** | **date** | **No** | **YYYY-MM-DD** |  
| **to_date** | **date** | **No** | |  
| **mode** | **int** | **No** | **0=appointment date, 1=cancel date** |  
| **page** | **int** | **No** | |  
| **per_page** | **int** | **No** | |

**Response Field Mapping**

**appointment_id, appointment_date, appointment_time, appointment_duration, patient_id, practitioner_id, location_id, appt_book_id, cancel_date, cancel_type**

**Rules:**

- **Requires at least one parameter**
    
- **mode: 0=by appointment date, 1=by cancel date**

Appointment Resources

This endpoint retrieves a list of appointments based on optional filter criteria.<br>
You can filter by parameters such as `patient_id`, `practitioner_id`, `location_id`,
`appointment_id`, `appt_book_id`, `from_date` and `to_date`.

- FHIR - False
- Requires at least one parameter
- Date format: YYYY-MM-DD

GET Appointments

This endpoint retrieves a list of appointments based on optional filter criteria.<br>
You can filter by parameters such as `patient_id`, `practitioner_id`, `location_id`,
`appointment_id`, `appt_book_id`, `from_date` and `to_date`.

- FHIR - True
- Requires at least one parameter
- Date format: YYYY-MM-DD

GET Appointments - FHIR

This endpoint retrieves appointment details based on `appointment_id`.

- FHIR - False
- Single record response
- 404 if not found

GET Appointment By Id

This endpoint retrieves appointment details based on `appointment_id`.

- FHIR - True
- Single record response
- 404 if not found

GET Appointment By ID - FHIR

This endpoint retrieves a list of cancelled appointments based on optional filter criteria.<br>
You can filter by parameters such as `patient_id`, `practitioner_id`, `location_id`,
`mode`, `appt_book_id`, `from_date` and `to_date`.

- FHIR - False
- Requires at least one parameter
- mode: 0=by appointment date, 1=by cancel date

GET Cancelled Appointments

### **2\. Financial Resources**

**The Financial Resources API provides secure access to billing and payment data stored in the Dental4Web Practice Management System. It enables third-party applications to retrieve transaction histories, invoice details, receipt records, and other financial information to support accounting, reporting, and integration with external financial systems. These endpoints are especially useful for practice owners and accountants managing revenue tracking, third-party billing systems needing to reconcile payments, insurance integration platforms that require payment and invoice data, patient portals showing billing history and payment receipts.**

#### **2.1. Get Financials List**

**Overview:  
This API retrieves financial transaction records within a given date range, optionally filtered by patient, practitioner, or location. It provides a detailed breakdown of invoices, receipts, discounts, refunds, and health fund rebates, allowing practices to track revenue, outstanding balances, and payment activity. This is essential for billing teams, financial reporting, and reconciling accounts.**

**End Point:  
GET /api/v1/financials**

**Use Cases:**

- **Generating monthly revenue reports filtered by practitioner.**
    
- **Reviewing financial performance per location.**
    
- **Identifying outstanding invoices for follow-up.**
    
- **Analysing the ratio of refunds or discounts to total income.**
    

**Parameters:**

| **Name** | **Type** | **Required** | **Description** |
| **patient_id** | **int** | **No** | **Filter** |
| **practitioner_id** | **int** | **No** | **Filter** |
| **location_id** | **int** | **No** | **Filter** |
| **from_date** | **date** | **Yes** | **Mandatory** |
| **to_date** | **date** | **No** |  |
| **page** | **int** | **No** |  |
| **per_page** | **int** | **No** |  |

**Response Field Mapping**

**location_id, practitioner_id, patient_id, date, trans_type, invoice_id, receipt_id, invoice, discount, refund, receipt, health_fund_rebate**

**Rules:**

-  **from_date is mandatory** 
    
-  **trans_type: 1=invoice, 2=discount, 3=refund, 4=payment** 
    
-  **Use location_id=-1 for all locations**
    
-   **Use practitioner_id=-1 for all practitioners"**
    

#### **2.2. Get Receipt Data**

**Overview:  
Retrieves detailed payment information for a specific receipt, including payment types, cheque details, banking information, and deposit status. This is particularly useful for reconciliation, auditing, and resolving payment disputes. It allows administrators to verify how payments were made and ensure that deposits match records.**

**End Point:  
GET /api/v1/receipts/{receipt_id}**

**Use Cases:**

- **Confirming payment method for a specific transaction.**
    
- **Auditing banking details to prevent reconciliation errors.**
    
- **Investigating discrepancies between payment records and bank deposits.**
    
- **Generating reports for cheque-based or EFT payments.**
    

**Parameters:**

| **Name** | **Type** | **Required** | **Description** |
| **receipt_id** | **int** | **Yes** | **Receipt unique identifier** |

**Response Field Mapping**

**receipt_id, detail_id, payment_type_id, receipt_date, cheque_name, bank_name, banked, bank_branch**

**Rules:**

- **receipt_id is required** 
    
-  **Single record response**

Financial Resources

This endpoint retrieves a list of financial based data on optional filter criteria.<br>
You can filter by parameters such as `patient_id`,`from_date`,`to_date`,
    `practitioner_id`,`location_id`,`page`,`per_page`.

- from_date is mandatory
- trans_type: 1=invoice, 2=discount, 3=refund, 4=payment
- Use location_id=-1 for all locations
- Use practitioner_id=-1 for all practitioners

GET Financials

This endpoint retrieves a single record of financial receipt based data `receipt_id`.

- receipt_id is required
- Single record response

GET Receipts

### **3\. Patient Resources**

**The Patient Resources API provides access to patient-related data stored within the Dental4Web Practice Management System. It allows external applications to retrieve details about patients, their recall schedules, and associated practitioners and clinic locations enabling rich, integrated experiences for both clinical and administrative tools.**

**This resource is designed to align with the FHIR standard, making it easier to integrate with healthcare systems and ensure interoperability. Whenever the fhir parameter is enabled, the API structures patient data in FHIR-compliant format for standardised use across medical software.**

#### **3.1. Get Patient List**

**Overview:  
This API retrieves a list of patient records from the Dental4Web system based on given filters such as patient ID, practitioner association, location, and name search. It is designed to give clinical staff and integrated systems access to essential patient demographics and contact information for day-to-day operations, patient communication, and reporting. By returning a paginated list, it also supports large patient databases efficiently.**

**End Points:  
GET /api/v1/patients-list  
FHIR: GET /api/v1/fhir/patients-list**

**Use Cases:**

- **Searching for a patient’s profile before booking an appointment.**
    
- **Syncing patient demographic data to an external CRM.**
    
- **Displaying patient lists for reception or admin dashboards.**
    

**Parameters:**

| **Name** | **Type** | **Required** | **Description** |
| **patient_id** | **int** | **No** | **Filter** |
| **patient_card** | **str** | **No** | **Filter** |
| **first_name** | **str** | **No** | **Filter** |
| **surname** | **str** | **No** | **Filter** |
| **practitioner_id** | **int** | **No** | **Filter** |
| **location_id** | **int** | **No** | **Filter** |
| **page** | **int** | **No** | **Default 1, max 500** |
| **per_page** | **int** | **No** |  |

**Response Field Mapping**

**Direct mapping: patient_id, family_head_id, patient_card, patient_status, title, first_name, middle_name, surname, preferred_name, address1, address2, suburb, state, postcode, gender, birthdate, email, phone, mobile, practitioner_id, location_id, created_date, updated_date**

**FHIR Mapping**

**Patient Resource: resourceType: "Patient", id: patient_id, identifier: {system:"http://example.org/fhir/identifier/patient-card", value:patient_card}, active: (patient_status=="Active"), name: \[{use:"official", family:surname, given:\[first_name,middle_name\], prefix:\[title\]}, {use:"usual", family:surname, given:\[preferred_name\]}\], telecom: phone/mobile entries, gender, birthDate, address: {line:\[address1,address2\], city:suburb, state, postalCode:postcode, country:"Australia"}, generalPractitioner: reference to Practitioner/{practitioner_id}**

**Rules:**

- **Requires at least one parameter** 
    
-  **Null/empty params omitted from Call • Defaults: page=1, per_page=10 (max 500)"**
    

#### **3.2. Get Single Patient**

**Overview:  
Fetches detailed information for a specific patient, including full demographic details, contact information, and identifiers. This is commonly used in patient profile pages, before a consultation, or when updating a patient’s record.**

**End Point:  
GET /api/v1/get_patient/{patient_id}  
FHIR: GET /api/v1/fhir/get_patient/{patient_id}**

**Use Cases:**

- **Displaying patient details on a clinician’s dashboard prior to an appointment.**
    
- **Retrieving a patient’s full contact information to send appointment reminders.**
    
- **Verifying identity before updating medical or billing records.**
    

**Parameter:**

| **Name** | **Type** | **Required** | **Description** |
| **patient_id** | **int** | **No** | **Filter** |

**Response Field Mapping**

**Direct mapping: patient_id, family_head_id, patient_card, patient_status, title, first_name, middle_name, surname, preferred_name, address1, address2, suburb, state, postcode, gender, birthdate, email, phone, mobile, practitioner_id, location_id, created_date, updated_date**

**FHIR Mapping**

**Patient Resource: resourceType: "Patient", id: patient_id, identifier: {system:"http://example.org/fhir/identifier/patient-card", value:patient_card}, active: (patient_status=="Active"), name: \[{use:"official", family:surname, given:\[first_name,middle_name\], prefix:\[title\]}, {use:"usual", family:surname, given:\[preferred_name\]}\], telecom: phone/mobile entries, gender, birthDate, address: {line:\[address1,address2\], city:suburb, state, postalCode:postcode, country:"Australia"}, generalPractitioner: reference to Practitioner/{practitioner_id}**

**Rules:**

- **Single record response** 
    
-  **404 if not found**
    

#### **3.3. Patient Recalls**

**Overview:  
\-**

**End Point:  
GET /api/v1/patients/{patient_id}/recalls  
  
**

**Use Cases:**

- **\-**
    

**Parameters:**

| **Name** | **Type** | **Required** | **Description** |
| **patient_id** | **int** | **No** | **Filter** |
| **from_date** | **date** | **Yes** |  |
| **to_date** | **date** | **No** |  |
| **page** | **int** | **No** | **Default 1, max 500** |
| **per_page** | **int** | **No** |  |

**Response Field Mapping**

**recall_type_id, patient_id, recall_date, reminder_date, reminder_type, reminder_no, practitioner_id, location_id, created_date, updated_date**

**Rules:**

- **Date format: YYYY-MM-DD** 
    
- **Optional date filters**

Patient Resources

This endpoint retrieves a list of patients based on optional filter criteria.<br>
You can filter by parameters such as `patient_id`, `patient_card`, `first_name`,
`surname`, `practitioner_id`, and `location_id`.

- FHIR - False
- Requires at least one parameter
- Null/empty params omitted from Call
- Defaults: page=1, per_page=10 (max 500)

GET Patients

This endpoint retrieves a list of patients based on optional filter criteria.<br>
You can filter by parameters such as `patient_id`, `patient_card`, `first_name`,
`surname`, `practitioner_id`, and `location_id`.

- FHIR - True
- Requires at least one parameter
- Null/empty params omitted from Call
- Defaults: page=1, per_page=10 (max 500)

GET Patients - FHIR

This endpoint retrieves data of patients based on `patient_id`.

- FHIR - False
- Single record response

GET Patient By ID

This endpoint retrieves data of patients based on `patient_id`.

- FHIR - True
- Single record response

GET Patient By ID - FHIR

This endpoint retrieves data of patients recall.<br>
 You can filter by parameters such as `patient_id`, `from_date`, `to_date`.

- <b>FHIR - False</b>
- Date format: YYYY-MM-DD
- Optional date filters

GET Patient Recalls

GET Patient Extended By ID

GET Patients Extended

### **4\. Treatment & Clinical Resources**

**The Treatment & Clinical Resources API gives access to core clinical records in the Dental4Web Practice Management System. It enables third-party systems to retrieve treatment histories, upcoming planned treatments, and clinical notes while maintaining patient privacy and security. These endpoints are designed for integration with external EHR systems, automated reporting and analytics, building patient-facing treatment history views, supporting compliance and audit needs.**

#### **4.1. Treatments Data List**

**Overview:  
\-**

**End Point:  
GET /api/v1/treatments**

**Use Cases:**

- **\-**
    

**Parameters:**

| **Name** | **Type** | **Required** | **Description** |
| **patient_id** | **int** | **No** | **Filter** |
| **practitioner_id** | **int** | **No** | **Filter** |
| **location_id** | **int** | **No** | **Filter** |
| **page** | **int** | **No** | **Default 1, max 500** |
| **per_page** | **int** | **No** |  |

**Response Field Mapping**

**treatment_id, patient_id, treatment_date, item_code, item_qty, tooth, surface, item_fee, fee_discount, item_paid, practitioner_id, location_id, plan_id, created_date, updated_date**

**Rules:**

- **Requires at least one parameter** 
    
- **Use location_id=-1 for all locations** 
    
- **Use practitioner_id=-1 for all practitioners"**
    

#### **4.2. Treatment Plan Data List**

**Overview:  
Provides access to treatment plan details for patients, including planned procedures, associated costs, and statuses. This is vital for clinical staff to review and update proposed treatments and for administrative teams to generate cost estimates for patients. It supports better treatment coordination and transparency for patients.**

**End Point:  
GET /api/v1/treatment-plans  
  
Use Cases:**

- **Reviewing a patient’s pending and completed treatment plans.**
    
- **Sharing cost estimates with patients.**
    
- **Generating clinical workload reports by practitioner.**
    
- **Tracking acceptance rates of proposed treatments.**
    

**Parameters:**

| **Name** | **Type** | **Required** | **Description** |
| **patient_id** | **int** | **No** | **Filter** |
| **practitioner_id** | **int** | **No** | **Filter** |
| **location_id** | **int** | **No** | **Filter** |
| **from_date** | **date** | **Yes** |  |
| **to_date** | **date** | **No** |  |
| **page** | **int** | **No** | **Default 1, max 500** |
| **per_page** | **int** | **No** |  |

**Response Field Mapping**

**treatment_plan_id, treatment_plan_item_id, patient_id, planned_date, item_code, item_qty, tooth, surface, item_fee, practitioner_id, location_id, treatment_plan_status, is_alt_plan, is_plan_active, appointment_id, treatment_id, treatment_date, created_date, updated_date**

**Rules:**

- **Requires at least one parameter** 
    
- **Use location_id=-1 for all locations** 
    
- **Use practitioner_id=-1 for all practitioners**
    

#### **4.3. Clinical Notes**

**Overview:  
Retrieves clinical notes recorded by practitioners for a patient, including visit details, observations, diagnoses, and procedural notes. This is critical for maintaining accurate patient medical records and ensuring continuity of care across multiple practitioners.**

**End Points:  
GET /api/v1/clinical-notes  
FHIR: GET /api/v1/fhir/clinical-notes**

**Use Cases:**

- **Reviewing historical clinical notes before an upcoming appointment.**
    
- **Pulling patient records into an integrated EHR system.**
    
- **Tracking specific conditions or treatment progress over time.**
    
- **Supporting legal or insurance claims requiring medical history.**
    

**Parameters:**

| **Name** | **Type** | **Required** | **Description** |
| **patient_id** | **int** | **No** | **Filter** |
| **practitioner_id** | **int** | **No** | **Filter** |
| **location_id** | **int** | **No** | **Filter** |
| **from_date** | **date** | **Yes** |  |
| **to_date** | **date** | **No** |  |
| **page** | **int** | **No** | **Default 1, max 500** |
| **per_page** | **int** | **No** |  |

**Response Field Mapping**

**note_id, treatment_id, patient_id, note_date, note_source, item_code, tooth, surface, notes, practitioner_id, location_id, created_date, updated_date**

**FHIR Mapping**

**Observation Resource: resourceType: "Observation", id: note_id, status: "final", category: \[{coding:\[{system:"http://terminology.hl7.org/CodeSystem/observation-category", code:"procedure", display:"Procedure"}\]}\], code: {coding:\[{system:"http://loinc.org", code:item_code, display:"Clinical Note"}\]}, subject: {reference:"Patient/{patient_id}"}, performer: \[{reference:"Practitioner/{practitioner_id}"}\], effectiveDateTime: note_date, valueString: notes, bodySite: {text:"tooth, surface"}**

**Rules:**

- **Requires at least one parameter** 
    
-  **Use location_id=-1 for all locations** 
    
-  **Use practitioner_id=-1 for all practitioners"**

Treatment & Clinical Resources

This endpoint retrieves a list of treatment data based on optional filter criteria.<br>
You can filter by parameters such as `patient_id`, `practitioner_id`, `location_id`,
`from_date` and `to_date`.

- Requires at least one parameter
- Use location_id=-1 for all locations
- Use practitioner_id=-1 for all practitioners

GET Treatments

This endpoint retrieves a list of treatment plan data based on optional filter criteria.<br>
You can filter by parameters such as `patient_id`, `practitioner_id`, `location_id`,
`from_date` and `to_date`.

- Requires at least one parameter
- Use location_id=-1 for all locations
- Use practitioner_id=-1 for all practitioners

GET Treatment Plans

This endpoint retrieves a list of treatment plan data based on optional filter criteria.<br>
You can filter by parameters such as `patient_id`, `practitioner_id`, `location_id`,
`from_date` and `to_date`.

- FHIR - False
- Requires at least one parameter
- Use location_id=-1 for all locations
- Use practitioner_id=-1 for all practitioners

GET Treatment Clinical Notes

GET Treatment Clinical Notes - FHIR

POST Treatment Clinical Notes

### **5\. Reference Data Resources**

**The Reference Data Resources API provides access to essential configuration and operational data in the Dental4Web Practice Management System. These resources are not patient treatment records, but rather supporting datasets that define the structure, people, and reference data used across other APIs. They are especially important for linking appointments, treatments, and financial transactions to the correct practitioner, location, or appointment book, integrating reference data like procedure codes and payment types, managing user and recall reminder records.**

#### **5.1. Practitioners**

**Overview:  
Retrieves a list of practitioners within the organisation, including their active status, personal details, role, location, and provider numbers. This API is crucial for linking appointments, treatments, and billing information to the correct healthcare provider. It ensures that all related patient records, invoices, and clinical data correctly reference the appropriate practitioner.**

**End Point:  
GET /api/v1/practitioners  
FHIR: GET /api/v1/fhir/practitioners**

**Use Cases:**

- **Populating a dropdown list of practitioners in appointment booking forms.**
    
- **Filtering reports by practitioner to assess productivity or revenue.**
    
- **Synchronising practitioner data with an external HR or scheduling system.**
    
- **Ensuring correct provider details are shown on patient invoices and receipts.**
    

**Parameters:**

| **Name** | **Type** | **Required** | **Description** |
| **location_id** | **int** | **No** | **Filter** |
| **page** | **int** | **No** | **Default 1, max 500** |
| **per_page** | **int** | **No** |  |

**Response Field Mapping**

**practitioner_id, is_active, practitioner_code, full_name, first_name, surname, title, role, location_id, provider_number, qualifications**

**FHIR Mapping**

**Referenced in FHIR (as Practitioner/{practitioner_id})**

**Rules:**

- **location_id is optional** 
    
-  **Returns all practitioners if no location specified"**
    

#### **5.2. Locations**

**Overview:  
Returns a list of locations within the organisation, including their active status. Locations are essential for multi-site practices where patient records, appointments, and billing must be tied to the correct branch or clinic. This ensures accurate operational reporting and avoids misallocations.**

**End Point:  
GET /api/v1/locations  
FHIR: GET /api/v1/fhir/locations**

**Use Cases:**

- **Assigning appointments or invoices to the correct branch.**
    
- **Generating location-specific performance and revenue reports.**
    
- **Filtering available appointment slots by location in booking systems.**
    
- **Integrating with facility management or resource scheduling tools.**
    

**Parameters:**

| **Name** | **Type** | **Required** | **Description** |
| **page** | **int** | **No** | **Default 1, max 500** |
| **per_page** | **int** | **No** |  |

**Response Field Mapping**

**location_id, location_name, is_active**

**FHIR Mapping**

**Referenced in FHIR (as Location/{location_id})**

**Rules:**

-  **No parameters required** 
    
-  **Returns all locations"**
    

#### **5.3. Appointment Books**

**Overview:  
Provides a list of appointment books configured within the system, including their associated location, operating hours, and active status. Appointment books are essential for managing multiple schedules within a single location, such as separate books for different practitioners, rooms, or services.**

**HTTP Request:  
GET /api/v1/appointment-books**

**Use Cases:**

- **Assigning patient bookings to the correct appointment book based on service type.**
    
- **Managing practitioner or room availability in a clinic.**
    
- **Creating a customised calendar view for a specific service or department.**
    
- **Separating clinical and administrative appointment schedules.**
    

**Parameters:**

| **Name** | **Type** | **Required** | **Description** |
| **page** | **int** | **No** | **Default 1, max 500** |
| **per_page** | **int** | **No** |  |

**Response Field Mapping**

**appt_book_id, appt_book_name, location_id, start_time, end_time, is_active**

**Rules:**

- **No parameters required**
    

#### **5.4. Procedure Codes (Items)**

**Overview:  
Retrieves a list of procedure codes and descriptions, including ADA codes and categories. This data ensures consistent billing, reporting, and treatment descriptions across the organisation. It also supports compliance with dental coding standards in Australia.**

**End Point:  
GET /api/v1/items**

**Use Cases:**

- **Populating treatment plan forms with standard procedure codes.**
    
- **Mapping treatments to billing and insurance claim submissions.**
    
- **Ensuring uniform terminology in patient records.**
    
- **Enabling reporting by procedure category for business analysis.**
    

**Parameters:**

| **Name** | **Type** | **Required** | **Description** |
| **page** | **int** | **No** | **Default 1, max 500** |
| **per_page** | **int** | **No** |  |

**Response Field Mapping**

**item_code, ADA_Code, description, category, sub_category, non_reporting, non_treatment**

**Rules:**

- **No parameters required** 
    
- **Returns all procedure/item codes**
    

#### **5.5. Payment Types**

**Overview:  
Provides a list of available payment methods in the system, such as cash, credit card, EFTPOS, or health fund rebates. This ensures all payments are recorded consistently and can be accurately reported in financial statements.**

**End Points:  
GET /api/v1/payment-types**

**Use Cases:**

- **Allowing front desk staff to select the correct payment method during transaction entry.**
    
- **Filtering revenue reports by payment type.**
    
- **Integrating payment methods with external POS or accounting systems.**
    
- **Analysing payment method trends for operational planning.**
    

**Parameters:**

| **Name** | **Type** | **Required** | **Description** |
| **page** | **int** | **No** | **Default 1, max 500** |
| **per_page** | **int** | **No** |  |

**Response Field Mapping**

**payment_type_id, payment_type, reporting_name, show_in_reports, is_deleted**

**Rules:**

- **No parameters required** 
    

#### **5.6. Users**

**Overview:  
Retrieves details of system users, including their role, active status, and associated location. This API helps manage user permissions, track activity logs, and ensure accountability for transactions and patient data updates.**

**End Point:  
GET /api/v1/users**

**Use Cases:**

- **Controlling access to sensitive data by role and location.**
    
- **Tracking who created or updated patient records.**
    
- **Linking logged-in user details to audit logs.**
    
- **Synchronising user data with an HR or identity management system.**
    

**Parameters:**

| **Name** | **Type** | **Required** | **Description** |
| **page** | **int** | **No** | **Default 1, max 500** |
| **per_page** | **int** | **No** |  |

**Response Field Mapping**

**user_id, user_code, firstname, surname, location_id, is_active, user_type**

**Rules:**

-  **No parameters required** 
    
-  **user_type: 'Provider' or 'Staff'"**
    

#### **5.7. Recalls**

**Overview:  
All recalls (multiple patients, practitioners, locations, dates).**

**End Points:  
GET /api/v1/recalls**

**Parameters:**

| **Name** | **Type** | **Required** | **Description** |
| **patient_id** | **int** | **No** | **Filter** |
| **practitioner_id** | **int** | **No** | **Filter** |
| **location_id** | **int** | **No** | **Filter** |
| **from_date** | **date** | **Yes** |  |
| **to_date** | **date** | **No** |  |
| **page** | **int** | **No** | **Default 1, max 500** |
| **per_page** | **int** | **No** |  |

**Response Field Mapping**

**recall_type_id, patient_id, recall_date, reminder_date, reminder_type, reminder_no, practitioner_id, location_id, created_date, updated_date**

**Rules:**

- **Requires at least one parameter**

Reference Data Resources

This endpoint retrieves a list of practitioners based on optional filter criteria.<br>
You can filter by parameter `location_id`.

- FHIR - False
- location_id is optional
- Returns all practitioners if no location specified

GET Practitioners

This endpoint retrieves a list of appointment books.<br>

- FHIR - False
- No parameters required

GET Locations

GET Appointment Books

GET Procedure Codes

GET Payment Types

GET Users

GET Recalls

GET Practitioners - FHIR

GET Locations  - FHIR

MediaWeb PACS Resources

GET Image Search

GET Single Image

GET Patient Images (Bulk)

D4WEB API - Swagger

from_date

Production

Sandbox

<p class="slate-p " ><p class="slate-p " ><span style="background-color:transparent;color:#434343">The Dental4Web API provides secure API access to dental practice management data. This API enables third-party applications to integrate with practice data while maintaining security and privacy controls. This API currently provides read-only access. Write access is planned for future releases.</span></p><p class="slate-p " ><span style="background-color:transparent;color:#434343">The API provides access to patient records, appointment schedules, financial transactions, treatment plans, and clinical notes. Separate endpoints are available for accessing data in the HL7 FHIR (R4) format.</span></p><p class="slate-p " ><span style="background-color:transparent;color:#000000"><strong class="slate-bold">Prerequisites:</strong></span><span style="background-color:transparent;color:#000000"> </span><span style="background-color:transparent;color:#434343">Understanding of REST APIs, HTTP methods, JSON format, and healthcare data standards. You&apos;ll need a valid API key and tenant organisation ID from Centaur Software to get started.</span></p><p class="slate-p " >
</p></p><p class="slate-p " ></p>

<p class="slate-p " ><p class="slate-p " ></p><div class="steps-widget" style="width:100%;
  	min-width:100%;"><div class="steps-wrapper"><div class="steps-content"><h6 class="slate-h6 " >1</h6><h3 class="slate-h3 " >Obtain Credentials</h3><p class="slate-p " ></p><div class="slate-div"><p class="slate-p " ><span style="background-color:transparent;color:#434343">To gain API access, an integrator must contact </span><a href="https://dental4web.com.au/book-a-demo/" target="_blank"><span style="background-color:transparent;color:#1155CB"><u class="slate-underline">Centaur Software</u></span></a><span style="background-color:transparent;color:#434343"> to set up an integration account. This request should state the intended use case, the scope of required data, and the organisation(s) for which access is being sought.</span></p><p class="slate-p " ><span style="background-color:transparent;color:#434343">Once the account is created, the integrator will be provided with an API key and given access to Dental4Web tenants. All API requests require a unique organisation ID to identify the specific tenant.</span></p></div><p class="slate-p " ></p></div></div><div class="steps-wrapper"><div class="steps-content"><h6 class="slate-h6 " >2</h6><h3 class="slate-h3 " >Add Authentication</h3><p class="slate-p " ></p><div class="slate-div"><p class="slate-p " ><span style="background-color:transparent;color:#434343">All HTTP requests must include the following headers:</span></p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><span style="color:#000000">x-api-key</span></div></li></ul><p class="slate-p " ><span style="background-color:transparent;color:#434343"><em class="slate-italic">This is the integrator’s API key.</em></span></p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><span style="background-color:transparent;color:#000000">org-id</span></div></li></ul><p class="slate-p " ><span style="background-color:transparent;color:#434343">The organisation ID identifies a specific organisation within Dental4Web. Note that an integrator&apos;s API key can be used to access multiple organisations, so both the organisation ID and the API key are required for all requests.</span></p><p class="slate-p " ><span style="background-color:transparent;color:#434343">The API token grants access only to the data of the mapped org-id. Any attempt to retrieve information for a tenant other than the current one will be rejected by the API.</span></p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><span style="background-color:transparent;color:#000000">Accept: application/json</span></div></li></ul><p class="slate-p " ><span style="background-color:transparent;color:#434343"><em class="slate-italic">All requests must specify the expected response format.</em></span></p><p class="slate-p " ></p></div></div></div><div class="steps-wrapper"><div class="steps-content"><h6 class="slate-h6 " >3</h6><h3 class="slate-h3 " >Try it Out</h3><p class="slate-p " ></p><div class="slate-div"><p class="slate-p " ><span style="background-color:transparent;color:#434343">Once you have all the required details, you can test your connection using the curl example below.</span></p><div class="code-block-wrapper"  style="width:100%;min-width:100%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden">curl -X GET "https://api.dental4web.centaursoftware.com/api/v1/practitioners" \
  -H "org-id: TENANT_ORG_ID" \
  -H "x-api-key: INTEGRATOR_API_KEY" \
  -H "Accept: application/json" </textarea><code class="language-plainText keep-markup drop-tokens"></code></pre></div></div></div></div></div><p class="slate-p " ></p><p class="slate-p " ></p></p><p class="slate-p " ></p>

<h4 class="slate-h4 " ></h4><h4 class="slate-h4 " ><span style="color:#000000"><strong class="slate-bold">Choose your primary integration scenario to jump to the most relevant sections:</strong></span></h4><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><span style="color:#000000"><strong class="slate-bold">Patient Data Integration</strong></span><span style="color:#000000">: </span><span style="color:#434343">Synchronise patient demographics, contact info, and medical history into your system.</span></div></li><li class="slate-li " ><div style="position:relative"><span style="color:#000000"><strong class="slate-bold">Appointment Synchronisation</strong></span><span style="color:#000000">:</span><span style="color:#434343"> Pull appointment schedules, status updates, and practitioner assignments for calendar apps.</span></div></li><li class="slate-li " ><div style="position:relative"><span style="color:#000000"><strong class="slate-bold">Billing &amp; Payment Systems</strong></span><span style="color:#000000">:</span><span style="color:#980100"> </span><span style="color:#434343">Extract transaction data, payment records, and financial reports for accounting software.</span></div></li><li class="slate-li " ><div style="position:relative"><span style="color:#000000"><strong class="slate-bold">EHR/EMR Connectivity</strong></span><span style="color:#000000">:</span><span style="color:#434343"> FHIR R4 endpoints for healthcare interoperability and clinical data exchange.</span></div></li><li class="slate-li " ><div style="position:relative"><span style="color:#000000"><strong class="slate-bold">Development &amp; Testing</strong></span><span style="color:#000000">:</span><span style="color:#434343"> Quick authentication setup and endpoint testing for proof-of-concept builds.</span></div></li></ul><p class="slate-p " ></p><p class="slate-p " ></p>

Choose your primary integration scenario to jump to the most relevant sections:

<p class="slate-p " ></p><h3 class="slate-h3 " ><span style="color:#000000">Required Headers</span></h3><p class="slate-p " ></p><div class="published-table"><div class="table-container" style="padding-left: 0px;"><table class="slate-table" style="min-width:100%;"><div class="published-table-header" style="width:100%;min-width:100%;"><div style="width:0px;">Header</div><div style="width:0px;">Type</div><div style="width:353px;">Required</div><div style="width:0px;">Description</div></div><colgroup ><col style="width:initial"><col style="width:initial"><col style="width:353px"><col style="width:initial"></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><span style="color:#434343">org-id</span></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><span style="color:#434343">string</span></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><span style="color:#434343">yes</span></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><span style="color:#434343">Organisation ID for routing</span></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><span style="color:#434343">x-api-key</span></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><span style="color:#434343">string</span></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><span style="color:#434343">yes</span></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><span style="color:#434343">API Key for authentication</span></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><span style="color:#434343">Accept</span></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><span style="color:#434343">string</span></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><span style="color:#434343">yes</span></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><span style="color:#434343">application/json</span></p></td></div></tr></tbody></table></div></div><p class="slate-p " ></p><h3 class="slate-h3 " ><span style="color:#000000">Sample Response:</span></h3><p class="slate-p " ></p><h4 class="slate-h4 " ><span style="color:#000000"><strong class="slate-bold">Response Field Mapping</strong></span><span style="background-color:transparent;color:rgb(0, 0, 0)"><strong class="slate-bold">
</strong></span></h4><div class="code-block-wrapper"  style="width:100%;min-width:100%" ><div class="code-block-header">JSON</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden"> </textarea><code class="language-json keep-markup drop-tokens"><div class="slate-code_line"><div class="slate-code_line">{
    &quot;data&quot;: [],
    &quot;pagination&quot;: {
        &quot;page&quot;: 1,
        &quot;per_page&quot;: 10,
        &quot;total_rows&quot;: 0,
        &quot;total_pages&quot;: 0
    },
}</div></div></code></pre></div><h3 class="slate-h3 " ><span style="background-color:transparent;color:rgb(0, 0, 0)">
</span></h3><h4 class="slate-h4 " ><span style="background-color:transparent;color:rgb(0, 0, 0)"><strong class="slate-bold">FHIR Mapping</strong></span></h4><p class="slate-p " ></p><div class="code-block-wrapper"  style="width:100%;min-width:100%" ><div class="code-block-header">JSON</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden"> </textarea><code class="language-json keep-markup drop-tokens"><div class="slate-code_line"><div class="slate-code_line"> {
    &quot;data&quot;: [],
    &quot;pagination&quot;: {
        &quot;page&quot;: 1,
        &quot;per_page&quot;: 10,
        &quot;total_rows&quot;: 0,
        &quot;total_pages&quot;: 0
    }
}</div></div></code></pre></div><p class="slate-p " ></p><h4 class="slate-h4 " ><span style="background-color:transparent;color:rgb(0, 0, 0)"><strong class="slate-bold">Error Codes</strong></span></h4><p class="slate-p " ></p><div class="published-table"><div class="table-container" style="padding-left: 0px;"><table class="slate-table" style="min-width:100%;"><div class="published-table-header" style="width:100%;min-width:100%;"><div style="width:100px;">Codes</div><div style="width:100px;">Reason</div></div><colgroup ><col style="width:initial"><col style="width:initial"></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><span style="color:#666666">400</span></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><span style="color:#666666">Missing Required Parameters</span></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><span style="color:#666666">401</span></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><span style="color:#666666">Invalid/Missing Arguments</span></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><span style="color:#666666">404</span></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><span style="color:#666666">Appointment Not Found</span></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><span style="color:#666666">422</span></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><span style="color:#666666">Parameter Validation Error</span></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><span style="color:#666666">500</span></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><span style="color:#666666">Internal Server/Database Error</span></p></td></div></tr></tbody></table></div></div><p class="slate-p " ></p>

Header

Type

Required

Description

Codes

Reason

<p class="slate-p slate-indent-0" style="0px"></p><p class="slate-p slate-indent-0" style="0px"><span style="color:#434343">The Appointment Resources API provides appointment-related information stored within the Dental4Web Practice Management System. It enables third-party applications to retrieve appointment schedules, statuses, and related details for patients, practitioners, and clinic locations. Designed for interoperability, the API supports FHIR-compliant Appointment resources when the FHIR parameter is enabled, ensuring compatibility with healthcare industry standards.</span></p><p class="slate-p " ></p>

The Appointment Resources API provides appointment-related information stored within the Dental4Web Practice Management System. It enables third-party applications to retrieve appointment schedules, statuses, and related details for patients, practitioners, and clinic locations. Designed for interoperability, the API supports FHIR-compliant Appointment resources when the FHIR parameter is enabled, ensuring compatibility with healthcare industry standards.

<p class="slate-p " >
<span style="background-color:rgb(255, 255, 255);color:rgb(67, 67, 67)">The Financial Resources API provides secure access to billing and payment data stored in the Dental4Web Practice Management System. It enables third-party applications to retrieve transaction histories, invoice details, receipt records, and other financial information to support accounting, reporting, and integration with external financial systems. These endpoints are especially useful for practice owners and accountants managing revenue tracking, third-party billing systems needing to reconcile payments, insurance integration platforms that require payment and invoice data, and patient portals showing billing history and payment receipts.</span></p>

The Financial Resources API provides secure access to billing and payment data stored in the Dental4Web Practice Management System. It enables third-party applications to retrieve transaction histories, invoice details, receipt records, and other financial information to support accounting, reporting, and integration with external financial systems. These endpoints are especially useful for practice owners and accountants managing revenue tracking, third-party billing systems needing to reconcile payments, insurance integration platforms that require payment and invoice data, and patient portals showing billing history and payment receipts.

<p class="slate-p " ><span style="color:#434343">The Patient Resources API provides access to patient-related data stored within the Dental4Web Practice Management System. It allows external applications to retrieve details about patients, their recall schedules, and associated practitioners and clinic locations, enabling rich, integrated experiences for both clinical and administrative tools.</span></p><p class="slate-p " ><span style="color:#434343">This resource is designed to align with the FHIR standard, making it easier to integrate with healthcare systems and ensure interoperability. Whenever the FHIR parameter is enabled, the API structures patient data in FHIR-compliant format for standardised use across medical software.</span></p><p class="slate-p " ></p>

The Patient Resources API provides access to patient-related data stored within the Dental4Web Practice Management System. It allows external applications to retrieve details about patients, their recall schedules, and associated practitioners and clinic locations, enabling rich, integrated experiences for both clinical and administrative tools.

This resource is designed to align with the FHIR standard, making it easier to integrate with healthcare systems and ensure interoperability. Whenever the FHIR parameter is enabled, the API structures patient data in FHIR-compliant format for standardised use across medical software.

<p class="slate-p " ><span style="background-color:transparent;color:#434343">The Treatment &amp; Clinical Resources API gives access to core clinical records in the Dental4Web Practice Management System. It enables third-party systems to retrieve treatment histories, upcoming planned treatments, and clinical notes while maintaining patient privacy and security. These endpoints are designed for integration with external EHR systems, automated reporting and analytics, building patient-facing treatment history views, and supporting compliance and audit needs.</span></p><p class="slate-p " ></p><p class="slate-p " ></p>

The Treatment & Clinical Resources API gives access to core clinical records in the Dental4Web Practice Management System. It enables third-party systems to retrieve treatment histories, upcoming planned treatments, and clinical notes while maintaining patient privacy and security. These endpoints are designed for integration with external EHR systems, automated reporting and analytics, building patient-facing treatment history views, and supporting compliance and audit needs.

<p class="slate-p " ><span style="background-color:transparent;color:#434343">The Reference Data Resources API provides access to essential configuration and operational data in the Dental4Web Practice Management System. These resources are not patient treatment records, but rather supporting datasets that define the structure, people, and reference data used across other APIs. They are especially important for linking appointments, treatments, and financial transactions to the correct practitioner, location, or appointment book, integrating reference data like procedure codes and payment types, and managing user and recall reminder records.</span></p><p class="slate-p " ></p>

The Reference Data Resources API provides access to essential configuration and operational data in the Dental4Web Practice Management System. These resources are not patient treatment records, but rather supporting datasets that define the structure, people, and reference data used across other APIs. They are especially important for linking appointments, treatments, and financial transactions to the correct practitioner, location, or appointment book, integrating reference data like procedure codes and payment types, and managing user and recall reminder records.

<p class="slate-p " ><span style="color:#434343">MediaWeb PACS endpoints provide access to Dental4Web&apos;s digital imaging platform. These endpoints facilitate search, retrieval, and bulk extraction of digital images. The platform&apos;s native storage format is DICOM, with optional JPEG conversion available at quality level 98. If the quality threshold cannot be maintained during conversion, the original DICOM file will be delivered instead. We strongly recommend downloading the original DICOM format wherever possible for optimum diagnostic quality. All images are delivered via pre-signed URLs with time-limited access.</span></p>

MediaWeb PACS endpoints provide access to Dental4Web's digital imaging platform. These endpoints facilitate search, retrieval, and bulk extraction of digital images. The platform's native storage format is DICOM, with optional JPEG conversion available at quality level 98. If the quality threshold cannot be maintained during conversion, the original DICOM file will be delivered instead. We strongly recommend downloading the original DICOM format wherever possible for optimum diagnostic quality. All images are delivered via pre-signed URLs with time-limited access.

Sections