API Reference
Introduction
The Intervals Partner API lets you build integrations that read and write running event data for your organization.
Base URL
All API requests are made against the following base URL.
What you can build
- Pull your event series and upcoming runs into your own website
- Create events programmatically from your internal tools
- Sync participant data with your registration system
- Build custom dashboards with live event data
Quick example
Fetch all recurring schedules for your organization with a single request.
Versioning
The API does not use URL-based versioning. When breaking changes are introduced, we will version via calendar-based headers (e.g. Intervals-Version: 2026-03-01). Requests without a version header always use the latest stable version. The API is currently unversioned, so do not send an Intervals-Version header yet — an unrecognized version returns 400 BAD_REQUEST. We’ll announce each version in the changelog well in advance and support previous versions for a migration period.
Enumerated fields can gain values Additive, and not a version bump
We may introduce a new value in an enum-valued field without a version bump — removing one would break you, adding one does not. roles on the organization resource is the field this applies to today; it gained charity in v1.3. If you validate responses against a pinned list, treat an unrecognized value as unknown rather than as an error, and watch the changelog.
Next steps
Head to the Authentication page to learn how to create an API key and start making requests.