RunSignup API

Name: RunSignup API API
Brand: RunSignup API
Availability: InStock

✓ Official Vendor SpecCommunicationsChat MessagingapiKey, oauth288 EndpointsREST

For Agents

Programmatically get race information, list upcoming races. Covers 88 operations with apiKey, oauth2 authentication.

Use for: I need to race information, I want to upcoming races, Search for set race syncing settings, Find all set race and event urls

Connect the RunSignup API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the RunSignup API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with RunSignup API API.

Get race information

List upcoming races

Set race syncing settings

Query and filter RunSignup API records by parameters

Monitor RunSignup API operational status and events

GET STARTED

Start building with RunSignup API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use RunSignup API API for, with concrete tasks.

★ Communications Operations

Use the RunSignup API to perform communications operations programmatically. The API provides 88 endpoints covering core functionality including get race information, list upcoming races, set race syncing settings.

Call GET /API/race/{race_id} to get race information

Automated Announcer Management

Automate announcer operations by combining multiple RunSignup API endpoints. Agents can list upcoming races and then set race syncing settings in a single workflow.

Call GET /API/races to list upcoming races, then verify the result

AI Agent Integration via Jentic

AI agents discover and call RunSignup API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey, oauth2 tokens manually.

Search Jentic for 'get race information', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

88 endpoints — the runsignup api provides programmatic access to runsignup's race management platform.

METHOD

PATH

DESCRIPTION

GET

/API/race/{race_id}

Get race information

GET

/API/races

List upcoming races

POST

/API/race/{race_id}/sync-settings

Set race syncing settings

POST

/API/race/{race_id}/race-urls

Set race and event URLs

POST

/API/race/{race_id}/race-description

Set race description

GET

/API/countries

Get list of countries and states

GET

/API/v2/auth-info/entity-info.json

Get entity information for a v2 API key

POST

/API/race/{race_id}/participants

Add or edit race participants

GET

/API/race/{race_id}

Get race information

GET

/API/races

List upcoming races

POST

/API/race/{race_id}/sync-settings

Set race syncing settings

POST

/API/race/{race_id}/race-urls

Set race and event URLs

POST

/API/race/{race_id}/race-description

Set race description

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

RunSignup API apiKey, oauth2 credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'get race information') and Jentic returns the matching RunSignup API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct RunSignup API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Twilio

Alternative communications API

Choose Twilio when you need a different approach to communications operations

Alternative

Sendgrid

Alternative communications API

Choose Sendgrid when you need a different approach to communications operations

Complementary

Pusher

Complementary communications API

Choose Pusher when you need a complementary approach to communications operations

FAQs

Specific to using RunSignup API API through Jentic.

What authentication does the RunSignup API use?

The RunSignup API uses apiKey, oauth2 authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I get race information with the RunSignup API?

Yes. Use the GET /API/race/{race_id} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the RunSignup API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I get race information through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'get race information'. Jentic returns the matching RunSignup API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the RunSignup API have?

The RunSignup API exposes 88 endpoints covering announcer, basic info, clubs operations.