Race data terms

Attribution is required

Wherever you show race data, show the Data from Endurance HQ badge or the words "Data from Endurance HQ", and link the race's official site, the eventUrl in every response's attribution block.

When a response credits contributors (the people who measured or corrected the data), show their credit next to the data they touched.

Do not imply official status

Your app is not the race's official app, and neither the organizer nor Endurance HQ endorses it, unless the organizer approves that in writing. Name the race as the source of the data, not as your partner, and do not use the race's or Endurance HQ's logos except the badge on this page.

Personal data stays with the race

Names, bibs, positions and results appear in the API only where the race already shows them publicly, and a runner the race removes from public view disappears from the API. Mirror that: drop a runner your app stored once the API stops returning them.

Do not sell, rent or share personal data from the API, combine it across races to profile people, or use it for marketing. Show live positions for the race in progress, not as a history of where someone was.

Rate limits

Keyed reads are limited per key, 120 requests a minute today. A 429 answer carries Retry-After: wait that long. The open reads are cached for minutes, so polling them faster returns the same answer.

Subscribe to race events instead of polling for changes. One key belongs to one app; do not spread one app across several keys to raise its limit.

The organizer decides

Each race's organizer controls its data. Open race data can be turned off, and companion apps (live tracking and results) are off until the organizer turns them on. When a switch is off the API answers 403; stop showing live positions you stored from that race.

Revocation

We can suspend or revoke a key, or block an app, at any time: for breaking these terms, for load that affects other users, or at a race organizer's request. Wolfe Run developer keys are revoked in Wolfe Run, and Endurance HQ stops accepting a revoked key within a minute.

Accuracy and safety

Race data comes as is. Timing reads, GPS fixes and predictions can be late or wrong, and the API can be unavailable. Never use it for safety decisions such as search and rescue; those belong to the race and its officials.

Fields only gain under /v1; a breaking change gets a new version. We may update these terms and will change the date below when we do.

The Data from Endurance HQ badge

Place it near the data, at its own size or larger, and link it to the race's official site. In a native app, show the image or the words and open the race's site on tap.

<a href="{attribution.eventUrl}" rel="noopener">
  <img src="https://www.endurancehq.app/badges/data-from-endurance-hq.svg"
       alt="Data from Endurance HQ" width="196" height="36">
</a>