RunSignup API Documentation

This is the complete API documentation for connecting to the RunSignup API using MindCloud's Universal API. If you are new to MindCloud, start with the Introduction to see how one API can sit in front of many different apps.

MindCloud is an integration company that offers one normalized API to access 3,100+ apps from a single place. It cleans up provider-specific quirks, keeps requests and responses consistent, and centralizes authentication so you do not need to manage separate flows for every app. Browse other apps.

Meet RunSignup: RunSignup is a race-registration and event-operations platform with APIs for race data, participants, results, fundraising, and related race-management workflows. Keep reading to get started.

Quickstart

Before you run your first RunSignup request, you need three things:

1. A MindCloud account — sign in or create an account at MindCloud.
2. A MindCloud API Key — create one in API Keys. Keep it on your server.
3. At least one RunSignup connection — create or choose one in Connections. Note its connectionId.

Every RunSignup action uses the same URL pattern:

https://connect.mindcloud.co/v1/universal/runSignup/latest/actions/{actionSlug}

You need a MindCloud API Key and a RunSignup connection. Then call an action such as Get Bib Validation Settings:

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/runSignup/latest/actions/get-bib-validation-settings" \
  --header "Authorization: Bearer $MINDCLOUD_API_KEY" \
  --get \
  --data-urlencode "connectionId=$CONNECTION_ID"

Every response comes back in the same envelope, with your rows in a data array:

{
  "success": true,
  "data": [
    { "id": "1042", "name": "Ava" }
  ],
  "meta": {}
}

After your first request works, use Shape your requests to control arguments, pagination, filtering, fields, and errors.

Authentication

Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected RunSignup account that should run the action. MindCloud stores and refreshes the RunSignup credentials behind that connection, so you never send provider tokens with your requests.

Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions. Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs.

RunSignup actions

All 40 published actions for this RunSignup version. Each page documents the endpoint, arguments, and response controls.

• PUTAdd or Edit Coupon
• PUTAdd or Edit Race Groups and Teams
• PUTAdd or Edit Race Participants
• PUTAssign Bib and Chip Numbers
• POSTCreate Event Result Set
• PUTCreate or Edit Race Corrals
• PUTCreate or Edit Race Divisions
• PUTCreate or Edit Race Teams
• DELETEDelete Participants
• DELETEDelete Race Corrals
• DELETEDelete Race Divisions
• PUTEdit Event Result Set
• GETGet Bib Validation Settings
• GETGet Current Active Registration ID for Event Transfers
• GETGet Event Start Time
• GETGet Race
• GETGet Race Participant Counts
• GETGet Race Theme
• GETList Bib and Chip Numbers
• GETList Corporate Teams
• GETList Coupons
• GETList Event Result Sets
• GETList Event Results
• GETList Race Corrals
• GETList Race Division Groupings
• GETList Race Divisions
• GETList Race Donations
• GETList Race Fundraisers
• GETList Race Group and Team Types
• GETList Race Groups and Teams
• GETList Race Participants
• GETList Races
• GETList Removed Race Participants
• GETList Timing Data
• PUTManage Race Group and Team Types
• PUTSet Race Description
• PUTSet Race URLs
• POSTSign Waivers
• PUTSwitch Participant Events
• PUTUpdate Race Syncing Settings

Related apps

More Support apps on the Universal API, behind the same REST shape. Or browse all apps.

TrelloClickUpZendeskQuoIntercomEventbriteTickTickLinear