Practical shooting help

Integrations — importing registrations and exporting results

For integrators and external systems: integration today is by file and by portal. Registrations enter the system via CSV, results go out in WinMSS format — the standard used by IPSC scoring programs — and, when you finalize the match, Orbit publishes the classification on the scoring.services portal (source Orbit). No step requires technical access: everything happens on the match screen.

The public REST API is now available: manage matches, divisions, stages, squads, ROs and registrations, and read full results in JSON, with your entity API key. The file formats on this page remain valid for manual import/export. API reference (Swagger)

1. Importing registrations (CSV)

The source system (the club's own registration site, a spreadsheet, other software) exports a CSV and the match staff imports it under Registrations → Import CSV. Before anything is saved, the system shows a preview of what will be created, updated or rejected — registrations only enter the match after confirmation.

File rules

Semicolon separator (;), UTF-8 encoding (Excel BOM is accepted).
The first line is the header, with the column names. Column order is free and names are case-insensitive.
Required columns: ATLETA, CPF and DIVISAO. Everything else is optional.
Dates in dd/mm/yyyy format (with optional time dd/mm/yyyy HH:MM:SS). CPF with 11 digits, with or without the mask.
One line per registration: an athlete shooting two divisions appears on two lines, with the same CPF and a different DIVISAO.

Recognized columns

Column	Content
ATLETA	Full name (required).
CPF	Athlete's CPF (required) — it is the key that prevents duplicate registrations.
DIVISAO	Division name (required). If it does not exist in the match, it is created during import.
MODALIDADE	Division modality (Handgun, Mini Rifle, PCC…). The usual IPSC names are accepted.
EMAIL · TELEFONES	Athlete's contact details.
DATA_NASCIMENTO	Date of birth
CR · VALIDADE_CR	Registration certificate and its expiry date.
UF_ATLETA	Athlete's state (UF).
CLASSE · CATEGORIA	Class (GM, M, A…) and category (Senior, Lady…).
STATUS	Payment status — the value PAGO confirms the registration automatically.
SQUAD · POSTO	Squad number (created if it does not exist) and shooting order within it.
TIPO_ARMA · MODELO_ARMA · MARCA_ARMA · CALIBRE · NUMERO_SERIE · NUMERO_SIGMA	Athlete's declared equipment.

Any other column is preserved — external identifier, membership number, city, amount paid, barcode, whatever the source system wants to send. These fields are visible on the registration as additional items and come back with the athlete when queried. There is no need to remove columns from the original export.

Recommended header

ATLETA;CPF;EMAIL;TELEFONES;DATA_NASCIMENTO;CR;VALIDADE_CR;UF_ATLETA;MODALIDADE;DIVISAO;CLASSE;CATEGORIA;STATUS;SQUAD;POSTO;TIPO_ARMA;MODELO_ARMA;MARCA_ARMA;CALIBRE;NUMERO_SERIE;NUMERO_SIGMA

Minimal valid example (required columns only):

ATLETA;CPF;DIVISAO
Fulano de Tal;111.444.777-35;Production
Fulano de Tal;111.444.777-35;Production Optics

Logged-in staff can download the ready-made template (header + sample line) on the import screen itself.

How the system handles the file

Preview without saving — the file is analyzed and the screen lists, line by line, what will be created, what will be updated and the errors/warnings (invalid CPF, new division, new squad).
Confirmation — only valid lines are applied.
Re-importing does not duplicate — the key is match + CPF + division. Sending the same file again (or a corrected version) updates the existing registrations. The integrator can always export the full file, without tracking diffs.
Empty contact fields get placeholder values — and a re-import with real data does not overwrite data already confirmed by the athlete in the system.

2. Exporting results (WinMSS)

At any point during the match, the officials (RM / Stats) download, under Results → Export WinMSS, a .zip package in WinMSS format. It is used for verification, parallel scoring and submission to ranking systems that already read this format.

What comes in the package

The six files of the WinMSS format — THEMATCH.XML (match data), MEMBER.XML (athletes), ENROLLED.XML (registrations: division, category, squad, power factor, DQ), STAGE.XML (stages) and SCORE.XML (scores), plus CLASSIFY.XML.
A winmss_export.cab with the same files — the compressed format that WinMSS imports directly.

Three ways to download

Full match — all divisions in a single package.
All divisions — one zip with a folder per division, each with its own XML files.
Per division — a master zip containing a complete zip (XML + cab) for each division, ready to distribute separately.

Generation rules

Only active registrations are included (cancelled ones are left out) and only approved scores — drafts and entries pending the athlete's PIN never leave in the export.
Chrono and equipment-check Stages do not become a Stage in the file.
The division is converted by its official IPSC name (Production, Open, Production Optics, PCC…). A division with a name outside the IPSC table gets a generic code — for external rankings, use the official names in the match divisions.
The category is recognized by name (Lady, Junior, Senior, Super Senior, Military/Law Enforcement…), including when it comes from registration tags.
Power factor (Major/Minor), DQ and squad follow each registration. Each score carries A/C/D hits, misses, penalties, procedurals, time, hit factor and points.
Each athlete with an account in the system carries a stable identification number — the same across all matches — repeated in the Telephone and Alias fields of the WinMSS record. It is what lets the external system recognize the same athlete across different matches. Guests without an account get a synthetic number, unique only within that package.
When the club uses external membership codes, the athlete's code goes in the record's RefNo field.

To import into WinMSS: use the winmss_export.cab file from the package in WinMSS's match import function. The loose XML files are for systems that read the format directly.

3. Publish on scoring.services (Orbit)

When every Score is entered, Finalize the match opens a modal with Send results to scoring.services checked by default. Confirming publishes classification by division and each athlete’s detail on the scoring.services portal, with source Orbit. Practical shooting (IPSC) only.

You can update the results later from the match overview.
You can remove the match from the portal and send it again later.
If sending fails, the match stays finalized; try again with the button on the overview.

4. Public results (link)

Besides the file, published results live at a stable public link (/r/CODE) that the external system can embed or share — no login, and nothing beyond what the match published is exposed.

Integrator checklist

CSV with ;, UTF-8, header on the first line.
ATLETA, CPF and DIVISAO present on every line.
One line per division; re-import updates, it does not duplicate.
External identifier in its own column (e.g. IDENTIFICADOR) — it comes back in the additional items.
Match divisions named with official IPSC names, if the destination is an external ranking via WinMSS.
For the scoring.services portal: finalize the IPSC match with the send option checked (or use the button on the overview afterwards).

Do you build a club management system? We are open to building the integration together — the public REST API is live and evolves with partners. Talk to us on the integrations page.

← All guides Entity guide →