The API Report CardAPI Index
Moxie

Moxie API

Medspa Management (EMR + CRM + Compliance + Business Coaching) · joinmoxie.com

Moxie ships a documented REST API and webhooks for its medspa EMR, exchanging JSON over HTTPS. Access is per workspace: an owner enables Custom Integration and mints an X-API-KEY; there is no OAuth or developer portal. A cap of 100 requests per 5 minutes slows any real sync.

Last verified: July 2026Healthcare
API GRADE
D+
VERIFIED JUL 2026

SCORECARD

ExistencePOORA REST API and webhooks exist only as help center articles; no spec, no endpoint catalog, and base URLs differ per workspace pod.
AccessPOOREnabled per workspace by an admin or owner; no developer portal, no app review program, and no third party signup path.
CoveragePOORWrite endpoints like /clients/create plus event webhooks, but no documented path to clinical charts, GFE records, or bulk export.
AuthPOORA single X-API-KEY header minted by the workspace owner; no OAuth, no scopes, no per-user credentials.
Docs & DXPOORDocs are a handful of help center articles; no SDKs, no OpenAPI spec, and no public developer portal.
StabilityMIXEDThe 100 requests per 5 minutes cap is at least documented; versioning and deprecation policy are not.
Supergood: Moxie has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Moxie scores D+ on the API Report Card. Moxie ships a documented REST API and webhooks for its medspa EMR, exchanging JSON over HTTPS. Access is per workspace: an owner enables Custom Integration and mints an X-API-KEY; there is no OAuth or developer portal. A cap of 100 requests per 5 minutes slows any real sync.

Tried to integrate with Moxie?
SOURCES
Hard rate limit of 100 requests per 5 minutes per workspace, any meaningful sync or backfill (clients, appointments, charges) will 429 quickly help.withmoxie.com
API key is per-workspace and only an admin/owner can mint one, no OAuth, no scopes, no per-user credentials, no app review program help.withmoxie.com
No public developer portal, no SDKs, no published OpenAPI/Swagger spec, no enumerated object/endpoint catalog outside the help center articles help.withmoxie.com
Base endpoint URL differs per workspace (pod-based hostnames like `pod00.withmoxie.dev`), making generic third-party integrations awkward help.withmoxie.com
No documented bulk export, pagination spec, or programmatic access to clinical chart data / GFE records, limits what owners can pull out of the EMR help.withmoxie.com
Public industry chatter has questioned Moxie's financial health, forcing the company to publish a 'Setting the Record Straight' post denying claims it was running out of money and shopping itself joinmoxie.com
Reviewers in growing practices report outgrowing Moxie's feature depth, citing thinner automation and reporting than PatientNow, Nextech, or Symplast patientnow.com
Comparisons highlight Moxie as 'simple' but lacking the deeper EHR functionality multi-location aesthetic practices need at scale portraitcare.com
Pabau marketing comparison cites Moxie limitations around global usability, deeper clinical workflows, and pricing transparency vs. competing aesthetic platforms pabau.com
Portrait/Care comparison notes Moxie's bundled medical director + coaching model can become a constraint once owners want to bring those functions in-house portraitcare.com
AestheticsPro comparison flags Moxie pricing/feature lock-in concerns for established practices that don't need launch coaching portraitcare.com
Boulevard comparison notes Moxie is purpose-built for solo/launch practices and weaker on the high-volume booking + retail POS flows that multi-room medspas need portraitcare.com