Password dimenticata? Iscriviti
RACE RESULT 14 API: Authentication Update

At the end of 2026, we’re changing how external solutions connect to RACE RESULT 14. The current authentication method will no longer be compatible after that.

Key facts

  • Existing API keys keep working. You don’t need to create new keys.
  • The new authentication is already available. Providers can switch over now.

Does this affect me?

Most RACE RESULT 14 users don’t need to do anything. You’re only affected if you use an external solution (for example a registration platform, results app, or display/broadcast tool) where you either:

  • log in with your RACE RESULT account, or
  • have entered an RR14 API key.

I use an external solution. What should I do?

Please contact the provider of that solution and ask whether they’ve already made the update. If they have any questions, they’re welcome to contact us.

I’m a provider or have my own integration. What changes?

Your existing API key stays valid. Only the way you authenticate with it changes, and the new method is already live. Instead of the previous login, you exchange the API key for an access token and send that token with every request.

  1. Request a token: Send your API key via POST to /api/token/get (form value apikey). The response contains access_token, refresh_token, and expiry.
  2. Call the API: Add the header Authorization: Bearer <access_token> to every request.
  3. Renew the token: The token is valid for 2 hours. Before it expires, either renew it via /api/token/refresh (form value refresh_token) or request a new one with your API key. After a refresh, store and use both the new access_token and the new refresh_token.

All details, including code examples, are in the attached RACE RESULT 14 API – Authentication Guide (PDF).

Our recommendations

  • Use the API key. Logging in with username and password is possible, but only works if two-factor authentication (2FA) isn’t enabled for the account, which is less secure.
  • Plan for token renewal in long-running tools. Displays, broadcast systems, or services that run all day need to renew the token automatically. This is the part worth testing most carefully.
  • Keep the API key and tokens out of your source code. Load them from environment variables or a secret store instead.
  • Start early. The new method is already available, so you can switch and test right away.

Timeline

  • Now: The new authentication is live. Both the current and the new method work.
  • Until December 31, 2026: The current method keeps working.
  • After that: Only the new method will be supported.

Related articles

  • RACE RESULT 14 API – Authentication Guide.pdf
×

Ha qualche domanda?

Il nostro team sarà lieto di consigliarla personalmente.

╳

Contattaci!

Il team di RACE RESULT sarà lieto di valutare le vostre esigenze individuali, risolvere eventuali problemi e rispondere a qualsiasi domanda. Non esitate a contattarci tramite il modulo disponibile ora.

Se hai una richiesta di supporto, aggiungi il tuo ID evento!

Ho letto i termini sulla privacy dei dati.