Frequently Asked Questions

Subscribe to the API on RapidAPI and copy your key from the RapidAPI dashboard. Send it as the X-RapidAPI-Key header together with X-RapidAPI-Host. There is no separate Racing APIs account.

Plans, quotas and rate limits are set on each API's RapidAPI listing. RapidAPI handles billing and enforces the limits for your key.

Race results and championship standings are updated after each race weekend. Rider and team profiles are refreshed when a new season is imported.

Call GET /seasons for the current list of available seasons and GET /seasons/latest for the most recent one. Each season reports its status (completed, ongoing or upcoming).

Every successful response is a JSON object with data (an object or array) and meta (totals and paging). Errors return a JSON body with an HTTP status, message and error code.

Yes. Season-scoped endpoints take a category query parameter — MOTOGP, MOTO2 or MOTO3 — for riders, teams, calendars, results and standings. See Conventions.

Don't ship your RapidAPI key in client code — anyone could copy it and spend your quota. Call the API from your backend, a serverless function or a build step, and cache the responses. The standings table guide shows a small proxy.

Results and standings change after each race weekend; profiles change between seasons. Caching standings for an hour and profiles for a day keeps pages fast and saves quota. Suggested cache times are in Conventions.

Every endpoint in the API reference has curl, JavaScript and Python samples. The guides walk through complete projects — standings tables, rider profiles, calendars and fantasy scoring — and use cases shows which endpoints each kind of product uses.

It is in development and has no release date yet. Use the contact form to be notified at launch.

Use the contact form for questions about the APIs, data coverage or a custom plan. Current availability is on the status page.