Skip to content

Connecting other software: Manager's network interfaces ​

Audience: Event organisers and club IT volunteers connecting other software — a results website, a federation system, a script, an AI app — to meshO Manager.

Every HTTP interface Manager has is listed, live, at http://<server>/swagger — on the server computer, http://localhost:5154/swagger. It is generated by the running Manager itself, so it is always complete and always matches the version you have: every address under /manager/api/, grouped by area, with the parameters each takes and what it returns, and a Try it out button that sends a real request. Software that reads an API description can fetch the same list as an OpenAPI document from http://<server>/swagger/v1/swagger.json.

The full list: /swagger ​

The list is open to anyone who can reach the server. Trying an address out is not: it goes through the same rules as any other request, so anything that changes the event — a POST, PATCH or DELETE — needs the access PIN once one is set, and you sign in by opening /manager in the same browser first. Try it out on such an address changes your event for real; use a copy of the event if you are experimenting.

Most of those addresses are the plumbing between Manager's own screens and the server, and they can change from one release to the next. Two kinds are kept stable for other software to build on: the files other software can fetch and the MCP endpoint. The rest of this page covers those, and the things Swagger can't show: the screens people open in a browser, radio punches over TCP, and the connections Manager makes out to other servers.

All of it goes out on one web server — port 5154 over HTTP, and 5155 over HTTPS once HTTPS is on (both can be changed in Settings → Server). In the addresses on this page, <server> is the server's name or IP with the port — 192.168.1.42:5154, say — and Reaching the server: name or IP says which one to give each device. {eventId} is the event's folder name, like 2026-11-10.01.

At a glance ​

WhatAddress or portDirectionDetail
Every API address, with its parameters/swagger (OpenAPI: /swagger/v1/swagger.json)Browsers connect inabove
Screens for people/manager, /rego, /, /kiosk, /screen/…, /info, /commentaryBrowsers connect inbelow
Results, start list and entry list filesGET /manager/api/ResultsExport/{eventId}/…Other software fetchesbelow
AI assistants (MCP)/manager/mcp — off by defaultAn AI app connects inAI assistants (MCP)
The HTTPS certificate/manager/api/https/ca.crtDevices download itHTTPS and certificates
This user guide/docs/user/Browsers connect in—
Radio punches in (SIRAP)TCP, the Listen port (default 10000)Another system connects inForwarding and receiving punches
Radio punches out (SIRAP or OE12)TCP, to the host and port you setManager connects outForwarding and receiving punches
Live results fileA folder, not a network addressManager writes a fileLive export
liveresultat, the meshO cloud, Eventor, ANNE, ROCTheir serversManager connects outbelow

Screens for people ​

Each of these is listed with a copy button and a QR code under Settings → Server → Access links, except the arena screens, which have their own links on the Screens page.

ScreenAddressPage
Managerhttp://<server>/manager—
Registration deskhttp://<server>/regoRegistration desk
Spectator sitehttp://<server>/Spectator site and kiosk
Kioskhttp://<server>/kioskSpectator site and kiosk
Arena screenshttp://<server>/screen/<screen-id>?eventId={eventId}TV screens
Info screenshttp://<server>/infoEvent info screens
Commentaryhttp://<server>/commentaryCommentary

Files other software can fetch ​

The entry list, start list and results that the Export menus save are also plain GET addresses, so a results website or a script can fetch them itself, as often as it likes:

DocumentIOF XMLOrienteering JSONCSV
Results/manager/api/ResultsExport/{eventId}/iof-xml…/{eventId}/json—
Start list…/{eventId}/iof-startlist-xml…/{eventId}/startlist-json…/{eventId}/startlist-csv
Entry list…/{eventId}/iof-entrylist-xml…/{eventId}/entrylist-json…/{eventId}/entrylist-csv
Start blocks—…/{eventId}/startblocks-json…/{eventId}/startblocks-csv
bash
curl -o results.xml "http://localhost:5154/manager/api/ResultsExport/2026-11-10.01/iof-xml?includeDidNotStart=true"

They take the same choices as the Publish options dialog, as query parameters:

Query parameterApplies toMeaning
kindall but the start blocksRelay or Individual. Required on an event that has both kinds of class: a file never mixes them.
classIdsallComma-separated class ids. Left out, every class.
countriesresultsComma-separated country codes; - is everyone with no country. Left out, every country.
includeDidNotStartresultstrue keeps the competitors marked DNS in the file.
acceptUnsettledresultstrue publishes even while someone has no settled result, as Ignore and continue does. Without it, the results are refused (HTTP 409, naming who is unsettled) until everybody has one.
combine, omitOrganisationIdsIOF XML resultsThe IOF XML options: classes combined for the World Ranking, and leaving out organisation ids. See Combining classes for the World Ranking.
includePrivateFieldsJSON resultsAdds birth year and sex. Needs a signed-in operator.

The JSON format, what each parameter does in detail, and the schema to validate against are in Orienteering JSON (OJSON). What a results file says about each status is in What an exported results file contains.

Things to know:

  • These answer without the access PIN, as every read does on a Manager running on your own computer — so anyone who can reach the server can fetch them. Two things do need a signed-in session where a PIN is set: includePrivateFields, and the results while a class is held back in quarantine.
  • To feed a live-results system that watches a folder, such as LiveResults EmmaClient, use the Live export instead: it writes the results file every few seconds or minutes on its own, including runners still on course.
  • Nothing pushes to you. There is no webhook: software that wants the latest results fetches again.

Reading the event from another program ​

To have another program read the event and answer questions about it rather than fetch a file, connect it as an AI assistant over MCP: that is the interface designed for it, and it is switched off until you turn it on.

Connections Manager makes itself ​

Some features have Manager connect out to someone else's server, rather than the other way round. Each is off until you set it up:

FeatureConnects toPage
Live results onlineliveresultat.orientering.se, and the meshO cloud (events.mesho.live)Publishing live results online
EventorYour federation's Eventor, with your organisation's API keyCreate an event from Eventor, Uploading to Eventor
ANNEANNE, the Austrian orienteering portal — the real one or its test copy, as Settings → ANNE saysImporting from ANNE, Uploading to ANNE
ROC radio controlsThe ROC server, to fetch punchesRadio controls that report to ROC
Radio punch forwardingThe TCP host and port you setForwarding and receiving punches
Built-in assistantmeshO's assistant serviceBuilt-in assistant