Sign in

Approves or revokes one requirement for exactly ONE participant - strictly additive and idempotent on record level, other participants, competitions and event days stay untouched. Used by the QR scan app. Dimensions follow the requirement's switches: with perEventDay the current event day is recorded, with perCompetition the optional competitionId decides which competition the approval is for.

post/event/{eventId}/participantRequirement/approve/participant

Request

  • The document declares no server URL.
  • Auth: none declared

Request body

requirementIdstring uuid required
participantIdstring uuid required
approvedboolean required
notestring nullable
namedParticipantIdstring uuid nullable
competitionIdstring uuid nullable

For requirements with perCompetition - the competition this approval is for. Without it the fulfillment is stored without competition reference, which deliberately covers no match while the switch is on.

Response

No Content

Changes

No recorded changes to this operation across all 1 revision of this API.