Aesthetic Record API

Last reviewed: August 2026

Overview

Integuru's Aesthetic Record integration provides production-ready HTTP API access to Aesthetic Record, the practice management platform used by med-spas and aesthetic clinics, covering 15 actions including create_appointment and get_patient_details. Integuru reaches Aesthetic Record via direct HTTP requests rather than browser automation, so calls complete in under 3 seconds with a 99.9%+ success rate.

No public API. Aesthetic Record does not expose an official developer API. Teams that need to move data in or out have historically relied on manual CSV exports or fragile browser scripts that break whenever the UI updates.

The integration exposes every major clinic object: patients, providers, clinics, services, appointments, invoices, and clinical notes. The get_patient_details action returns structured data including age, emails, phones, address, loyalty_programs, and payments_on_file, giving downstream systems a complete patient record in a single call.

Med-spa engineering teams typically use this integration to synchronize patient records across internal CRM or EHR systems, automate appointment scheduling from external booking flows, and pull invoice data into reporting pipelines without manual intervention. See the full integrations catalogue for other platforms Integuru supports in healthcare and adjacent verticals.

---

Use Cases

Integuru's Aesthetic Record integration covers the full patient lifecycle, from initial client creation through appointment management and invoice export. Teams building patient portals, CRM sync pipelines, or automated reminder systems can query or write any of the 15 available actions programmatically.

• Patient record sync: Use list_patients with term or letter_key filtering to page through your patient roster, then call get_patient_details to pull structured demographic, insurance, and payment data for each record.
• Appointment automation: Create, retrieve, and edit appointments via create_appointment, get_appointment, and edit_appointment. Required fields include date, time, clinic_id, provider_id, patient_id, patient_name, and appointment_service.
• Invoice reporting: Pull paginated invoice lists with list_invoices (15 per page, filtered by date range, provider, clinic, and status), or use export_invoices with report_type: 'items' for a full line-item breakdown.
• Clinical notes management: Create, update, and delete patient notes via create_patient_note, edit_customer_note, and delete_customer_note. Notes support tags and sticky/pinned status.
• Provider and service lookup: list_providers and list_clinics return the IDs you need before calling actions that require provider_id or clinic_id.

---

Setup Notes

Integuru's Aesthetic Record integration authenticates against https://app.aestheticrecord.com/login. Integuru handles the full session flow automatically, including any 2FA steps your account requires, so you pass credentials once during setup and the integration manages token refresh from that point forward.

Several actions use IDs that must be resolved before use. Call list_clinics to get valid clinic_id values, list_providers to get valid provider_id values, and list_services (which requires both IDs) to resolve service IDs before calling create_appointment or edit_appointment.

Two actions use page-based pagination:

• list_invoices: Pass page_number (starts at 1); Aesthetic Record returns a fixed page size of 15 invoices per page.
• list_patients: Pass page and pagesize to scroll through the full roster, or use term (free-text by name, email, or phone) or letter_key (alphabetic filter) to narrow results before paging.

The term and letter_key parameters on list_patients are mutually exclusive. Use term for free-text search by name, email, or phone; use letter_key for alphabetic roster browsing.