Integrations
Your club’s system + the clay shooting module
Orbit takes care of the Match — registration, target-by-target scoring in the field, and results — and has no intention of replacing the system that runs your club. The integration exists so each side does what it does best: shooters come from there, the Match runs here, results go back there.
Available today
Public REST API — no file in between
The module’s API is live. Your system creates the Match, lays out each round stand by stand, opens the Squads, registers the shooters and reads back the target-by-target card, the warnings and the standings with tie-breaks applied — all in JSON.
Authentication uses the same entity key as IPSC: the club owner generates the pair in their own panel, the secret is shown only once, and access is either read-only or read and write. What changes from one module to the other is the spec, not the credential.
-
Match, rounds and Squads over the API The Match is created as a draft with the first round and the public code already in place. You describe the layout — how many stands, how many targets on each — and build the Squads without anyone opening the panel.
-
Registrations both ways Register in bulk from your own database, or read what came in through the public registration link and reconcile it on your side. The link is to the club’s athlete roster, so nobody ends up as a duplicate record.
-
Target card and standings in JSON Target by target, with warnings and the state of each signature — enough to rebuild the Match sheet on your side. The standings come with the tie-break already applied, and you can ask for the partial while the Match is still running.
-
Your own identifier, preserved Every Match and every registration stores the id it has in your system. You match records by your identifier, not ours, and reconciliation keeps working when someone renames the Match.
Without writing any code
What already works before any integration
Not every club has someone who codes, and most of the manual work disappears without a single line.
-
Registration through the public link You publish the Match link and shooters register themselves, picking their Squad. It is not an integration, but it solves the same problem: nobody in the office types registrations in.
-
Results as CSV Standings and Teams export as CSV straight from the results screen, ready for the club spreadsheet or to publish on your own site.
-
Stable public pages The Match Hub, the standings and the venue screen live at fixed addresses, with no login — embed them in the club site or just share the link in the group chat.
-
Overlay for your stream One URL pasted as a browser source in OBS or Prism puts the round’s target card on air — no plugin, no operator typing the scoreboard.
What is not there yet
Said before you ask
Two things people coming from IPSC look for here and do not find — worth knowing before you plan your schedule, not after.
-
CSV import of registrations It exists in IPSC, not in clay yet. For bulk entry the path is the API; with no code, it is the public registration link. If CSV is what unblocks your integration, say so — a request with a club name behind it moves up the queue.
-
WinMSS export WinMSS is a practical shooting format and has nowhere to store a clay target card. The equivalent here is the API and the results CSV — same data, in a format that makes sense for the modality.
Get in touch
Shall we integrate?
Tell us which system the club uses (or which one you build) and what needs to flow to and from Orbit. We reply with a concrete path and with what can already be done at the next Match.
Frequently asked questions
Integration questions
Does Orbit integrate with my club's management system?
Yes, through the public REST API. Your system creates the Match, sets up rounds and Squads, registers the shooters and reads back the target-by-target card and the standings — all in JSON, authenticated with your entity key. It is the same key pair used for IPSC; only the spec differs.
Is there CSV import of registrations, like in IPSC?
Not yet. In clay shooting, bulk entry goes through the API, and the public registration link covers the case where the club would rather not type anyone in. If CSV is what unblocks your integration, tell us — a request with a club name behind it moves up the queue.
What about WinMSS export?
WinMSS is a practical shooting format: it has nowhere to store a clay target card. Clay results come out as JSON through the API, as CSV from the results screen, and through the public links, which are stable and require no login.
I develop a club system. How do I start?
Ask the club for an API key in their own panel and open the module’s Swagger reference, where you can try each endpoint straight from the browser. If your flow needs something beyond the standard contract, we build custom APIs.