How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

RunSignup Participants API

Manage race participants including registration, editing, deletion, bib/chip assignment, and participant data retrieval.

RunSignup Participants API is one of 9 APIs that RunSignup publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 2 JSON Schema definitions.

Tagged areas include Participants. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, authentication docs, a GitHub repository, a JSON-LD context, and 2 JSON Schemas.

This API exposes 4 operations across 3 paths, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://runsignup.com/Rest.

4 operations 3 paths 8 schemas 2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://runsignup.com/Rest
Authentication
OAuth 2.0, API Key
Terms of Service
Resource Areas
1

Authentication & Security 2

RunSignup Participants API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 2 scopes. An API key is passed in the query as api_key (apiKeyAuth). By default, every request must be authenticated.

  • OAuth2 — OAuth 2.0 authentication (preferred)
  • apiKeyAuth — Permanent API key for affiliates, partners, and timers. Pass apikey and apisecret as query parameters.

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 2 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Participants 4

Manage race participants including registration, editing, deletion, bib/chip assignment, and participant data retrieval.

GET
/race/{race_id}/participants
Get Race Participants
getRaceParticipants 7 params → 200401404
POST
/race/{race_id}/participants
Add or Edit Race Participants
addOrEditParticipants 1 param body → 200400401
POST
/race/{race_id}/delete-participants
Delete Race Participants
deleteParticipants 1 param body → 200401
GET
/race/{race_id}/get-bib-chip
Get Bib and Chip Assignments
getBibChipAssignments 2 params → 200401404

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are Participant (17 properties), BibChipAssignment (6 properties), Address (5 properties), ParticipantListResponse (3 properties). Each schema is shown below with its type and property counts.

BibChipAssignment
object
6 properties
Address
object
5 properties
ParticipantUpdateResponse
object
3 properties
BibChipResponse
object
1 property
ErrorResponse
object
2 properties
ParticipantListResponse
object
3 properties
Participant
object
17 properties
ParticipantUpdateRequest
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

runsignup-participants-api-openapi.yml Raw ↑

Other APIs RunSignup publishes across the network.

RunSignup Corrals API
RunSignup Divisions API
RunSignup Donations API
RunSignup Races API
RunSignup Reference API
RunSignup Results API
RunSignup Teams API
RunSignup Users API
Where this information came from

This is an independent, third-party profile of RunSignup Participants API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.