Feeds and widgets
Feeds
Import competitions without writing API code. Latest-updated first, public competitions only, up to 100 entries:
/feeds/competitions.atom(Atom 1.0)/feeds/competitions.rss(RSS 2.0)/feeds/competitions.json(JSON Feed 1.1; each item also carries the full API representation in_cupa)
Query parameters: lang (ro, en), organizer (slug), country (ISO code), style (code), limit (1–100). Responses support ETag/If-None-Match.
Embeddable widgets
Organizers can embed a competition (that follows the competition through its whole life) or a list of their competitions:
<div class="cupa-embed" data-competition="123" data-lang="en"></div> <script async src="https://concursuripescuit.ro/assets/js/embed-loader.js"></script>
The competition widget is a small application, not a banner: tabs (details, participants, stands, standings, gallery), live standings, add-to-calendar, and registration inside the widget: visitors need no account, they confirm their e-mail address and are registered through the usual approval / capacity / waiting-list rules. The organizer list opens a competition inside the same frame.
Or a plain iframe: https://concursuripescuit.ro/embed/competition/123. Look options (all optional, validated): theme (auto, light, dark), lang (ro, en), accent (hex, buttons and active tabs; the text colour on it is computed), bg (hex or transparent), text (hex), radius (sharp, soft, round), font (system, inter), frame (card, flat). Content options: view (first tab: details, participants, sectors, standings, gallery), sections (comma list of header, summary, schedule, prizes, description, rules, conditions, charity, contacts, participants, sectors, standings, gallery, register; default: all), poll. Organizers can restrict which sites may embed them.
With the script snippet the iframe height follows the content and the page scrolls to the registration form when it opens. The container element receives a bubbling cupa:registered event (detail.competition) when a visitor sends the form, e.g. for analytics: el.addEventListener('cupa:registered', e => ...). Registration requests are limited (honeypot, signed form token, per-IP and per-address limits); the confirmation e-mail needs working outgoing mail (email.*).
CORS
The API and feeds answer with Access-Control-Allow-Origin: * (public read-only data), so browser applications can call them directly.