🚧 Beta version - The site is under active development. I am aware of many bugs and fix them daily. Any feedback is welcome - data, functionality, UI, security, or anything else. · feedback welcome Contact
← Showcase Studio API v1

Showcase API documentation

Each key represents either the verified dancer or one observed couple they belong to. Dancer and couple selections remain independent and private profile data is never exposed.

JSON API endpoint

GET /api/showcase-studio/v1/results
X-DanceStats-Key: dsshow_live_…
If-None-Match: "previous-etag"

Authentication

Use ?key= for a simple iframe or browser GET. Server-side clients should send X-DanceStats-Key or Authorization: Bearer so the key stays out of ordinary URL logs.

Domains and CORS

Every browser request is checked against the key's exact or wildcard domain list. Allow all only when the widget is intentionally portable.

Efficient polling

Respect X-DanceStats-Poll-Interval, retain ETag and send If-None-Match. Unchanged data returns 304 without a response body.

Response shape

{
  "ok": true,
  "version": "1",
  "target": {
    "type": "dancer",
    "id": 42, "name": "…", "profile_url": "/dancer/…"
  },
  "items": [{
    "federation": "csts", "competition_id": 123,
    "event_title": "…", "date": "2026-05-16",
    "ranking": 2, "couple_count": 31, "note": "…", "url": "/competition/…"
  }],
  "meta": {"poll_interval_seconds": 120, "powered_by": "DanceStats"}
}

Who is this Showcase about?

// A couple key returns the same result item shape with:
"target": {
  "type": "couple",
  "name": "… & …",
  "members": [{"id": 42, "name": "…"}, {"id": 84, "name": "…"}],
  "profile_url": "/couple/…"
}
0.0