Race Timing System: Send reviewed results to Sports Hub
Operational reference for send reviewed results to sports hub in Race Timing System.
Send reviewed results to Sports Hub
Create the meet and races in Sports Hub first. Use its numeric meet ID and matching race keys. The active account/plan/key needs cross_country_entries:write, plus meet management permission and applicable record licenses.
python3 sports_hub_race_entries.py --csv reviewed_results.csv --meet-id 123
python3 sports_hub_race_entries.py --csv reviewed_results.csv --meet-id 123 --send --response hub_receipt.jsonFirst command previews; second prompts for the private Hub application key and uploads. For unattended invocation you can supply GA360_API_KEY in the environment. Keep it separate from reader credentials. The request ID is stable for unchanged retries. Current Hub timing source is other; no new zebra source or raw-RFID backend endpoint is added by this kit. Hub manual results and other-source results remain protected. The API supports result upserts, not pre-race participant registration.
Need more help with this?
Search a specific symptom, review related guides below, or prepare a report with the app version, operating system and exact error. Guides describe the documented release; installed versions and subscription access can differ.
Prepare a support report