Welcome to the Race Registration API Documentation
This API enables approved partners to securely submit race registration data. Each partner is provisioned credentials and authorized funnel access prior to integration.
API Overview
The Race Registration API is designed to handle structured race registration data intake. The platform acts as the central data ingestion layer, ensuring:
- Secure data ingestion — all submissions are authenticated and transmitted over HTTPS
- Structured validation — fields are validated on intake to prevent malformed records
- Idempotent duplicate handling — duplicate registrations are detected and suppressed safely
- Unified UUID tracking — each registration is assigned a unique identifier for traceability
All submissions are processed in real time.
Base URL
All API requests must be made to:
https://tdpudkswxg.execute-api.us-west-2.amazonaws.comAuthentication
Authentication is handled via credential validation and JWT token issuance. See the Authentication section for full details on obtaining and using tokens.
All protected endpoints require the following header:
Authorization: Bearer <jwt_token>Rate Limiting
To ensure service availability, the API enforces the following limits per credential set:
- 100 requests per minute
- 1,000 requests per hour
Exceeding these limits will result in a 429 Too Many Requests response.
Error Codes
The API uses standard HTTP status codes. See the Error Codes section for a full reference. Common responses:
| Code | Meaning |
|---|---|
| 200 | Success |
| 401 | Unauthorized |
| 403 | Forbidden |
| 422 | Validation Error |
| 500 | Internal Server Error |