The API Report CardAPI Index
SalonRunner

SalonRunner API

Salon POS booking · salonrunner.com

No API in any form for SalonRunner or its Rosy sibling: no developer portal, REST or GraphQL docs, SDKs, webhooks, published rate limits, or Zapier app. Partner connections like Birdeye run as managed-service data transfers, and programmatic access starts with phoning support.

Last verified: July 2026Fitness & Wellness
API GRADE
D
VERIFIED JUL 2026

SCORECARD

ExistencePOORNo API at all: no portal, endpoints, SDKs, webhooks, or even a Zapier app in the public directory.
AccessPOORThe only path to moving data is contacting support; partners like Birdeye run managed transfers instead.
CoverageFAILWith no API at all, no appointment, client, or sales data is programmatically reachable for customers.
AuthPOORNothing to authenticate against; no keys, tokens, or OAuth exist for outside developers.
Docs & DXFAILThe only published documentation is end user support content; there are no developer docs, SDKs, or webhooks.
StabilityMIXED
MORE FROM THE REPORT CARD
Supergood: SalonRunner has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

SalonRunner scores D on the API Report Card. No API in any form for SalonRunner or its Rosy sibling: no developer portal, REST or GraphQL docs, SDKs, webhooks, published rate limits, or Zapier app. Partner connections like Birdeye run as managed-service data transfers, and programmatic access starts with phoning support.

Tried to integrate with SalonRunner?
SOURCES
No public API, no developer portal, no published REST/GraphQL/OpenAPI documentation, and no public 'getting started' guide for SalonRunner or Rosy Salon Software salonrunner.com
No SalonRunner or Rosy Salon app exists in the public Zapier directory, third-party integration is not available through the most common no-code platform zapier.com
No public SDKs or client libraries on npm, PyPI, RubyGems, or Maven, and no public GitHub organization (github.com/salonrunner, github.com/rosy-salon) with sample code npmjs.com
No documented webhooks, no published rate limits, no public sandbox, and no public partner/integration portal support.salonrunner.com
Third-party integrations (e.g., Birdeye) are run as 'managed services' data transfers handled by the partner's team rather than self-serve API integrations birdeye.com
RosyPay is delivered as an embedded payments relationship through Fullsteam, not as an open payment API customers can extend or replace rosysalonsoftware.com
No documented self-serve full-database export, data retrieval requires contacting support (877) 346-7679, with no published SLA or programmatic path support.salonrunner.com
Customer support is reported as 'close to nonexistent' with problems often deflected as user error rather than software issues, and resolved via workarounds rather than fixes capterra.com
Once customers depend on Rosy/SalonRunner to keep their records, customer service becomes hard to reach even within business hours; users are pushed to leave messages with ~24-hour response times capterra.com
Reviewers describe the UI and reporting as feeling dated relative to mobile-first competitors (GlossGenius, Boulevard, Fresha) g2.com
Pricing escalates with add-ons (Website Builder $19/mo, BoothRunner $19–$27/mo, RosyPay processing) that are not always obvious at signup rosysalonsoftware.com
Some marketing/SMS volume sits behind the Premium tier, requiring upgrades for higher-volume salons rosysalonsoftware.com
Reports require export and external rework for non-templated analyses; no native ad-hoc query builder softwareadvice.com
Cancelled customers face the same data-portability ambiguity common to legacy SMB salon SaaS, no documented self-serve full-database export path support.salonrunner.com