Pull race listings and registered participants for a race via the RunSignup API
domain: runsignup.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Request API credentials (api_key and api_secret) from RunSignup for your application
Call the races endpoint with search params (e.g. start_date) to find races and their events
Call the race detail endpoint for a specific race_id to get its events (e.g. 5K, Fun Run)
Call the participants endpoint for a race_id, using after_registration_id to page through and fetch only new registrations since your last sync
Always call over HTTPS and pass api_key/api_secret as required request parameters
Known gotchas
Credentials are passed as request parameters rather than a header — always use HTTPS or they're exposed in transit/logs
Participant data access depends on the race timing partner/owner granting your application permission for that specific race — a valid API key doesn't automatically grant access to every race's participant data
Use after_registration_id-based incremental paging for syncing, not just start_date filters, or you risk missing or duplicating registrations between polls
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?