API usage and attribution
Operating policy version 2026-10-01. Reference language: English.
This guide governs supported API integration and supplements the site's general terms and privacy policy. It does not replace an existing agreement, grant rights owned by another publisher, or authorize private data access. Historical snapshots remain evidence, not a promise of current facts.
Permitted interactive use
Bounded interactive lookup, factual display and AI-assisted answers through documented public APIs are permitted with attribution, privacy restrictions and the declared quotas. Commercial factual display is permitted on the same basis; an application that needs persistent bulk copies, resale, redistribution, large-scale archiving or model-training access must request a separate agreement. A reachable endpoint or a source-code licence does not grant a licence to all underlying data.
Attribution
Place visible linked attribution near displayed information: Data via DanceStats, linking to the relevant canonical event, competition or profile page. For a page assembled from many results, also provide a link to the supporting source page for each item. Preserve original-publisher links when returned provenance identifies them. Keep built-in widget attribution visible.
Suggested citation: DanceStats, [competition title], original publisher [publisher], accessed [date], [canonical URL]. For a snapshot, retain the
complete observation URL and its effective/observation context. Clearly label
Elo ratings and predictions as computed by DanceStats. Use text attribution;
logo use, co-branding and an implication of endorsement require separate
permission. Do not imply federation sponsorship or that our predictions are
official results.
Responsible access
Respect quotas, cache controls, 429 backoff, access scopes, account ownership and publisher restrictions. Do not evade limits by rotating IP addresses, accounts, tokens or forwarding headers. Do not extract private analytics for other people, reidentify withheld profiles, publish secret tokens, or use publishable widget keys as confidential credentials.
Preserve provenance, dates and uncertainty. Refresh cached displays according to their returned cache policy; process canonical replacements, corrections and retractions. Do not continue describing a superseded or retracted observation as current. For approved bulk contracts, agree retention, correction propagation, availability and delivery terms explicitly.
Additional rights and support
Bulk redistribution, resale, training and guaranteed delivery are inquiry-only and require review of both intended use and upstream publisher rights. Submit your purpose, endpoints, volumes, retention and attribution design through Contact. Report factual errors through Feedback, with the resource URL and request ID. Policies may be versioned; review the current policy when changing your use. Documentation discovery and robots rules are not a substitute for an access or reuse agreement.