Club Studio publishing guide
Updated 2026-10-01. Reference language: English.
Club Studio is included with Club Lite and Club. Open Club Studio to create a workspace publication. It is independent of lesson Booking. Create up to five active publishable keys, with separate domain controls for your website and staging environment. The complete key is shown once; revoke and replace a lost or exposed publication key.
Interfaces
Iframe routes: /embed/studio/recent, /embed/studio/archive and
/embed/studio/adjudicators. Copy the configured iframe from Studio; retain its
built-in Powered by attribution. Never interpolate arbitrary HTML or CSS.
JSON routes: /api/club-studio/v1/results, /api/club-studio/v1/archive,
/api/club-studio/v1/roster, /api/club-studio/v1/couples and
/api/club-studio/v1/adjudicators. Use only scopes selected on your publication.
curl --fail-with-body https://YOUR_SITE_DOMAIN/api/club-studio/v1/results \
-H 'X-DanceStats-Key: YOUR_PUBLICATION_KEY' \
-H 'If-None-Match: "previous-etag"'
Keys can be sent as X-DanceStats-Key, Bearer credentials or ?key=. Prefer a
header for server integrations to avoid routine URL logs. A publishable key is
necessarily visible in a browser widget: restrict its publication and allowed
domains, rather than treating it as a confidential general API token.
Browser use and refresh
Configured origin/referrer host checks apply to browser requests. Successful JSON responses support CORS for permitted origins and expose ETag, cache policy and polling guidance. Error responses (402, 403, 404, 429 and handled server errors) carry the same CORS headers, so a browser can read why a request was refused, and a 429 exposes Retry-After. Match your domain allowlist to your actual deployment. Server clients cannot prove ownership merely by sending an Origin header.
Honor X-DanceStats-Poll-Interval: 120, Cache-Control and ETag. Poll at most
once per two minutes in a shared backend cache; do not poll separately for
every visitor. A 304 has no JSON body and still consumes request quota. Follow
429 Retry-After. Route defaults are 60/minute; the application's aggregate
API/Studio attempt ceiling also applies. A subscription does not remove quotas.
Boundaries and errors
This is a club presentation overlay, not a way to rewrite federation identity,
scraped affiliation or Booking data. Some result attribution is inferred and
bounded; curated roster membership is not an official federation assertion.
Private profile restrictions remain in force. Keys resolve only their own
publication; personal Showcase keys and general ds_live_ tokens are separate.
The response uses its own ok envelope. Handle status before parsing items.
An inactive subscription may return 402; an invalid publication/key or domain
may return 404/403. Do not retry these indefinitely. A finite subscription has
the publication grace period described in Studio; payment and access are
rechecked server-side.
For a personal verified dancer/couple widget, use Personal Showcase documentation. For public factual lookup, use the general API guide. Follow attribution and usage; commercial bulk access and new integration plans remain inquiry-only.