MediaWiki API result
This is the HTML representation of the JSON format. HTML is good for debugging, but is unsuitable for application use.
Specify the format parameter to change the output format. To see the non-HTML representation of the JSON format, set format=json.
See the complete documentation, or the API help for more information.
{
"batchcomplete": "",
"continue": {
"lecontinue": "20260807081828|3",
"continue": "-||"
},
"query": {
"logevents": [
{
"logid": 13,
"ns": 0,
"title": "Team Entry Board",
"pageid": 13,
"logpage": 13,
"revid": 117,
"params": {},
"type": "create",
"action": "create",
"user": "Trackinfo",
"timestamp": "2026-10-08T11:05:35Z",
"comment": "Created page with \"= Team Entry Board = == Overview == The '''Meet Entry Board''' is the Team Leader's workspace for entering athletes into a track and field meet. It brings the team's athlete roster and the meet's available events together on one page, allowing the Team Leader to organize entries, assign athletes to events, manage relay teams, and review the team's participation. The board is designed around direct interaction: select athletes, drag them into events, review their assi...\""
},
{
"logid": 12,
"ns": 0,
"title": "Privacy policy",
"pageid": 12,
"logpage": 12,
"revid": 85,
"params": {},
"type": "create",
"action": "create",
"user": "Trackinfo",
"timestamp": "2026-09-10T17:35:15Z",
"comment": "Created page with \"'''To Run It''' collects personal information necessary for sorting your data for track and field, running and walking events. We are supported by usage fees a Meet Director pays us and includes those fees as part of the entry fees you pay to participate in their meet. That means we are not advertiser supported. There are no advertiser links or data mining elements built into our code. What we embed in your device is necessary for our purposes to make your participa...\""
},
{
"logid": 11,
"ns": 0,
"title": "Privacy notice",
"pageid": 11,
"logpage": 11,
"revid": 80,
"params": {},
"type": "create",
"action": "create",
"user": "Trackinfo",
"timestamp": "2026-09-10T12:06:17Z",
"comment": "Created page with \"'''To Run It''' collects personal information necessary for sorting your data for track and field, running and walking events. We are supported by usage fees a Meet Director pays us and includes those fees as part of the entry fees you pay to participate in their meet. That means we are not advertiser supported. There are no advertiser links or data mining elements built into our code. What we embed in your device is necessary for our purposes to make your participat...\""
},
{
"logid": 10,
"ns": 0,
"title": "About",
"pageid": 10,
"logpage": 10,
"revid": 79,
"params": {},
"type": "create",
"action": "create",
"user": "Trackinfo",
"timestamp": "2026-09-10T11:57:44Z",
"comment": "Created page with \"'''To Run It''' is an intended modernization of meet management technology. io It uses communication tools available through the internet to accomplish tasks in close to real time. Being dependent on the internet, you will need good connectivity in your stadium or venue. If it is not available from local cel sites, we strongly recommend you supplement with service that effectively can deliver the data at the speeds you want.\""
},
{
"logid": 9,
"ns": 0,
"title": "Event families",
"pageid": 9,
"logpage": 9,
"revid": 22,
"params": {},
"type": "create",
"action": "create",
"user": "Trackinfo",
"timestamp": "2026-08-09T22:42:04Z",
"comment": "Created page with \"Event families are events where the division and rule book determine the actual event. It applies to hurdles, where different divisions run different distances. The easiest example is the short hurdles, where most female divisions run a different distance, like 100H, than the male divisions, like 110H. You can select the family once then the rulebook. Later in the meet, you will find each correct distance for each division you offer.\""
},
{
"logid": 8,
"ns": 0,
"title": "Micro/Daily Scheduler",
"pageid": 8,
"logpage": 8,
"revid": 16,
"params": {},
"type": "create",
"action": "create",
"user": "Trackinfo",
"timestamp": "2026-08-07T12:37:45Z",
"comment": "Created page with \"{{DISPLAYTITLE:Micro/Daily Scheduler}} The '''Micro/Daily Scheduler''' is the detailed operational scheduling page for a multi-day meet. The [[Macro Scheduler]] establishes the large-scale structure of the meet: * Which day an event occurs * Which facility it uses * Its general order * Its scheduled starting position The Micro/Daily Scheduler takes those scheduled blocks and exposes the detailed operation inside them. It is where the Meet Director can examine and re...\""
},
{
"logid": 7,
"ns": 0,
"title": "Macro Scheduler",
"pageid": 7,
"logpage": 7,
"revid": 11,
"params": {},
"type": "create",
"action": "create",
"user": "Trackinfo",
"timestamp": "2026-08-07T10:23:27Z",
"comment": "Created page with \"{{DISPLAYTITLE:Micro/Daily Scheduler}} The '''Micro/Daily Scheduler''' is the detailed operational scheduling page for a multi-day meet. The [[Macro Scheduler]] determines the broad day, order, facility, and approximate placement of events. Micro/Daily then exposes the detailed timing and internal structure of those blocks. Use it to answer questions such as: * Exactly when does this block start? * How many heats or flights does it contain? * Which divisions compete...\""
},
{
"logid": 6,
"ns": 0,
"title": "Schedule",
"pageid": 6,
"logpage": 6,
"revid": 8,
"params": {},
"type": "create",
"action": "create",
"user": "Trackinfo",
"timestamp": "2026-08-07T10:19:23Z",
"comment": "Created page with \"{{DISPLAYTITLE:Schedule}} The '''Schedule''' page creates and manages the operational schedule for a one-day meet. It takes the events, divisions, participant estimates, rounds, facility information, and meet settings already entered elsewhere in Torunit and turns them into a timed competition schedule. For a multi-day meet, use the [[Macro Scheduler]] and [[Micro/Daily Scheduler]] instead. == Who should use this page? == Use the Schedule page for a one-day meet. B...\""
},
{
"logid": 5,
"ns": 0,
"title": "Rounds",
"pageid": 5,
"logpage": 5,
"revid": 7,
"params": {},
"type": "create",
"action": "create",
"user": "Trackinfo",
"timestamp": "2026-08-07T09:40:15Z",
"comment": "Created page with \"{{DISPLAYTITLE:Rounds}} The '''Rounds''' page defines how athletes advance through qualifying rounds before the schedule is built. It operates at the '''GDE''' level \u2014 Gender, Division, Event \u2014 so different divisions or genders in the same event may use different round structures when necessary. The page also records anticipated participant counts used to calculate heats and advancement. == Who should use this page? == Use the Rounds page when a meet requires mo...\""
},
{
"logid": 4,
"ns": 0,
"title": "Participants",
"pageid": 4,
"logpage": 4,
"revid": 6,
"params": {},
"type": "create",
"action": "create",
"user": "Trackinfo",
"timestamp": "2026-08-07T09:39:09Z",
"comment": "Created page with \"{{DISPLAYTITLE:Participants}} The '''Participants''' page records the number of athletes the Meet Director expects to enter each event, division, and gender combination. These anticipated numbers are used by Torunit to estimate heat sizes and build the initial one-day schedule. The figures entered here are planning numbers. They are not the final entry list. == Who should use this page? == The Participants page is primarily intended for one-day meet scheduling. Use...\""
}
]
}
}