This page lists deprecated features and upcoming breaking changes to the RunSignup API. When we plan to remove or change a feature in a way that could break existing integrations, we will list it here along with the date it takes effect. We will try to give at least 45 days’ notice before a breaking change takes effect.
Announced October 2026.
Calling get-results without individual_result_set_id returns results for every result set in the event.
For events with more than one result set, page and results_per_page are applied to each result set separately.
For example, with three result sets and results_per_page=1000, one request could return up to 3,000 results.
If a request would return more than 2,500 results in total, it returns an error instead.
In the future, individual_result_set_id will be required for events with more than one result set.
Use the get-result-sets API to get the list of result sets for an event, then pass individual_result_set_id to get results for each result set.
Takes effect on or after December 7, 2026.
Announced July 2026.
An API caller registration identifies the integration making API calls and is tied to your user account.
Sending API caller credentials is currently optional.
Once this change takes effect, every API request must include a registered API caller’s token in an HTTP GET parameter named rsu_api_reg and its password in an HTTP header named X-RSU-API-REG-SECRET.
Requests without valid API caller credentials will be rejected.
Register as an API caller, then include your token and password in every API request. API caller registration is not the same as your authentication to the API. You still need to use OAuth or API keys to access your race, events, etc.
Takes effect on or after January 1, 2027.
