EVENT ACCESS // SECURE WORKSPACE
Verifying your SIGNAL session and event permissions…
SIGN IN TO EVENT ACCESS →RETURN TO SIGNALEVENT OPERATIONS
EVENT OVERVIEW
A live summary of participant attendance across your competition.
CHECK-INS BY SESSION
Compare check-ins across all three competition days.
PARTICIPANT STATUS
Participants in the selected period.
ATTENDANCE RECORDS
Use filters to view participant-level records. The overview stays focused on totals and trends.
GATE OPERATIONS // SESSION CONTROL
Gate sessions can only be opened or closed by a Super Admin.
| DAY / SESSION | SCHEDULE | STATUS | ACTION |
|---|---|---|---|
| Loading sessions… | |||
ATTENDANCE BY CATEGORY
| CATEGORY | SELECTED | CHECKED IN | INSIDE NOW | CHECKED OUT | NOT ARRIVED |
|---|
PARTICIPANT STATUS
EVENT DETAILS
Participant records and operations are scoped to this event.
REGISTRATION WORKFLOW
| NAME | INSTITUTION | CATEGORY | SELECTION |
|---|
GATE OPERATIONS // PARTICIPANT DIRECTORY
Search the full event participant list and choose an action for an individual.
| PARTICIPANT | SELECTION | ACTION |
|---|
DISTRIBUTION WORKFLOW
Generate QR files here or send fresh QR tickets directly to participants by email. Downloads and sharing are also available after generation. Replacing an active ticket disables its previous QR.
| REFERENCE | PARTICIPANT | STATUS | ISSUED | QR FILE | ACTION |
|---|
DISTRIBUTION
Eligible participants with email addresses receive a fresh QR ticket. The same QR can be used for Day 2 Session 1 and Session 2. Existing active tickets are replaced when you send this distribution.
| RECIPIENT | STATUS | ATTEMPTS | LAST ATTEMPT | ACTION |
|---|
GATE OPERATIONS // ONLINE-FIRST
Use the camera to scan a SIGNAL ticket QR, or enter its credential below.
GATE OPERATIONS
Search for the participant and confirm the departure. The movement history remains append-only.
INSIGHTS & GOVERNANCE WORKFLOW
GOVERNANCE
Invite an assistant by email and choose “Check-in & check-out assistant.” Once they accept the email invitation, they can scan tickets and record check-ins and check-outs for this event.
SPREADSHEET IMPORT
Upload a CSV or XLSX file. Mapping is explicit, and no rows are committed until you confirm the preview.
INTEGRATION GUIDE
Issue an event-scoped key. It is shown once; store it in a backend secret manager.
Base URL:
Send X-API-Key: your_key with each request. Keys are limited to 60 requests per minute and are scoped to the selected event. Read endpoints return participant IDs and attendance timestamps, never contact details.
| METHOD | PATH | USE |
|---|---|---|
| GET | /api/v1/events/{eventId}/access | Event details, days and sessions |
| GET | /api/v1/events/{eventId}/attendance/summary?day=1&session=2 | Filtered statistics and three-day trends |
| GET | /api/v1/events/{eventId}/attendance?day=1&session=2 | Attendance rows for a day/session |
| GET | /api/v1/events/{eventId}/participants/{participantId}/attendance | Participant attendance history |
| POST | /api/v1/events/{eventId}/check-ins | Record an authorized check-in |
{"participantId":"registered-participant-uuid","day":1,"session":2,"source":"door-tablet-1"}Send JSON to the POST endpoint. Success returns HTTP 201 with the server timestamp. Duplicate check-ins return HTTP 409; unregistered participants return HTTP 404. Invalid inputs return HTTP 400, invalid keys return HTTP 401, missing scopes return HTTP 403 and rate limits return HTTP 429.
const response = await fetch(`${BASE_URL}/api/v1/events/${EVENT_ID}/check-ins`, {
method: "POST",
headers: { "Content-Type": "application/json", "X-API-Key": API_KEY },
body: JSON.stringify({ participantId, day: 1, session: 1, source: "registration-app" })
});
const result = await response.json();Keep API keys on a trusted server. Never embed them in public browser code. Revoke a compromised key and create a replacement.
GATE OPERATIONS // ATTENDANCE
Find checked-in participants or review who has not checked in for the selected period.
| PARTICIPANT | CATEGORY | STATUS / SESSION | CHECKED IN |
|---|