Software integrations

Keep the tool that owns the job. Connect the dance work around it.

An integration should remove duplicate work while keeping availability, checkout, refunds, source data, and support responsibility explicit.

Ownership map

Know where to edit, pay, support, and return.

The source system keeps its authority. Abrazo carries only the approved context needed by the next product.

Availability

The teacher’s selected scheduling path owns open times and booking confirmation.

Checkout and refunds

The named seller and payment provider own the transaction, receipt, refund clock, and dispute path.

Event record

DanceLedger keeps the shared festival occurrence while official and ticketing sources remain visible.

Existing website

Supported Integration Kit surfaces publish approved information without taking over the organizer’s whole site.

Dancer access

The owning product grants the membership, purchase, invitation, or media permission that lets a dancer in.

Integration Kit

Place supported artist, studio, and event information on an existing site while checkout and sign-in remain on the appropriate first-party page.

We will name the current connection, its owner, and any remaining setup or release gate before suggesting a path.